The Green Tick Is Not a Bank Transfer
Card payment authorisation, clearing and settlement are three distinct events that most merchants, developers and even policy professionals routinely conflate — and the consequences of that confusion range from misconfigured payout schedules to flawed financial infrastructure decisions. When a customer taps a card at a terminal or completes a checkout flow online, the confirmation appears in under a second. What actually moved was not money. It was a message.
The funds themselves travel a longer, more fragmented path — through a gateway, a processor, an acquiring bank, a card network, an issuing bank, and in some markets an entirely separate legacy banking rail before they reach the merchant's business account. Understanding where the abstraction ends and the actual accounting begins is essential for anyone building payment infrastructure, advising on financial compliance or designing merchant-facing software.
According to a detailed breakdown published by Silicon Canals, the speed visible at the point of sale is produced by contracts and technical specialisation behind the terminal, not by instantaneous fund movement across every ledger in the chain.
What Actually Happens During Authorisation
Take a customer paying €5 for a coffee with a contactless card. The terminal passes transaction details to the merchant's payment provider. A gateway packages and encrypts the data. A processor or acquirer routes an authorisation request through the relevant card network — Visa, Mastercard or a domestic scheme — to the bank that originally issued the card.
The issuing bank checks the account balance or credit limit, validates the card status, and applies its own fraud and risk rules. It sends back an approval or decline through the same chain in reverse. On approval, it places a hold on the cardholder's available funds, reducing what they can spend — but it does not yet transfer that €5 anywhere.
The European Central Bank's payments glossary defines the card issuer as the institution that authorises point-of-sale transactions and guarantees conforming payments to the acquirer under the scheme's rules. The acquirer, in turn, is defined as the entity to which the merchant transmits the information needed to process the card payment. That guarantee is what allows the merchant to hand over the goods without waiting for a confirmed bank transfer — it is relying on an approved obligation within a governed network, not on received cash.
"The architecture of card payments was deliberately designed to decouple transaction speed from fund finality," notes industry payment infrastructure analyst commentary cited in the ECB's 2025 report on European card payments. "That design choice explains both the system's scalability and many of the compliance complexities that arise around it."
How Clearing Converts Individual Purchases Into Net Institutional Positions
After authorisation comes capture and clearing. The merchant submits completed transactions — typically in a batch — through its provider. The card network then reconciles the details, applies applicable rules and fees, and calculates what each participating issuer and acquirer owes the other. The ECB formally defines clearing as the reconciliation and confirmation of transfer orders prior to settlement, potentially including netting and the establishment of final positions.
Mastercard's published documentation on its switching operation separates this into three distinct systems: an authorisation platform that carries initial requests and responses; a Global Clearing Management System that exchanges transaction details and assesses fees; and a Settlement Account Management system that calculates each issuer's and acquirer's net position and facilitates the actual transfer of funds. Mastercard's technical specifications portal documents these systems in detail.
Netting is central to why this works at scale. Rather than sending a separate interbank transfer for every individual coffee, train ticket and subscription renewal, the scheme offsets large volumes of obligations and settles the resulting net totals between participants. A bank that has issued thousands of cards used at a single merchant chain does not send thousands of separate micropayments — it sends one net settlement amount. The customer sees one purchase. The institutions see one entry inside a much larger accounting cycle.
Settlement and Merchant Payout: Why These Are Not the Same Event
This is where the operational reality diverges most sharply from merchant expectations — and where developers building platform integrations most frequently encounter edge cases. Settlement is the moment when the financial obligations between the issuer and acquirer are discharged according to the card scheme's arrangements. Merchant payout is when the provider sends available funds to the merchant's ordinary business bank account. These are conceptually and often temporally separate events.
A modern payment provider may credit the merchant's internal balance while funds are still pending at the scheme level, make them available after a configurable settlement delay, deduct processing fees, reserves and any refund offsets, and then pay an aggregated net amount to the merchant's bank on a pre-agreed schedule. Stripe's payout documentation illustrates this precisely: a successful charge first appears in a pending balance, moves to available after the applicable settlement period (which varies by country and payment method), and a payout then moves the available balance to an external bank account.
This is also where older banking rails may enter a card payment's story. In the United States, payment providers can use an Automated Clearing House (ACH) credit to deliver aggregated funds into a merchant's account. The ACH network was established in the 1970s and remains a batch-oriented, store-and-forward system — though it has added faster settlement windows in more recent years, as documented by Nacha, the ACH network's governing body. In Europe, the equivalent final-leg transfer may travel over SEPA infrastructure. The specific rail depends on provider, currency, market and the banks involved.
| Stage | What Happens | Who Is Involved | Typical Timing |
|---|---|---|---|
| Authorisation | Issuer approves or declines the transaction and places a hold | Gateway, processor, card network, issuer | Milliseconds |
| Capture | Merchant confirms the transaction for settlement submission | Merchant, acquirer | Immediate to hours |
| Clearing | Network reconciles transaction details, calculates net positions | Card network, issuers, acquirers | Same day to next day |
| Settlement | Interbank obligations are discharged under scheme rules | Issuing and acquiring banks, scheme | 1–2 business days |
| Merchant Payout | Provider sends net available funds to merchant bank account | Payment provider, domestic rails (ACH/SEPA), merchant's bank | 1–3 business days |
Why Multiple Companies Can Touch a Transaction Without Any of Them Holding the Money
A common source of confusion for developers integrating payment APIs is the difference between data flow and fund flow. Several entities handle a transaction without possessing the funds at any point. The payment gateway transmits and encrypts data — it is a routing and security layer, not a vault. A processor operates the connection between acquirer and issuer. The card network supplies rules, routing, clearing and settlement services but does not hold the cardholder's account. A payment facilitator may aggregate dozens of small merchants under one acquiring relationship and maintain its own internal ledger of their sub-balances.
The ECB's 2025 report on European card payments describes processors specifically as companies positioned between the merchant's acquirer and the card issuer, performing tasks involved in authorising and processing payments. The same report found that most EU countries rely on international card schemes — an observation with direct relevance to discussions about European digital sovereignty and the policy debate around building independent payment infrastructure.
"The apparent simplicity at the terminal is produced by contracts and technical specialisation behind it. Speed at the edge does not require every ledger in the chain to update finally at the same moment."
— Payment infrastructure analysis, Silicon CanalsFor compliance professionals, this layered structure raises important questions under GDPR and PCI DSS. Transaction data — cardholder names, purchase details, device identifiers — passes through multiple entities across potentially different jurisdictions. Each handoff is a potential scope expansion for data protection obligations. Understanding which entity acts as a data processor versus a data controller in each segment of the chain is not merely an academic exercise; it is a compliance requirement under European data protection law.
ISO 8583, Batch Rails and the Structural Reasons Legacy Infrastructure Survives
Card systems are not simply transfer mechanisms. They must support authorisation holds, delayed capture, partial captures, reversals, refunds, dynamic currency conversion, chargebacks and multi-party disputes — all while operating across millions of merchants and thousands of financial institutions running different software in different legal systems. That complexity creates strong path dependency.
The ECB has noted that many card-processing protocols are variants of ISO 8583, a messaging standard with roots in the 1980s. The interfaces built around it have evolved substantially, but replacing a working network used across countries, currencies and banks is not comparable to shipping a new version of a consumer application. The compatibility surface area is enormous, and the cost of a transition error is not a degraded user experience — it is failed payments at scale.
Newer account-to-account architectures demonstrate that different trade-offs are possible. India's Unified Payments Interface (UPI), which routes instant bank payments without reproducing the classic four-party card model, has reached extraordinary transaction volumes. Europe's own instant credit-transfer infrastructure — built on the SEPA Instant Credit Transfer scheme — is another attempt to move
Originally reported by Silicon Canals. Summarised and curated by European Purpose.
