Switching answers “yes or no” in real time. Clearing works out who owes whom across millions of transactions before anyone moves central-bank money. Two different jobs, often confused — and in South Africa, both now run under a reshaped operator.
Switch = decide now. Clear = reconcile and net. Settle = move the money.
Switching is the real-time routing of a transaction to the party that can authorize it — the terminal asks, the switch finds the issuer, the issuer says yes or no, the answer comes back. It happens in milliseconds and moves no money; it moves a decision.
Clearing is the exchange and reconciliation of transaction records between institutions to calculate what each owes the other. It batches and nets; it produces the figures that settlement then acts on. Clearing determines the obligation; settlement (a separate stage) discharges it. Confusing these three is the single most common payments-architecture mistake.
A router with rules, optimised for latency and uptime.
An authorization switch is a high-availability router with rules. It takes an inbound auth request, identifies the destination from the card range or account, applies routing logic (least-cost routing, stand-in, fraud rules), forwards it, and relays the response. Latency and uptime are everything — a switch that is slow or down stops commerce.
| Function | What the switch does |
|---|---|
| Routing | Resolve issuer/destination from card range (BIN) or account and forward |
| Protocol handling | Speak ISO 8583 (cards) or ISO 20022 (newer rails) on each leg, translating if needed |
| Stand-in (STIP) | Authorize on the issuer’s behalf, within limits, when the issuer is unreachable |
| Least-cost routing | Pick the cheapest valid network for a transaction where multiple are possible |
| Fraud / velocity | Apply real-time rules before forwarding |
Clearing turns a flood of transactions into a few net numbers.
After authorizations accumulate, clearing exchanges the transaction records between institutions and computes net positions — for each pair (or against a central counterparty), the single amount one owes the other. Clearing runs in cycles (windows): records are submitted, validated, matched, and netted; the net figures are handed to settlement.
An approved auth is a promise; the clearing record (presentment) is the instruction to actually move value. Auths can expire, partially clear, or be reversed before they ever clear.
Without netting, every transaction would need its own settlement. Netting collapses millions of obligations into a handful of net positions — dramatically reducing settlement volume and liquidity needed.
Between clearing and settlement, obligations are calculated but unfunded. That gap is where settlement risk lives (see the Settlement leaf).
PCH = the rulebook + arrangement; PCH SO = the operator that runs the clearing.
A payment clearing house (PCH) is the arrangement — rules plus infrastructure — under which a set of participants clear a particular payment stream (e.g. EFT, card, instant). The body that runs the technical clearing for a PCH is the PCH System Operator (PCH SO). The PCH defines the scheme rules; the PCH SO operates the switch and clearing engine that enforces them.
Above the PCHs sits the national payment system’s governance — historically a payments association, increasingly the central bank directly. The PCH SO does not settle: it hands net positions up to the settlement system, which moves central-bank money.
BankservAfrica is now PayInc, half-owned by the SARB, on the way to a national payments utility.
South Africa’s clearing has run through BankservAfrica, the national automated clearing house (founded 1972), acting as PCH System Operator for the major payment streams. As of 2025–26 the picture has shifted materially:
BankservAfrica rebranded as PayInc, signalling a shift toward a broader public payments utility rather than a bank-owned ACH.
The South African Reserve Bank acquired a 50% stake in PayInc, moving the operator toward a centralised National Payments Utility (NPU) providing open infrastructure to banks and non-banks alike.
Under the SARB’s Payments Ecosystem Modernisation (PEM) programme, PayInc is set to own scheme governance, rules, and participation requirements — consolidating roles previously spread across the industry and PASA.
PSPs licensed to operate in South Africa are expected to establish processing infrastructure that clears domestic transactions on-soil rather than offshore — a sovereignty requirement reshaping where clearing physically happens.
Low-value payments modernisation in SA is shifting from bank-consortium-driven to regulator-led. If your roadmap assumed an industry body sets the pace, re-check — the SARB and PayInc increasingly do.
Three stages, three reconciliations. And in SA, a moving operator.
Get the auth/clearing/settlement boundary right in your architecture or you will build the wrong reconciliation. A surprising number of systems treat an authorization as a completed payment — then cannot explain why authorized totals never match cleared or settled totals. They are different stages with legitimate divergence (reversals, partial clearings, expiries). Design for three sets of numbers, not one.
Auth vs clearing vs settlement should each reconcile independently. The differences are where exceptions, fraud, and bugs surface first.
Scheme rules, participation requirements, and the on-soil processing expectation are in active flux under PEM. Connectivity and compliance assumptions made before 2025 need revalidating against the new operator and the SARB’s direction.
If your books assume auth = money, every reversal and clearing adjustment looks like a discrepancy, your liquidity forecasting is wrong, and settlement breaks are buried in noise. This is a foundational error, not a tuning issue.