Ozow Hub
On this page4 sections

PayShap RequestPayShap Request The request side of PayShap. Rather than the payer pushing money, the payee asks for it: the payer receives a request and approves it in their own banking app, and the funds move once they do. Enabled by Ozow on request rather than by default.payshap.co.za lets you request a payment and have your customer approve it instantly in their own banking app.

Your customer identifies themselves with a cellphone number or a bank account number. They don't enter card details, they don't download anything, and they never share banking credentials with you or with Ozow; the approval happens inside their bank's own app.

How your customer pays

  1. Your customer chooses Pay by BankPay by Bank The payer authorises the payment inside their own banking app or online banking, and the funds move from their bank account. No card is involved and no card details are entered. at checkout and selects PayShapPayShap South Africa's rapid payments service, run by the banks. Low-value payments clear in seconds, and the recipient can be identified by a ShapID instead of by an account number.payshap.co.za.
  2. They provide their cellphone number or bank account number.
  3. A payment request appears in their banking app.
  4. They approve it there.
  5. The customer returns to your site.

If you've requested a standalone PayShap button, your customer reaches step 2 directly instead.

Enabling PayShap Request

Speak to your account manager to have PayShap Request enabled on your account.

Once enabled, it appears on the Ozow payment page automatically. No separate integration is needed; it works through the Ozow integration you already have.

If you operate in a high-risk industry, Customer Identity VerificationCustomer Identity Verification Checking that the payment instrument belongs to the natural person making the payment. Ozow requires it for merchants it has classified as high-risk, on Pay by Bank, Absa Pay, Capitec Pay, Nedbank Direct EFT, FNB Payment Requests and PayShap Request, and can disable those methods where it is not implemented correctly. is mandatory for PayShap Request. It changes what you build, so read Customer Identity Verification before you start rather than after.

Things to know

Your customer needs their phone. The approval happens in their banking app, so they need the device that app is on. Consider this for desktop checkouts, particularly if your customers typically buy from a work computer.

Not every bank participates. PayShap coverage has grown steadily but it isn't universal. A customer whose bank isn't on the network can't pay you this way, so keep your other payment methods available.

PayShap sits inside your Pay by Bank flow by default. Your customer selects Pay by Bank and then chooses PayShap from there: by default it isn't a separate option on the payment method screen unless you ask for one. If you're promoting PayShap to your customers, that's worth knowing: they won't see it named until they're a step into the flow.

Refunds go back to the customer's bank account. PayShap Request payments can be refunded. See Refunds.

Integrating PayShap Request

PayShap Request works with every Ozow integration method, and nothing PayShap-specific is required; once it's enabled on your account, it appears on the Ozow payment page automatically.

Standalone PayShap button. Available on request. By default PayShap appears inside the Pay by Bank flow rather than as its own option, so if you want a "Pay with PayShap" button that goes straight there, ask your account manager to enable it, then pass PayShap Request's institutionId.

There's a single institutionId for PayShap as a whole. There are no bank-specific PayShap identifiers, so you can't send a customer straight to PayShap at a particular bank: your customer chooses their bank inside the PayShap flow.

See Standalone payment buttons.

PayShap icons for your checkout buttons are in Brand assets.

Last updated