Questions about NetPay
Straight answers aligned with how the product actually works—not marketing shortcuts.
What is NetPay?
NetPay is a multi-merchant M-Pesa Daraja gateway for business software. Each merchant uses their own shortcode and Daraja credentials. Your product calls one consistent API.
Does a successful STK Push initiation mean the customer paid?
No. Initiation only means Daraja accepted the prompt request. Payment state changes when provider evidence arrives (callback or verified status). NetPay never treats initiation alone as proof of payment.
Who owns the Daraja credentials?
The merchant. NetPay stores them encrypted and uses them to call Daraja on the merchant’s behalf. A successful OAuth token proves authentication, not every shortcode permission.
How do I know a payment succeeded?
Use the payment resource status driven by provider results, and optionally subscribe to durable payment events (including signed webhooks when enabled).
Is the merchant dashboard available?
A dashboard shell is available as a preview. Merchant sign-in and live data are not enabled until NetHub identity is connected. Integrate via the M2M API today.
Do I have to register C2B URLs?
No. C2B registration is opt-in for merchants that need it. STK-only merchants are not forced to register C2B validation/confirmation URLs.
What about sandbox outages or delayed callbacks?
Provider sandboxes can be intermittently unreachable. NetPay is designed around idempotent handling and durable events so your system can recover when evidence arrives later.
How do I get access?
Review the API overview, then request access so NetHub can onboard your integration. Do not send Daraja secrets over unsolicited email threads without a secure channel.