Customers

Customers and the payment methods saved against them, which is what recurring charges reference.

Customer payment methods

Save, list, and manage customer payment methods for recurring charges

Supported payment methods

Orchestration supports cards, wallets, and numerous other payment methods. Filter by country or category to find what you need. Methods appear at checkout when they are enabled on your business profile. Saved cards can be reused for one-click checkout and recurring billing.

The table lists refund support per method. For how to process a refund - via the Dashboard or the API - and how long refunds take to complete, see Manage transactions.

Country

Category

Payment methodSupported countriesSupported currenciesRefundsTesting
Card: VisaSouth Africa, Kenya, MauritiusSouth Africa: ZAR Kenya: KES and depending on the acquirer, EUR and USD Mauritius: MUR and depending on the acquirer, EUR and USD✅ Yes, full or partialInstructions
Card: MastercardSouth Africa, Kenya, MauritiusSouth Africa: ZAR Kenya: KES and depending on the acquirer, EUR and USD Mauritius: MUR and depending on the acquirer, EUR and USD✅ Yes, full or partialInstructions
Card: AmexSouth Africa, Kenya, MauritiusSouth Africa: ZAR Kenya: KES Mauritius: MUR and depending on the acquirer, EUR and USD✅ Yes, full or partialInstructions
Card: DinersSouth Africa, MauritiusSouth Africa: ZAR Mauritius: MUR and depending on the acquirer, EUR and USD✅ Yes, full or partialInstructions
Apple PaySouth Africa, MauritiusSouth Africa: ZAR Mauritius: MUR, USD✅ Yes, full or partialInstructions
Google PaySouth AfricaZAR✅ Yes, full or partialInstructions
Samsung PaySouth AfricaZAR✅ Yes, full or partialInstructions
PayShapSouth AfricaZAR✅ Yes, full or partial (one refund only)Instructions
Peach EFTSouth AfricaZAR❌ NoInstructions
Capitec PaySouth AfricaZAR❌ NoInstructions
PayflexSouth AfricaZAR✅ Yes, full or partialInstructions
ZeroPaySouth AfricaZAR❌ NoInstructions
FloatSouth AfricaZAR✅ Yes, full or partialInstructions
Happy PaySouth AfricaZAR✅ Yes, full or partialInstructions
PayJustNowSouth AfricaZAR⚠️ Full or partial (POS only - eCommerce refunds not yet supported)Instructions
Scan to PaySouth AfricaZAR✅ Yes, full onlyInstructions
1VoucherSouth AfricaZAR✅ Yes, full or partialInstructions
MobicredSouth AfricaZAR✅ Yes, full or partialInstructions
RCSSouth AfricaZAR✅ Yes, full or partialInstructions
MoneyBadgerSouth AfricaZAR✅ Yes, full or partialInstructions
M-PESAKenyaKES❌ NoInstructions
blink by EmtelMauritiusMUR❌ NoInstructions
MCB JuiceMauritiusMUR❌ NoInstructions
MauCASMauritiusMUR❌ NoInstructions

Payment method details

Bank transfer

PayShapInstant bank payments with participating-bank limits

PayShap enables customers to make instant payments using their banking apps.

PayShap supports one refund per transaction only. If you perform a partial refund, you cannot perform another refund later. Availability is limited to specific participating banks with different transaction limits.

BankSupport statusTransaction limit
AbsaSupportedR3,000
Discovery BankSupportedR3,000
FNBSupportedR3,000
NedbankSupportedR50,000
TymeBankSupportedR5,000
African BankNot supportedNot applicable
CapitecNot supportedNot applicable
InvestecNot supportedNot applicable
Standard BankNot supportedNot applicable

Testing instructions

Peach EFTPay by bank transfer. Can include Capitec Pay and Absa Pay in the Pay by Bank user interface.

Pay by bank transfer. Can include Capitec Pay and Absa Pay in the Pay by Bank user interface.

When paying large amounts, customers should ensure their bank payment limits are high enough to cover the amount.

Testing instructions

Capitec PayRisk category affects how merchants identify customers

Capitec Pay may appear as part of the Pay by Bank experience when both are enabled.

Capitec categorises merchants as either high or low risk. Options differ by risk category:

Risk categoryNotes
LowSupports paying with ID and phone number.
HighSupports paying with a merchant-provided verified ID that the customer cannot edit. Does not support paying with phone number.

For high-risk merchants, provide the verified South African ID number on the payment (for example via customer identity fields). Capitec Pay does not support passport numbers for low- or high-risk merchants.

Testing instructions

Absa PayRisk category affects how merchants identify customers

Absa Pay may appear as part of the Pay by Bank experience when both are enabled.

To pay with Absa Pay, customers must have the Absa banking app. For registration guidance, see Absa: How to register for the Absa banking app.

Absa categorises merchants as either high or low risk. Options differ by risk category:

Risk categoryNotes
LowSupports paying with ID.
HighSupports paying with a merchant-provided verified ID that the customer cannot edit.

For high-risk merchants, provide the verified South African ID number on the payment (for example via customer identity fields). Absa Pay does not support passport numbers for low- or high-risk merchants.

Testing instructions

Pay later

PayflexBuy now, pay later with default amount limits

Payflex supports payments between R10 and R50,000 by default. To request a higher limit, contact support.

See the Payflex documentation for details on how to configure the Payflex instalment calculator.

Testing instructions

ZeroPayMinimum payment amount R30

The minimum amount you can pay using ZeroPay is R30.

Download the ZeroPay instalment calculator.

Testing instructions

FloatPayments between R1 and R99,000

Float supports payments between R1 and R99,000.

Testing instructions

Happy PayBuy now, pay later with optional storefront widgets

See the Happy Pay documentation for details on how to configure Happy Pay's payment widget.

Testing instructions

MobicredRevolving credit with optional instalment widgets

See the Mobicred documentation for details on how to configure the Mobicred instalment widget.

Testing instructions

Wallet

Apple PayMerchant account and Peach configuration requirements

To offer Apple Pay with Orchestration, you must:

  • South Africa: Have an FNB, Nedbank, or Standard Bank merchant account.
  • Mauritius: Have an MCB or Absa Mauritius merchant account.
  • Send Peach Payments your Apple Pay merchant ID and certificates. Peach Payments configures these for your account.

Testing instructions

Google PayMerchant account and Peach configuration requirements

To offer Google Pay with Orchestration, you must:

  • Have an Absa, FNB, Nedbank, or Standard Bank merchant account.
  • Send Peach Payments your Google Pay merchant ID. Peach Payments configures this for your account.

Testing instructions

Samsung PayMerchant account and Peach configuration requirements

To offer Samsung Pay with Orchestration, you must have a Nedbank or Standard Bank merchant account.

Testing instructions

Scan to PayQR payments with debit-card refund limits

Refunds are not allowed on debit cards. You can process a reversal on the debit card using the Scan to Pay service, but you must complete it within six hours of the original transaction.

Multiple banking and payments apps support Scan to Pay QR codes, including Nedbank Money, Standard Bank, Absa Banking App, Capitec Bank, FNB Banking App, RMB Private Bank App, Scan to Pay, VodaPay, Telkom Pay Digital Wallet, and Spot Money - Mobile Banking.

Testing instructions

Crypto

MoneyBadgerCrypto payments with specific refund rules

MoneyBadger enables you to accept crypto payments from Bitcoin Lightning Network, Luno, VALR, Binance, and Bybit wallets.

Refunds:

  • You can only refund amounts equal to or more than R25 (including partial refunds).
  • For Bitcoin Lightning Network wallets (not required for Luno, VALR, Binance, or Bybit), customers must provide their wallet address during the initial payment if they want to refund later. Otherwise refunds fail with response code 800.100.195.

Peach Payments bases the refund amount on the item’s Rand (ZAR) price at the time of purchase, then converts to crypto using the exchange rate at refund time. The customer might receive a different amount of crypto than they originally paid.

  • Example: customer paid R100 (0.00004 Bitcoin at purchase).
  • Refund value: R100.
  • Customer receives R100 worth of Bitcoin at the current exchange rate.

Testing instructions

Payment method lifecycle

Payment methods are saved during checkout and can be reused for future charges. This enables one-click checkout and recurring billing without requiring customers to re-enter their card details.

When to save cards

  • Subscriptions - Automatic recurring billing
  • One-click checkout - Faster repeat purchases
  • Marketplaces - Multiple purchases from same buyer
  • Free trials - Charge when trial ends

Key concepts

payment_method_id

Unique identifier for a saved card (pm_xxx)

customer_id

Links payment methods to a customer (cus_xxx)

setup_future_usage

Tells Orchestration to save the card (on_session / off_session)