M-Pesa payment workflows built for business software.
NetPay gives your application a consistent way to initiate STK Push, receive provider outcomes, and work with payment records across connected merchants.
STK Push
Initiate a customer payment prompt using the connected merchant's Daraja integration. Treat the initiation response as an acknowledgement, not proof of payment.
Callback-backed outcomes
Receive provider callbacks, correlate them to the payment request, and update payment state from the evidence received.
Payment events and records
Use durable payment records and supported event delivery to connect payment changes to your own order, POS, or business workflow.
Merchant-aware integrations
Connect each merchant with their own shortcode and Daraja credentials rather than mixing merchant configurations.
A payment layer for your existing product.
Keep your checkout, orders, and business rules in your application. NetPay handles the integration boundary and makes payment outcomes available for your software to consume.
- 1
Connect a merchant
Configure the merchant's shortcode and Daraja credentials securely.
- 2
Initiate the payment
Your server calls the NetPay API with the merchant integration and client reference.
- 3
Process the outcome
Use callback-backed status and supported payment events to update your own workflow.
Know the boundaries before you integrate.
Daraja products can require specific permissions and configuration. C2B is optional for merchants that need it. Transaction-status verification and merchant-specific validation behavior may require additional setup or may not be available for every integration.
Read current capabilities and limits