A card terminal can approve a purchase before the receipt has finished printing. Online, the confirmation page often appears in less than a second.
It feels as though money has moved straight from the customer to the merchant. Usually, it has not.
What moved first was a request and a reply: is this card valid, does the issuer approve the amount, and will it stand behind the payment? The funds may reach the merchant only after a separate sequence involving a gateway, processor, acquiring institution, card network, issuing bank and, in some arrangements, an ordinary bank-transfer system used for the final payout.
The exact chain varies by country, card scheme and provider. A single company can perform several roles, while a large merchant may contract with different companies for each. But the distinction between authorisation, clearing, settlement and payout is the part that the checkout screen hides.
The instant part is an approval message
Consider a customer tapping a card for a €5 coffee. The terminal passes the transaction details to the merchant’s payment provider. A gateway may package and encrypt the information. A processor or acquirer then routes an authorisation request through the relevant card network to the bank that issued the card.
The issuer checks the account, card status and its risk rules. It sends back an approval or decline through much the same chain. On approval, it will commonly reduce the cardholder’s available balance or credit by placing a hold.
The European Central Bank defines a card issuer as the institution that authorises point-of-sale transactions and guarantees conforming payments to the acquirer under the scheme’s rules. Its payments glossary also defines the acquirer as the entity to which the merchant transmits the information needed to process the card payment.
Those definitions explain how the shop can hand over the coffee without waiting for a bank transfer. The merchant is relying on an approved obligation within a governed network. No one needs to move that particular €5 through every bank account before the customer leaves.
Clearing turns purchases into amounts owed
After authorisation comes capture and clearing. The merchant submits completed transactions, often in a batch, through its provider. The card system reconciles the details, applies the relevant rules and fees, and calculates what each participating issuer and acquirer owes.
The distinction is formal, not merely jargon. The ECB defines clearing as reconciliation and confirmation before settlement, potentially including netting and the calculation of final positions.
Mastercard’s own description of its switching operation separates the same three stages. Its authorisation platform carries the initial requests and responses. Its Global Clearing Management System exchanges transaction details and assesses fees. Its Settlement Account Management system then calculates each issuer’s and acquirer’s net position and facilitates the transfer of funds. Mastercard describes those systems here.
Netting is central to the design. Banks do not necessarily send one tiny transfer for every coffee, train ticket and online subscription. A scheme can offset large volumes of obligations and settle the resulting net totals between participants. The customer sees one purchase. The institutions see entries inside a much larger accounting cycle.
Settlement and merchant payout are not always the same event
Settlement is when the financial obligations between the issuer and acquirer are discharged according to the card scheme’s arrangements. The merchant’s payout is when its provider sends available funds to the merchant’s ordinary business bank account.
Those events can be close together, but they are conceptually separate. A modern payment provider may credit the merchant’s internal balance while the funds are still pending, make them available after its settlement delay, deduct processing fees, refunds or reserves, and then pay an aggregated amount to the merchant’s bank on a chosen schedule.
Stripe’s documentation makes the separation visible. A successful card charge first appears in a pending balance. It becomes available after the applicable settlement period, which varies by country and payment method. A payout can then move that available balance to an external bank account.
This is where an older banking rail may enter a card payment’s story. In the United States, for example, companies can use an Automated Clearing House credit to pay aggregated funds into a merchant’s account. The ACH network was established in the 1970s and remains a batch-oriented, store-and-forward system, although it has added faster settlement windows over time.
That does not mean every Visa or Mastercard purchase passes through ACH. The final rail depends on the provider, banks, currency and market. European payouts may use SEPA transfers; other arrangements can settle through scheme banks or domestic infrastructure.
Several companies can touch one transaction without holding the money
The payment gateway might transmit data without possessing funds. A processor may operate the connection between acquirer and issuer. The network supplies rules, routing, clearing and settlement services but generally does not issue the customer’s bank account. The issuer serves the cardholder. The acquirer serves the merchant. A payment facilitator may place many smaller sellers under a larger merchant arrangement and keep its own ledger of their balances.
The ECB’s 2025 report on European card payments describes processors as companies positioned between the merchant’s acquirer and the card issuer, performing tasks involved in authorising and processing payments. It also found that most EU countries rely on international card schemes.
I think this is the useful structural detail. 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.
Why the old layers remain
Card systems have to handle more than a one-way transfer. They support authorisation holds, delayed capture, reversals, refunds, currency conversion and disputes. They must work across millions of merchants and thousands of financial institutions that do not all run the same software or operate in the same legal system.
Compatibility therefore carries unusual weight. The ECB has noted that many card-processing protocols are variants of ISO 8583, a messaging standard with roots in the 1980s. The interfaces around it have changed considerably, but replacing a working network used across countries and banks is not comparable to updating a consumer app.
Newer account-to-account systems show a different architecture. I previously wrote about the scale reached by India’s UPI payment system, which routes instant bank payments without reproducing the classic four-party card model. Europe’s instant credit-transfer infrastructure is another attempt to move bank money continuously rather than wait for traditional batch cycles.
Even then, “instant” needs a definition. It can mean the user receives confirmation, the recipient’s account is credited, the participating banks settle with finality, or an intermediary advances money before recovering it later. Different systems make different parts immediate.
For a merchant, the practical evidence is the payout report, not the customer’s green tick. One card purchase may be approved in milliseconds, cleared among millions of others, settled as part of a net institutional position and finally arrive bundled with a day’s sales. The interface is instant because the institutions agree not to make the customer watch the accounting happen.
