March 2026 marked three years since PayShap launched, PayInc’s answer to low-cost, real-time payments and its push for greater financial inclusion in South Africa. Growth has followed, interest has grown, and the platform has quietly embedded itself into millions of banking apps. Yet businesses remain genuinely unsure how to incorporate it into their payments or collections operations, and that uncertainty is worth unpacking.
The original intent
PayShap was designed to displace costly cash handling in informal and peer-to-peer transactions – paying a contractor after they fixed a leak, or splitting a dinner bill with friends in real time. The rail is genuinely fast, living up to its promise of speed, but inconsistent fees and patchy consumer education have caused it to smoulder rather than ignite.
Accessibility is broadly there. If you are reading this, your bank has likely already provisioned your ShapID inside your banking app – most commonly your cell number. For lower-value payments, most banks come in under R7, with some like TymeBank offering PayShap for free. Fees are still higher than they need to be to truly displace cash, but the direction of travel is encouraging.
Where businesses are already winning
While probably not part of the original vision, the clearest commercial benefit of PayShap for businesses lies in instant business-to-consumer (B2C) payouts. Think any business that needs to put money into consumers’ hands immediately – an insurer paying out a claim the moment it’s approved, a microloan provider that promises funds within minutes, or a gaming platform that settles winnings the second you click withdraw.
Traditionally, these transactions attracted hefty Real Time Clearing (RTC) fees – the charges banks levy for moving money between accounts outside of standard batch processing windows. According to Standard Bank’s published consumer pricing, a PayShap disbursement under R2 000 now costs around R7, compared to as much as R40 for a traditional real-time transfer. For any business processing thousands of payouts a month, that is a significant saving. PayShap also has account verification built in – confirming who a ShapID (typically a registered cell number) belongs to before payment – eliminating what was previously a separate cost.
The payments acceptance challenge
The biggest hurdle to using PayShap as a method to take payment – compared to a card machine or standard Electronic Funds Transfer (EFT) – is the fee logic. In a card payment, the consumer pays nothing to swipe or tap, the business absorbs that cost. Because PayShap charges the payer, asking consumers to cover a fee in an environment where they never used to pay one, is a difficult expectation to set.
Convenience is another obstacle. Consumers have grown accustomed to tapping their phones, smartwatches, or cards on terminals. The Payments Association of South Africa (PASA)’s QR standardisation forums are working to address this by developing a standardised QR code that would allow merchants to accept PayShap payments the way they currently accept SnapScan or Zapper. For this to work properly, though, you would need near-zero cost pricing for consumers and a seamless experience that genuinely rivals tapping a device, and that combination is not quite there yet.
Is PayShap Request to Pay the answer?
Request to Pay (RTP) is an extension of the PayShap rail that allows a business or individual to send a payment request to any registered ShapID and receive funds instantly. A few banks have gone live with the feature, though it will go through teething phases as institutions align their transaction limits, default ShapID logic, and fees.
For small, informal, or one-off transactions, RTP creates a neat way for traders and contractors to collect on invoices without hitting consumers with heavy fees – truly addressing PayInc’s financial inclusion mandate. For larger payments, the existing fee structure may still push payers towards a free, if slower, EFT.
For subscription or instalment businesses, RTP can serve as a useful backup tool if a client misses a payment. For regular monthly collections, however, it lacks the security and reliability of DebiCheck – the bank-mandated debit order system that holds a digital mandate from the account holder, and has built-in tracking capabilities if a first collection attempt fails.
There is a window for PayShap RTP to serve collections that are too small to justify the cost of DebiCheck. It is worth noting, though, that in late 2025, Capitec and fintech Stitch launched Variable Recurring Payments (VRP) – a recurring payment capability for Capitec’s more than 25 million active customers. For businesses collecting from that base, VRP may already cover some of the same ground, and it’s a space worth watching as other banks develop their own recurring payment offerings.
Hit or miss?
Three years in, PayShap is neither the revolution it was promised to be nor the missed opportunity its critics suggest. It is a payment rail that has found its clearest purpose in B2C payouts, is steadily building the infrastructure for merchant acceptance, and is beginning to wrestle seriously with the fee problem that has held it back from day one.
For businesses, the honest answer to the question in the headline is: it depends on what you are trying to do. If you are paying out, the answer is almost certainly yes. If you are trying to collect, the use case is real but narrowing – particularly for small, informal, or one-off transactions where the alternatives are worse. And if you are waiting for PayShap to replace your card terminal, the rails are being laid, but the wait may be a little longer yet. The next three years, though, should be considerably more interesting than the last.
Written by Derick Truscott, CFO, Hyphen