M-Pesa STK Push for online stores | DASNET
STK Push lets a supported merchant initiate a payment prompt to a customer's phone so the customer can review and authorise the request on their device.
This guide explains the workflow, how to prepare, which checks matter and how to handle common exceptions for online stores.
Explore DASNETDeveloper documentation
Understand the workflow, apply the checklist, and confirm which payment channels and features are enabled for your account before using them in production.
What M-Pesa STK Push means for online stores
STK Push lets a supported merchant initiate a payment prompt to a customer's phone so the customer can review and authorise the request on their device. For online stores, the goal is to connect checkout outcomes to orders and fulfilment. A reliable workflow makes the request, responsible person, reference and final outcome visible rather than leaving the process in disconnected messages.
The operational challenge
A common challenge is that a checkout page can return before the provider sends the final payment result. When the source request, payment status and business record do not line up, staff can repeat work or act on an assumption. A consistent process separates initiation from completion and records the evidence used to make a decision.
A practical end-to-end workflow
- Confirm the business shortcode, credentials, callback URL and permitted transaction type with the provider.
- Present the amount and purpose before initiating a prompt; never ask a customer to disclose their PIN.
- Treat the initiation response as a request identifier, not proof of payment.
- Validate and securely process the asynchronous callback, handle retries idempotently, then reconcile the final result.
A workflow shaped around this use case
- Create a unique order reference before initiating checkout.
- Keep the order pending until a trusted final result arrives.
- Release goods or digital access only after verifying the relevant status.
How DASNET fits
DASNET is a business workspace for supported payment workflows and everyday business operations. Depending on account configuration, teams may use it to manage payment requests and collections, review transaction records, handle supported wallet and payout activity, organise invoices or bills, and keep customer and operational information together. The precise menu, channel and automation available to a business should be confirmed in its account. DASNET is not a promise that every payment rail, bank destination or provider feature is automatically enabled.
Controls and measures to review
- Track the number of unresolved items and how long they remain open.
- Separate pending, successful, failed, reversed and disputed outcomes in reports.
- Keep a clear owner for exceptions and a reference for every consequential action.
- Review access permissions and avoid storing credentials or sensitive authentication data in notes.
- Compare material payment totals with trusted provider or bank records.
Frequently asked questions
Does an STK Push request mean the customer has paid?
No. Initiation means a prompt was requested. Mark an order paid only after a trusted final result confirms success.
Can customers share their M-Pesa PIN with DASNET support?
No. Customers enter their PIN only in the authorised provider prompt. DASNET staff should never request or store it.
What if the prompt times out?
Check the transaction status and callback history before retrying. Avoid creating duplicate charges from a blind retry.
Can any merchant use STK Push immediately?
It depends on the merchant shortcode, production Daraja permissions, credentials, callback setup and DASNET account configuration.
How does this apply to online stores?
The main objective is to connect checkout outcomes to orders and fulfilment. Start with the workflow and controls on this page, then verify the exact features enabled for your DASNET account.
What should we do if a payment or record looks wrong?
Pause any consequential action, keep the non-sensitive reference and timestamp, check the trusted source record, and follow your documented support or reconciliation process. Never share PINs, OTPs, passwords or API secrets.
Does DASNET guarantee that every feature is enabled?
No. Product availability depends on account setup, permissions, provider approvals and enabled services. Confirm the live configuration before making operational commitments.
Related DASNET guides
Continue with these related workflows:
STK Push integration guide for online stores · Safaricom Daraja API workflows for online stores · Online payment links for online stores · Customer payment requests for online stores · Merchant payment collections for online stores · Bulk payouts and bulk payments for online stores