Standalone buttons Deprecated

A standalone button shows one Ozow payment method as its own option on your checkout page, for example Capitec PayCapitec Pay Capitec's own payment method. The payer gives a cellphone, account or ID number rather than card details, and approves the payment in the Capitec app, so no card number and no banking login is ever entered at checkout. It gets its own button rather than sitting inside the bank list, and it requires Customer Identity Verification.Capitec or card. Customers don't land on a general payment page and choose from there. They click the method they recognise and go straight into that payment flow.

Customers who can't see how they can pay at checkout hesitate or leave. Most customers look for logos they know, and a standalone button puts that logo in front of them.

Why use standalone buttons#

Instant recognition. A familiar logo shows the customer straight away that their preferred way to pay is accepted.

Brand familiarity builds trust. A payment brand customers know reassures them when they decide whether to pay.

Customers expect to see their method. If customers don't see their payment method, they assume it isn't available. A standalone button removes that doubt.

One less step. The customer skips the method-selection screen, so there's less friction between payment intent and a completed payment.

What it looks like#

Standalone buttons work anywhere a customer chooses how to pay. Show them alongside the general Ozow button, not instead of it, so customers can still reach every other method enabled on your account.

E-commerce checkout example#

Wallet top-up example#

What the customer sees#

When a customer taps a standalone button, they skip choosing a payment method and a bank and go straight to that method's screen. Here's the journey for Capitec Pay.

Integration guide#

Add selectedBankId to your payment request. When the selectedBankId is valid, Ozow sends the customer directly to that payment method.

Post the request to https://api.ozow.com/postpaymentrequest (staging: https://stagingapi.ozow.com/postpaymentrequest).

{
  "siteCode": "YOUR_SITE_CODE",
  "countryCode": "ZA",
  "currencyCode": "ZAR",
  "amount": "100.00",
  "transactionReference": "ORDER-001",
  "bankReference": "ABC123",
  "cancelUrl": "https://yourstore.com/cancel",
  "errorUrl": "https://yourstore.com/error",
  "successUrl": "https://yourstore.com/success",
  "notifyUrl": "https://yourstore.com/notify",
  "isTest": false,
  "selectedBankId": "YOUR_BANK_ID",
  "hashCheck": "YOUR_GENERATED_HASH"
}

Include it in the hash#

selectedBankId is field 18 in the hash concatenation order. Add it directly after isTest (field 17) in the concatenated string. Only include it when you send it in the request. If it's missing from the hash or in the wrong position, the hash check fails.

• Use a card standalone button. It opens a payment screen where customers can pay by card, Apple Pay or Google Pay.
• Use Embedded Wallet to show Apple Pay and Google Pay as their own buttons on your checkout.

Next steps#

1. Confirm your enabled methods. Check your payment flow to see which payment methods are enabled on your account. 2. Get the official artwork. Download the button for each method from Logos and branding. Don't recolour, stretch or rotate it. 3. Add the buttons and pass the identifier. Place each standalone button next to the general Ozow button and send the matching selectedBankId in the payment request. 4. Test before going live. Confirm each button opens the right method. 5. Go live.