Accept Ozow
without building the integration
Ozow is a South African pay-by-bank provider. Instead of entering card details, the customer picks their bank at checkout, authorises the payment inside their own online banking session, and the merchant is notified in real time. Because no card is involved there is nothing to charge back and no card data touches the merchant's site.
- ZAR
- Region
- South Africa
- Methods
- 2
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Ozow in summary
- Coverage
-
- South Africa
Among the markets Ozow serves — their own list is authoritative (opens in new tab).
- Currencies
-
- ZAR
Among those supported. Which ones your account can charge in depends on its registered country.
- Supported banks
-
- FNB
- Absa
- Standard Bank
- Nedbank
- RMB
- Capitec
- TymeBank
- Investec
- Discovery Bank
- African Bank
- Fees
- Set and billed by Ozow, who publish current rates on their own site (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab)
Written against Ozow's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, Ozow's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Instant EFT
Customer authorises a real-time bank transfer during checkout
Bank API payments
Direct bank-API rails where the customer's bank supports them
What PaymentHood handles for you
A direct Ozow integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- API key and site code, signed per request; credentials stay server-side in PaymentHood
- Webhook security
- Signed notification, validated before the order is released
- Payment verification
- Server-side status re-check against Ozow before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Ozow is unreachable
- One reconciliation view across Ozow and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use Ozow on your platform
Install the free PaymentHood plugin for your store, then enable Ozow in your dashboard.
Connecting Ozow takes three steps
Open your Ozow account
Register directly with Ozow and complete their onboarding. Funds settle from Ozow into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Ozow API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and Ozow appears as a payment option. Test in sandbox, then switch to live.