South Africa payment gateway

South Africa payment gateway — ZAR rails on one API, alongside the rest of the world.

topropay surfaces South African connectivity — cards, Instant EFT, DebiCheck, Snapscan, Zapper and other SARB-NPS-aligned rails — through one unified API, delivered via licensed partner providers. SA traffic settles in ZAR; cross-border traffic can convert on receipt.

Book an SA integration review Read the API docs
topropay.com/checkout/ · ZA

R 1 899,00

Choose your payment method

  • Card · Visa / Mastercard routed
  • Instant EFT SARB-NPS
  • DebiCheck (recurring) mandate
  • Snapscan · Zapper QR

Routed via topropay · partner-licensed under SARB NPS

ZAR
South African rand settlement
NPS
SARB National Payment System aligned
Local
rails via licensed partner connectivity
1 API
across SA and global methods

Key benefits

Why orchestrated payment systems in south africa win on cross-border merchants

Four outcomes that show up consistently once SA connectivity rides the same orchestration layer as the merchant's EU / US / APAC / LATAM traffic.

  1. 01

    South Africa payment gateway methods on one API

    Cards (Visa, Mastercard, Amex, Diners), Instant EFT, DebiCheck debit orders, Snapscan, Zapper and other South African rails surface through the same /v1/payments endpoint as the merchant's EU, US, APAC and LATAM methods. One integration covers SA traffic alongside the rest of the world.

  2. 02

    Licensed partner connectivity under the SARB NPS

    South African connectivity is delivered through partners with the relevant SARB licences operating under the National Payment System framework. topropay handles the routing, vault and reconciliation; the partner side handles the SA-specific bank-rail compliance.

  3. 03

    Routing and cascade on South African card traffic

    Every card authorisation runs through the routing engine in under 200ms. Soft declines cascade across the connected SA acquirer panel inside the same request — useful for cross-border card traffic where the issuer / acquirer pair matters most.

  4. 04

    One reconciliation feed for SA and global flows

    Settlements, fees, refunds and chargebacks from every connected provider — South African and otherwise — normalise into one ledger keyed off vault tokens. Finance closes the month from one export with per-region tags on every row.

How it works

From discovery to live online payment systems south africa in five stages

Five concrete stages between picking topropay and live SA traffic. Most merchants reach live status in days for hosted checkout; the slowest step is usually KYC on the partner side.

  1. 01

    Discovery on the SA buyer base

    Where the SA traffic comes from, what buyers expect (card vs Instant EFT vs DebiCheck vs Snapscan), what merchant licence is required for the vertical, and where settlement currency should land.

  2. 02

    Sub-merchant onboarding

    Onboarding through topropay's sub-merchant model; SA-specific KYC and underwriting happen through the partner side under the SARB framework.

  3. 03

    Enable methods from the dashboard

    Switch on the SA methods relevant to the merchant's buyer mix — cards everywhere as the baseline, Instant EFT for high-conversion EFT-first buyers, DebiCheck for recurring debit orders, Snapscan / Zapper for QR-friendly checkouts.

  4. 04

    Run authorisations through one API

    Every authorisation — card or local rail — POSTs to the same /v1/payments endpoint. The webhook event model is identical; vault tokens identify the customer across rails.

  5. 05

    Settle in ZAR or convert on receipt

    Settlement currency per provider is a configuration choice. SA-domiciled merchants typically settle in ZAR; cross-border merchants can convert on receipt to EUR / GBP / USD at the rail's quote.

SA methods

Online payment gateways south africa methods exposed

A sample of the SA methods exposed through topropay's partner connectivity. The full live availability per merchant is in the dashboard.

  • Cards

    • Visa
    • Mastercard
    • Amex
    • Diners

  • Instant EFT

    • Stitch
    • Ozow
    • Peach EFT secure

  • Debit orders

    • DebiCheck
    • NAEDO
    • EFT debit

  • QR & wallets

    • Snapscan
    • Zapper
    • Masterpass

  • Bank rails

    • EFT
    • PayShap (where supported)
    • Pay@ retail collections

Main use cases

Where SA payment solutions earn their keep

Six merchant shapes that share the same SA partner connectivity but stress it differently — DTC, cross-border, subscriptions, marketplaces, travel and B2B.

  • DTC SA

    South African DTC and online retail

    Cards and Instant EFT as the core checkout, with QR-based methods surfaced where the buyer profile prefers them. The hosted checkout re-orders the visible method list per shopper; conversion lifts measurably vs a card-only setup on SA-domestic traffic.

  • Cross-border

    Cross-border merchants selling into South Africa

    EU, US and APAC merchants enabling SA connectivity via the same payment gateway integration that already powers their international cards and APMs. No second console, no second reconciliation pipeline, no SA-only integration project.

  • Subs

    Subscriptions with DebiCheck mandate

    Recurring subscriptions for SA buyers via DebiCheck — the SARB-mandated recurring-debit-with-authorisation scheme. Mandate management and recurring debits run inside the recurring engine, alongside card-on-file recurring for non-SA buyers.

  • Marketplaces

    Marketplaces with SA sellers / buyers

    Per-seller payouts in ZAR via partner-licensed connectivity; buyer-side Cards / Instant EFT capture deposits. Split-payment routing preserves the per-seller ledger across rails.

  • Travel

    Travel and ticketing into SA

    High-ticket bookings benefit from cards + Instant EFT side by side; refunds run through the same API; multi-currency capture covers buyers paying from outside SA.

  • B2B

    B2B invoicing into SA counterparties

    Invoices to SA B2B counterparties settle via EFT or card; one reconciliation row per invoice regardless of rail.

Platform features

Capabilities behind the africa payment gateway integration

What the platform actually ships for SA traffic — beyond the general orchestration features shared with mainstream merchants.

  • Unified payments API

    One REST contract across SA and global methods; SDKs for web, mobile and server.

  • Local SA method coverage

    Cards, Instant EFT, DebiCheck, Snapscan, Zapper, EFT and partner-supported PayShap surfaces.

  • Hosted SA checkout

    A drop-in hosted checkout that surfaces SA methods per shopper, in the right order, with ZAR amount formatting.

  • Smart routing engine

    Per-transaction scoring on BIN, scheme, currency, country pair and risk signals — across the SA acquirer panel and the global one.

  • Cascade & retry

    Soft declines cascade to the next ranked acquirer inside the same authorisation; nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    Card data captures into our vault before it touches any underlying provider — including SA-partner-side processors.

  • DebiCheck recurring

    Mandate-authenticated recurring debits inside the same recurring-payment engine as card-on-file recurring.

  • Network tokens & SCA

    Network tokens by default; selective 3DS2 / SCA on the authorisation path for cross-border card traffic.

  • Unified reconciliation

    SA settlements, fees, refunds and chargebacks normalise into one ledger alongside the merchant's global flows.

  • ZAR settlement or conversion-on-receipt

    Settle in ZAR for SA-domiciled merchants; convert on receipt to EUR / GBP / USD for cross-border merchants who prefer it.

  • Operator portal

    One dashboard for SA authorisations, refunds, disputes and chargebacks alongside global traffic.

  • Sandbox parity

    Sandbox that mirrors production for SA flows — card 3DS, Instant EFT bank-confirmation, DebiCheck mandate scenarios.

Trust & compliance

Compliance posture for South African flows

SA connectivity rides licensed partner providers under the SARB framework; the rest of the posture is inherited from the platform's audited environment.

SARB NPS alignment
South African connectivity rides partner providers operating under the SARB National Payment System framework with the relevant authorisations.
PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans on the platform cycle; SA card traffic inherits the same posture as global card traffic.
POPIA awareness
Where the merchant handles SA buyer personal information, regional data-residency options support POPIA-aligned handling on the platform side; the merchant retains its own POPIA controller obligations.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and per partner's appetite.
DebiCheck mandate evidence
Mandate metadata captured at sign-up and retained per the SARB and PASA scheme rules.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of integration shape.

Ready to integrate

South Africa next to the rest of the world on one API.

A 30-minute SA review walks through the partner connectivity for your traffic shape, the methods that fit your buyer base, the settlement-currency policy, and a sandbox to test against before any commercial commitment.

Book an SA integration review Read the API docs

Frequently asked

Buyer questions about South Africa payment gateway integration

Questions buyers ask before committing — coverage, NPS context, DebiCheck recurring, POPIA, settlement currency, and how SA fits alongside the merchant's global mix.

  1. 01

    What does topropay offer as a south africa payment gateway?

    topropay exposes South African connectivity — cards, Instant EFT, DebiCheck, Snapscan, Zapper and other SA rails — through one unified API alongside the merchant's global methods. SA-specific connectivity is delivered through partner providers operating under the SARB National Payment System framework with the relevant authorisations.

  2. 02

    How does topropay compare to other payment gateways south africa merchants typically pick?

    Most payment gateways south africa merchants pick (Peach Payments, Yoco, PayFast, iVeri and similar) focus on the SA market specifically. topropay sits at a different shape — one unified API across SA + global, with multi-acquirer routing on the back end. Merchants who run only SA traffic may not need orchestration; merchants who run SA alongside other regions typically do.

  3. 03

    What are the national payment systems in South Africa?

    National payment systems in South Africa is governed by the South African Reserve Bank (SARB) under the National Payment System Act, with operational rules managed by the Payments Association of South Africa (PASA). It covers the rules, infrastructure and oversight for clearing and settling payments domestically — card schemes, EFT, debit orders, real-time payments (PayShap), and the upcoming evolution of the NPS framework.

  4. 04

    How does topropay handle payment systems in south africa specifically?

    Payment systems in south africa on topropay are accessed via partner providers with the relevant licences and operational compliance under the SARB / PASA framework. The merchant integrates against topropay's unified API; the partner side handles the SA-specific bank-rail compliance and message exchange.

  5. 05

    Is topropay an africa payment gateway covering the wider continent?

    topropay's africa payment gateway coverage centres on South Africa via partner providers, with neighbouring corridors addressable through the same partner connectivity. For Nigerian, Kenyan or East-African connectivity specifically, the platform reaches those markets through regional partner gateways under the same unified API model. Coverage per market is shown in the merchant dashboard.

  6. 06

    What are the typical online payment gateways south africa merchants integrate with?

    Typical online payment gateways south africa merchants integrate with include Peach Payments, Yoco, PayFast, iVeri, Adumo, Mastercard Payment Gateway Services (MPGS) via local acquirers, and bank-specific gateways from ABSA, Standard Bank, FNB and Nedbank. topropay sits one layer above — orchestrating across the connected partner panel rather than being a direct SA acquirer itself.

  7. 07

    Is the national payment system south africa relevant for an EU merchant selling into SA?

    The national payment system south africa is relevant to the extent that the SA-side rails the merchant accepts (Instant EFT, DebiCheck, card schemes on SA acquirers) all clear through the NPS infrastructure. For an EU merchant, that detail is abstracted away by the partner — the merchant integrates against topropay's API; the partner handles NPS clearing.

  8. 08

    What is a national payment gateway in the SA context?

    A national payment gateway in the SA context is a gateway that connects to the SARB-NPS-aligned rails (Instant EFT, DebiCheck, EFT, the card-scheme acquirers). topropay's SA connectivity acts as a national-payment-gateway-shape for the merchant — one integration reaches the NPS-aligned rails plus card and QR methods.

  9. 09

    What payment solutions south africa work for recurring billing?

    Payment solutions south africa for recurring billing typically combine DebiCheck (mandate-authenticated debit orders, the SARB-mandated recurring scheme) with card-on-file recurring (network tokens, scheme updaters). topropay's recurring-payment engine handles both inside the same API.

  10. 10

    What online payment systems south africa is topropay competitive against?

    topropay competes more on the cross-border / orchestration shape than on direct SA-only integrations. A merchant whose volume is 100% SA may prefer a direct local PSP; a merchant whose SA traffic is part of a wider global mix typically gains more from orchestration that collapses SA + global into one API.

  11. 11

    Can SA-domiciled merchants settle in ZAR through topropay?

    Yes — SA-domiciled merchants settle in ZAR via the partner side. Cross-border merchants who prefer not to hold ZAR can turn conversion-on-receipt on for SA receipts; the platform converts incoming ZAR to the merchant's settlement currency at the rail's quote.

  12. 12

    Does the platform support DebiCheck recurring debits specifically?

    Yes — DebiCheck recurring debits run through the recurring-payment engine alongside card-on-file recurring. Mandate evidence is captured at sign-up and retained per SARB / PASA rules; recurring events fire signed webhooks into the merchant's stack.

  13. 13

    What about POPIA — does topropay handle SA personal-information compliance?

    POPIA (Protection of Personal Information Act) covers SA personal information. topropay's data-handling supports regional data-residency options for merchants under regulators that require it; the merchant remains the data controller for the buyer personal information it collects, and topropay acts as processor for the data it handles on the merchant's behalf. The merchant retains its own POPIA controller obligations.

  14. 14

    Are there licensing constraints on what SA verticals can be supported?

    Yes. Licensed gaming, regulated financial services and other compliance-bound SA verticals are supported only where the operator holds the relevant SA licence (NGB, FSCA, etc.). Unlicensed gambling, illicit substances and other grey-market verticals are out of scope regardless of integration shape, same as for every other region the platform covers.

  15. 15

    How long does an SA integration typically take?

    An SA integration typically reaches a live hosted-checkout state in days; a fully embedded integration takes weeks. The slowest step is usually onboarding (KYC / KYB on the partner side under the SARB framework), not the engineering work on the merchant side.

Related

Related on the topropay platform