HOW BANKING WORKS · CARDS 13
A tap at the checkout is the visible edge of a multi-institution payment system
You tap a debit card for S$48.70. The terminal beeps. The merchant sees “approved.” Your available balance falls. It feels as though S$48.70 moved directly from your account into the merchant’s.
That is not the whole mechanism. A debit-card purchase normally passes through the merchant, the merchant’s acquiring side, a card network or routing infrastructure, the cardholder’s issuing bank, clearing and settlement processes, then merchant reconciliation. Authorisation can happen in seconds. Final settlement and merchant funding follow the rules and timing of the card system.
This article is part of the How Banking Works authority spine. Batch 03 established payment finality. Batch 04 now puts that machinery inside the familiar object of a bank card.
The five roles hiding inside one card purchase
| Role | Job |
|---|---|
| Cardholder | Initiates the purchase and authorises use of the card credentials. |
| Merchant | Provides the goods or services and submits the transaction. |
| Acquirer / acquiring side | Provides merchant acceptance and receives the merchant’s card transactions. |
| Card network | Routes messages and applies network rules between acquiring and issuing sides. |
| Issuer / issuing bank | Issued the card and decides whether to authorise the transaction against the customer account and controls. |
The exact commercial structure can vary, and some firms perform more than one role. The conceptual separation still helps because each role owns a different part of the payment.
Step 1: the card presents credentials, not cash
When a card is tapped, inserted or otherwise used, the payment device captures information needed to identify the card account and authenticate the transaction according to the card technology and rules.
The card does not contain the customer’s bank balance in the same way a wallet contains notes. It presents credentials that allow the payment system to ask the issuing bank whether the transaction should proceed.
This is why a damaged card can fail even when the account contains enough money, and why a stolen credential can be dangerous even without physical access to a bank branch. The card is an access instrument to an account relationship.
Step 2: the merchant sends an authorisation request
The merchant terminal packages the purchase details and sends an authorisation request through the acquiring side and card network toward the issuer.
The request can contain the amount, merchant identity, card information, transaction type, location or device data, security information and other fields required by the scheme and processor.
The message asks a narrow question: may this transaction proceed?
Step 3: the issuer checks more than the account balance
For a debit card, the issuing bank may check whether sufficient available funds exist. But balance is only one gate.
- Is the card active?
- Is the account open and usable?
- Is the transaction within card and account limits?
- Does the security data make sense?
- Does fraud monitoring consider the pattern suspicious?
- Is the merchant category permitted?
- Are geographic or channel restrictions relevant?
- Does the transaction require additional authentication?
The issuer then returns an approval or decline response through the network to the merchant.
Authorisation reduces available funds—but it is not final settlement
When the issuer approves the purchase, it may place a hold or reduce the cardholder’s available balance. The exact accounting and timing depend on the institution and transaction type.
This is an important state distinction. The cardholder may see S$48.70 reserved or posted, and the merchant may see an approval, yet the interbank settlement process is still to come.
Read A Payment Instruction Is Not Yet Settlement for the underlying state machine.
Step 4: the merchant completes the transaction and submits it for clearing
After authorisation, the merchant completes the sale. Card transactions are then submitted through the acquiring side for clearing according to the network’s process.
Clearing determines the financial obligations among the issuer, acquirer and other relevant participants. Fees and adjustments may be calculated. The merchant’s transaction moves from an authorised event toward a settled financial claim.
Authorisation and clearing are therefore different jobs. The first allows the sale to proceed. The second establishes what the participants owe after the transaction is completed.
Step 5: settlement moves value between institutions
After clearing, the card system’s settlement process transfers value between participating institutions under its rules. The issuing side funds its obligation; the acquiring side receives settlement value and ultimately credits the merchant, less applicable fees and adjustments.
The merchant does not necessarily receive exactly the gross purchase amount as one untouched transfer. Merchant-service fees, network fees, interchange-related economics, refunds and other contractual items can affect what is ultimately credited.
The customer sees a S$48.70 purchase. The merchant sees a sale plus payment-processing economics. The banks see an inter-institution settlement flow.
Where does the customer’s deposit go?
From the issuing bank’s balance-sheet perspective, the debit-card purchase ultimately reduces the deposit liability owed to the customer. If the merchant is served by another bank, settlement value leaves the issuing side and reaches the acquiring side.
The underlying logic is the same as an ordinary interbank transfer:
customer deposit falls → issuer obligation arises → network clearing calculates the interbank claim → settlement value moves → acquirer funds merchant.
The card scheme adds acceptance, authorisation, fraud controls and commercial rules around that payment core.
Why the merchant can trust an approval before settlement completes
Card systems are designed so merchants can hand over goods or services after receiving an approval rather than waiting for final interbank settlement. The network rules allocate the resulting risks and responsibilities among merchant, acquirer, issuer and cardholder.
This is an important economic service. It converts a delayed institutional settlement process into an immediate retail decision.
But approval is conditional on compliance with the rules. Fraud, duplicate processing, incorrect amounts, merchant errors or disputes can later trigger reversals or chargebacks.
Why debit cards can show pending transactions
A pending transaction often represents an authorised amount that has not yet completed the later posting and settlement stages. The issuer may reserve funds so the customer cannot spend the same balance twice.
The final amount can sometimes differ from the initial authorisation. Hotels, petrol stations, transport or restaurants can use estimates, deposits or later adjustments depending on local practices and card rules.
This is another reason a banking app must distinguish available balance, ledger balance and pending activity clearly.
Why debit-card fraud is a bank-account risk
A debit card is closely connected to deposit funds. If a fraudulent debit transaction succeeds, the customer’s available bank balance can be affected immediately or quickly depending on the system.
Banks therefore combine card security with account-level controls: transaction alerts, card freezing, spending limits, merchant controls, device intelligence and fraud models. No control can eliminate every false positive and every fraud attempt simultaneously, so the system balances protection with legitimate usability.
Offline acceptance shows why card systems contain controlled trust
Some card environments can allow limited offline or delayed authorisation according to the technology and rules. In those cases the merchant accepts more risk because the issuer has not responded in real time.
This reveals the deeper architecture of cards: the system is not merely a live balance lookup. It contains explicit rules about when participants may act before certainty is complete and who bears the resulting risk.
Why cards cost merchants money
Card acceptance provides merchants with reach, speed, risk allocation, reconciliation and payment infrastructure. Those services have costs. Merchant pricing can include acquiring fees, network charges and other components depending on the contract and market.
The fee is therefore not simply “the bank taking a cut.” It pays for a multi-party infrastructure that authorises, routes, settles, manages fraud and supports disputes. Whether a particular fee is competitive or fair is a separate commercial question.
Reconciliation closes the merchant loop
The merchant needs to match till receipts, card authorisations, settled batches, fees, refunds and actual bank credits. The acquirer and issuer perform their own reconciliation.
A card payment is therefore not truly understood until the merchant can answer: which sale produced this settlement amount, which fees were deducted, which transactions remain pending, and which items were reversed?
Read Bank Reconciliation for the proof layer beneath this process.
Four misconceptions to remove
| Misconception | Better model |
|---|---|
| “A debit card sends money directly from customer to merchant.” | It routes a card transaction through issuing, acquiring, network, clearing and settlement layers. |
| “Approved means finally settled.” | Approval allows the purchase; clearing and settlement follow. |
| “The card contains my bank balance.” | The card provides credentials to access and authorise use of the account relationship. |
| “The merchant receives the gross sale immediately.” | Merchant funding follows acquiring and settlement rules and can be net of fees or adjustments. |
A mastery test
- Who decides whether a debit-card transaction is authorised?
- What does the acquirer do for the merchant?
- Why can a transaction be approved before final settlement?
- How does a debit-card purchase eventually reduce the customer’s deposit claim?
- Why does reconciliation matter to the merchant as well as the bank?
If those answers connect, the card terminal stops being the payment. It becomes the front door to a coordinated banking network.