By Bonaventure Ogeto · Published · Last verified: 2026-11-04
Daraja vs PayShap: an API-level comparison
The short answer
Daraja is Safaricom's own developer portal for its APIs[Safaricom Daraja developer portal, checked 2026-11-05], so you integrate the operator directly. PayShap is a scheme that PayInc runs[SARB media release and FAQ, checked 2026-11-05], reached through a bank or a provider such as Stitch[Stitch, checked 2026-11-05] or Ozow[Ozow blog, checked 2026-11-05]. An STK Push and a PayShap Request[PayInc Business Report 2025, checked 2026-11-04] share one shape: you ask, the payer approves, a callback confirms.
Source: Mctaba Labs, “Daraja vs PayShap: an API-level comparison”, last verified 2026-11-04, mctaba.com/learn/payments/kenya-vs-southern-africa/daraja-vs-payshap
Mctaba Labs builds payment integrations for businesses across Africa. This guide is written to be useful whether or not you ever hire us.
How different are Daraja and PayShap at the API level?
Less different in shape than in plumbing. Both give you a way to ask a customer for a specific amount and get told, later, whether they paid. What differs is who you are talking to when you make that request, how you identify the payer, and how much of the rail you can see.
- Daraja is a single operator's API. Daraja is Safaricom's developer portal for its APIs[Safaricom Daraja developer portal, checked 2026-11-05], with sandbox apps to test against[Safaricom Daraja developer portal, checked 2026-11-05]. You register, get credentials and call Safaricom.
- PayShap is a scheme. PayInc runs it, alongside EFT credits and debits, DebiCheck, Registered Mandate and RTC[SARB media release and FAQ, checked 2026-11-05], and banks take part in it. You call a bank or a payment provider, and it talks to the scheme for you.
That one difference explains most of what follows. If you are mapping a Kenyan product onto South Africa, or the other way round, read this next to the wider Kenya vs South Africa payments guide, which covers the markets around the two rails.
Who is on the other end of your API call?
On Daraja, Safaricom. Your server authenticates with Daraja and sends requests to Safaricom's endpoints; the Daraja API tutorial for beginners and the full Daraja integration walkthrough show the steps from credentials to a first sandbox call.
On PayShap, a bank or a provider. The SARB Governor said in October 2026 that at the moment, anyone who wants to access the payment system has to go through a bank[BIS: Kganyago, checked 2026-11-05]. The non-bank Authorisation Framework explains what is coming. Until it does, a South African build picks an intermediary:
- A payment provider. Stitch offers Capitec Pay, Capitec Pay VRP and PayShap Request[Stitch, checked 2026-11-05], and Ozow supports PayShap Request[Ozow blog, checked 2026-11-05]. PayShap becomes one payment method inside an API you may already use for other methods.
- Your bank. Some businesses integrate their own bank's channel. It means one relationship, but your code is tied to that bank's API.
The routes, and which banks and providers expose PayShap to developers, are compared in PayShap for developers. For a Kenyan team the mental shift is this: on Daraja you integrate the rail, on PayShap you integrate someone who integrates the rail. If you would rather hand that choice and the build to someone else, Mctaba Labs payment integration works on both sides.
How does an STK Push map to a PayShap Request?
Closely enough that the same order logic can drive both. Here they are side by side:
| Daraja STK Push | PayShap Request | |
|---|---|---|
| Who you call | Safaricom's Daraja API | Your provider or bank, which reaches the scheme |
| How you name the payer | Their M-Pesa phone number | Their bank account or an alias instead of an account number[SARB retail CBDC background note, checked 2026-11-04] |
| Where the payer approves | A PIN prompt on their phone | Their own bank's channel |
| How the result reaches you | A callback to the URL you supplied | Your provider's webhook or status endpoint |
| What you reconcile against | The M-Pesa receipt in the callback, against your reference | The provider's payment reference, against your order reference |
| Ceiling to design for | Check current limits in the Daraja production checklist | R50,000 since October 2024, with the payer's bank setting its own threshold[PayInc Business Report 2025, checked 2026-11-04] |
The Daraja column is explained properly in STK Push explained and in the end-to-end STK Push guide. The PayShap column is the subject of PayShap Request explained.
Two habits carry over unchanged. Both flows are asynchronous: your first API call starts the payment and proves nothing. And both need an order state between "created" and "paid", because the payer can ignore the prompt, decline it or approve it after your timeout.
How do you identify the payer on each rail?
On M-Pesa you collect a phone number; on PayShap you collect a bank account or an alias. That changes your checkout form, your validation and your error messages more than it changes your backend.
- Phone numbers are short, familiar and easy to validate for format. The failure you design for is the customer who types a number that is not registered for M-Pesa, or that belongs to someone else.
- Bank accounts and aliases are less familiar to customers at checkout. PayShap's pay-by-proxy feature lets you pay to an alias instead of a bank account number[SARB retail CBDC background note, checked 2026-11-04], which helps, but the customer must know their own alias. PayShap ShapIDs explained covers how aliases work.
The practical rule for a shared codebase: store the payer identifier as a typed field (phone number, account or alias), never as a bare string, and validate it per rail before you call anyone.
How does confirmation reach your server?
Through a callback on both rails, and on both rails you should not trust the callback on its own.
On Daraja, the result arrives at the callback URL you supplied with the request. Callbacks that never arrive are common enough that we keep a whole guide on them, M-Pesa callback URLs not firing. On PayShap you receive whatever your provider sends: a webhook, a status you can poll, or both. Each provider documents its own format and signature scheme, and Stitch's API is GraphQL[Stitch developer docs, checked 2026-11-05], with an alternative REST interface for creating payment requests[Stitch docs, checked 2026-11-05], so read the provider's docs rather than assuming a shape.
The same three rules keep both honest:
- Verify, then confirm. Check the signature or source of every notification, then query the payment status from the API before you release goods.
- Make handlers idempotent. Key every update on the rail's payment reference and your own order reference, so a repeated notification changes nothing.
- Reconcile daily. Match settled payments to orders from the operator's or provider's reports, not from your callback log. Transaction reconciliation for M-Pesa and payment webhooks and reconciliation for South African PSPs cover each side.
What do limits and volumes mean for your design?
They decide where each rail sits on your checkout. On PayShap, the transaction limit was raised from R3,000 to R50,000 in October 2024, and the payer's bank sets the threshold it applies[PayInc Business Report 2025, checked 2026-11-04]. So two customers paying the same invoice can hit different ceilings, and your code cannot raise either. Offer a fallback method when a PayShap Request fails for size.
Volume tells you how much of your checkout to build around each rail. PayShap is growing but still small next to cards: last year PayShap processed only about 6% as many transactions as cards, and under 40% of EFT credit volumes[BIS: Kganyago, checked 2026-11-04]. In South Africa it is one method among cards, pay-by-bank and Capitec Pay, so offer it alongside them rather than instead of them.
How do sandboxes and go-live compare?
Daraja gives you a direct path: a sandbox app on Safaricom's Daraja portal[Safaricom Daraja developer portal, checked 2026-11-05], then a production application for your shortcode. The Daraja sandbox setup guide and the production checklist cover each stage.
On PayShap, your provider sets the path. You test in its environment, go live under its merchant onboarding and inherit its timelines. The provider's documentation is the source of truth: Stitch and Ozow each have their own, and the two build guides, PayShap Request with Stitch in Node.js and PayShap Request with Ozow, follow those docs step by step.
The trade-off is clear. Daraja means more work on your side and more control. A PayShap provider means less integration work, more methods from one contract and a dependency on that provider's roadmap.
How do you build one payment layer that handles both rails?
Model the request, not the rail. A shared layer needs four pieces:
- A payment request record with amount, currency, your reference, the rail and a typed payer identifier.
- One status model that both rails map into: created, awaiting payer, paid, failed, expired. Each adapter translates its rail's statuses into it.
- Adapters per rail. A Daraja adapter that sends STK Push requests and reads callbacks; a provider adapter for PayShap Request. Neither leaks its field names into your order code.
- A vocabulary map for the team. Kenyan engineers think in C2B, B2C and B2B; South African providers speak in collections, payouts and payment methods. C2B, B2C and B2B in Daraja terms vs Paystack terms shows how that translation works between Daraja and a gateway.
The full build, one Next.js app taking both M-Pesa and PayShap, is in one codebase, two rails. If you are moving the other way, Kenyan founders entering South Africa should also read what Kenyan fintech builders get wrong about South Africa, and the bank-rail comparison in Pesalink vs PayShap.
For the regional picture beyond these two rails, see payments in Southern Africa. And when you want both rails built behind one payment layer, Mctaba Labs payment integration builds exactly that kind of shared layer.
Frequently asked questions
- Is PayShap Request South Africa's version of STK Push?
- It is the closest match in flow: your system asks for a set amount and the payer approves it. The differences are who you call, how you name the payer and how the result reaches you. PayShap Request went live in December 2024 with eight banks[PayInc Business Report 2025, checked 2026-11-04].
- Can I call PayShap directly, the way I call Daraja?
- Not as a non-bank today. As the SARB Governor put it, at the moment anyone who wants to access the payment system has to go through a bank[BIS: Kganyago, checked 2026-11-05], so you integrate a bank or a provider such as Stitch or Ozow.
- Does Daraja have a sandbox?
- Yes. Safaricom's Daraja portal lets developers create a sandbox app and test it by simulating it on an API client[Safaricom Daraja developer portal, checked 2026-11-05]. On the PayShap side you test in your provider's environment, under that provider's rules.
- What replaces the phone number when you request a PayShap payment?
- A bank account or an alias. PayShap includes a pay-by-proxy feature, so you can pay to an alias instead of a bank account number[SARB retail CBDC background note, checked 2026-11-04].
- How big is PayShap compared with cards?
- Still small. Last year PayShap processed only about 6% as many transactions as cards, and under 40% of EFT credit volumes[BIS: Kganyago, checked 2026-11-04], so plan it as one method among several.
Need this integration built?
Mctaba Labs builds payment integrations across South Africa and the region: PayShap, pay by bank, card gateways, mobile money and cross-border payouts, with the webhooks and reconciliation that keep the money matching the books.
Talk to the payments team