You tap a card against a terminal. A light flashes, the machine chirps, and the word Approved appears before you have put the card back in your wallet. It looks like the cleanest transaction imaginable: your money leaves, the shop receives it, and the exchange is over. Almost none of that description is quite right.
TAP CARD
The short answer
When you tap, the terminal does not pull money directly from your account and push it into the merchant’s. It starts a coordinated conversation. In a common four-party card system, the merchant’s payment provider sends an authorisation request through an acquiring institution and a card network to the bank that issued the card. The issuer decides whether to approve it. Detailed transaction records are exchanged later through clearing, and the financial obligations are settled afterward.1
The customer experiences one event. The payment system performs several.
The six participants hiding inside one tap
The exact route varies by country, card type, domestic network and commercial arrangement. But the common model contains a cast of institutions that most customers never see.
A payment is a networked decision
One purchase can involve more institutions than the customer and merchant combined.
The tap itself is only the first conversation
A contactless card contains a chip and antenna. When it is held close to an enabled terminal, the two devices communicate over a very short range using the EMV contactless framework. The terminal collects the payment credential and transaction data needed to construct a request. The speed feels magical because the radio exchange is local and the authorisation message is compact, not because a bag of money has moved through the air.2
The request typically contains information such as the merchant, amount, card or token credential and security data. The issuer evaluates the account and risk signals, then sends back an approval or decline through the same chain. Mastercard describes its switching network as facilitating authorisation, clearing and settlement; Visa’s materials likewise treat authorisation as distinct from later clearing and settlement.13
Approved does not mean paid
This is the most important distinction in the entire system. Approved means the issuer has agreed to honor the transaction subject to the applicable rules and later processing. It may reduce the customer’s available balance or credit by placing an authorisation hold. But the merchant’s final funding follows a different operational clock.
Authorisation is not clearing, and clearing is not settlement
Choose a stage to see what the system is doing.
Authorisation
The merchant asks whether the issuer will approve this transaction. The response usually returns in seconds. An approval may reserve funds or credit, but it is not the final transfer to the merchant.
Visa’s merchant guidance makes the separation visible in reverse: when an authorisation has been obtained but the transaction will not be settled, the merchant should send a reversal so the issuer can release the hold. The need for a reversal exists precisely because authorisation created a temporary commitment before final settlement.4
What Visa and Mastercard actually do
People often describe Visa and Mastercard as though they were the banks lending the money. In the common model, they are better understood as network and rule-system operators connecting issuing and acquiring institutions. The issuer owns the customer relationship and makes the account-level decision. The acquirer or its partners serves the merchant. The network carries standardised messages, applies scheme rules and helps calculate and settle obligations between the financial institutions.
That is why a Visa or Mastercard logo can appear on cards issued by thousands of different banks. The logo identifies the network the credential can use. It does not tell you who extended the credit, holds the deposit account or will decide whether this particular purchase is approved.
The merchant pays for access to the system
Card acceptance is not free to the seller. Merchants generally negotiate and pay a merchant discount or merchant service charge to the institution or provider that enables acceptance. Visa emphasizes that this merchant charge is not identical to interchange: it may bundle a range of processing and acquiring services, while interchange is a transfer between the acquiring and issuing sides. Mastercard similarly describes interchange as one component within the merchant discount rate.56
What remains from an illustrative $100 sale?
Move the slider. The rate is illustrative and does not represent a universal market price.
The fee is not merely a toll for moving data. It supports a package of value: broad customer acceptance, fraud controls, standardised processing, dispute mechanisms and the possibility of receiving payment without handling cash or extending credit directly to the buyer. Whether that package is worth the cost is a commercial question each merchant answers differently.
Apple Pay changes the credential, not the underlying rail
When you tap a phone or watch, the payment may look like a separate system. Often it is still a card transaction underneath. Apple says Apple Pay uses device-specific tokenized card credentials and that the transactions are processed like regular credit or debit card payments. EMVCo describes payment tokenization as replacing the primary account number with a unique alternative value that can travel through the payment ecosystem to the issuer.78
The payment route can stay similar while the credential changes
Switch between a physical card and a tokenized mobile wallet.
With Apple Pay, the payment object can include a device-specific account number and a unique one-time-use cryptogram. The merchant does not need to handle the underlying card number in the same way.9
Why a perfectly good card gets declined
A decline is not one single judgment. It can reflect the account, the transaction’s risk profile, the credential or the infrastructure carrying the request. The terminal usually gives the customer only a short result because detailed decline information can be sensitive and the merchant may not be the right party to resolve it.
“Declined” is an outcome, not an explanation
Select a category to see what may sit behind the same word.
The issuer may see insufficient available funds or credit, an expired account credential, or another account-level restriction.
A second attempt may succeed if the first failure was connectivity-related. It may also produce the same result because the issuer made a deliberate risk or account decision. The visible user experience is identical; the hidden cause is not.
A completed payment can still run backward
Card systems include a formal dispute process because authorisation proves that the network approved a transaction request, not that every later question about fraud, delivery or entitlement has been resolved. Mastercard defines a chargeback as a formal scheme procedure allowing a cardholder to recover money from a disputed card transaction. The issuer can initiate the process through the network toward the acquiring and merchant side, while the merchant may respond with evidence under the applicable rules.10
When a transaction becomes a dispute
Run the simplified chargeback path backward through the system.
This reversibility is valuable to consumers but costly to merchants and financial institutions. It also explains why card acceptance involves continuing risk after the customer has left the shop. Commercial finality and operational finality are not always the same moment.
Why merchants accept cards anyway
Convenience comes with intermediaries
What the merchant gains
- Access to customers who prefer cards or wallets
- Fast authorisation at the point of sale
- Less cash handling and change management
- Standardised cross-border acceptance
- Issuer and network fraud controls
- A familiar consumer-protection framework
What the merchant accepts
- Merchant service charges and other fees
- Settlement and funding timetables
- Fraud, refund and chargeback exposure
- Scheme, acquirer and security requirements
- Dependence on terminals, networks and processors
- Rules the merchant did not design
Cash appears simpler because the buyer hands value directly to the seller. Card payment substitutes a networked promise for that physical exchange. The system works because the institutions agree on the rules, trust the messages and settle the resulting obligations.
What people usually get wrong
The first mistake is thinking that the tap itself transfers the final money. It typically asks for authorisation. The detailed record and financial settlement follow.
The second is treating every logo as a bank. The issuer manages the customer’s card account; the acquirer and its partners serve the merchant; the network connects the sides.
The third is assuming a mobile wallet bypasses the card system. Tokenization can materially improve credential security, but an Apple Pay transaction can still travel over the same underlying card network.
The fourth is assuming the merchant’s fee is one simple network charge. The merchant discount can include several services and cost components. Interchange is important, but it is not synonymous with the entire price the merchant pays.
The bottom line
A card payment looks like a direct exchange between a customer and a merchant. It is actually a synchronised conversation between devices, processors, banks and a network, followed by a separate accounting process that moves and reconciles the money.
The system feels instant because the decision is instant. The money is not.
The tap is a message. “Approved” is permission. Settlement is what completes the financial story.