Why PayShap matters more than it looks

PayShap's headline is real-time interbank payment addressed by a proxy — usually a cellphone number. To anyone with a banking app, that reads as a convenience feature. In the market we build for, it removes the two things that actually stop a transfer happening.

• You no longer need someone's account number, which people do not know and cannot safely read out over a taxi rank.
• The money arrives in seconds, so the person receiving it does not have to trust that it is coming.

What it means for a shop

It means one QR code on the counter serves everybody. A customer with a WynkPay wallet settles closed-loop; a customer with any South African bank app pays the same code over PayShap. The shopkeeper does not have to ask which bank anyone is with, and nobody is turned away because they are on the wrong network.

The part we had to build carefully

The scheme is still evolving, and proxy handling changes between phases. We put the whole PayShap integration behind a single port interface so that a scheme upgrade is a configuration change on our side rather than a rewrite that reaches the app on a shopkeeper's phone.