Blog
What happens in the seconds after you tap: network, issuer and merchant
A tap travels from terminal to merchant's bank to network to your issuer and back in a second or two, and money moves days later. Each step and who owns it.
You hold a card or a phone to a reader, there is a beep, and the screen says approved. The whole exchange takes a second or two. In that moment a message has traveled from the shop's terminal to the merchant's bank, through a card network, to the bank that issued your card, been checked against your account and come back, passing through several computers owned by several companies. Not a dollar has moved yet. That comes later, in a second, slower stage, and a good deal of the confusion about pending charges, holds, tips and declines comes from mixing up the two stages.
This timeline follows one tap from start to finish. It names the party that is in charge at each step, shows what you see on your side, and marks the points where a payment can fail and who can fix it. The numbers in the worked example are invented for illustration.
The cast, in one paragraph
Five parties show up in nearly every card payment. You present the card or a wallet on your phone. The merchant runs the terminal. The merchant's acquirer (also called the merchant's bank or acquiring bank) accepts card payments on the merchant's behalf, usually working with a payment processor that runs the technical connection. The card network (Visa, Mastercard and others; see Visa and Mastercard) carries messages between the acquirer and your issuer, the bank that lent you the money and decides whether to approve. In some designs one company plays more than one role. This post uses the common four-party picture.
Two stages follow. Authorization is the question: will the issuer stand behind this payment? It takes seconds. Clearing and settlement is the movement of money, and it takes days. The next sections follow them in order.
0 seconds: the tap
When you tap a card or a phone, a short-range radio link (contactless payment) passes payment data to the reader. On a chip-based contactless card, the chip creates a one-time code, called a cryptogram, specific to this transaction, and the reader sends it along with the other data. With a phone wallet, the number the merchant receives is usually not your real card number but a stand-in called a token, which is tied to your device. That substitution is called tokenization, and how chips and tokens protect your card number in different ways explains how it differs from the chip itself.
Nothing is approved at this point. The terminal has gathered what it needs to ask the question. If the reader cannot read the card, or the phone is not close enough, the failure happens here, before any bank is involved. That is why a failed tap followed by a successful chip insertion is not strange: see My tap payment failed but the chip worked. Why does that happen?.
0 to 1 second: from terminal to acquirer
The terminal builds an authorization request: the amount, the merchant's identity, a merchant category code and the payment data from your card. It sends this to the merchant's acquirer or to the processor working for the acquirer. The acquirer and the payment processor do their first checks, such as whether the request is well formed and the merchant is in good standing, and forward it. The merchant has no way to see your credit limit or balance, and never receives them.
About 1 second: through the network
The acquirer sends the request to the card network, which reads the first digits of the card number (or the token) to decide which issuer should receive it. The network does three things in this step.
- Routes the message to the right issuer.
- Applies its rules, such as formatting and security requirements.
- Passes back the issuer's answer.
Note what the network does not do. It does not lend you money, set your credit limit or APR, or decide whether you are approved. It is the road and the rulebook, not the lender. That distinction is the reason, when something goes wrong, the network is rarely the one to call. Network, issuer or processor? Who to call when a card payment goes wrong sorts the symptoms by who can fix them.
About 1 second: the issuer decides
The issuer receives the request and decides in a fraction of a second. It runs through a short sequence of checks.
- Is the account open and in good standing?
- Is the card or token valid? Does the cryptogram match, and has the card not been reported lost?
- Is there room? Is the amount within your available credit?
- Does it look like you? Fraud models compare the purchase with your normal patterns: place, amount, merchant type, time and recent history.
- Any account rules? Spending controls you set in the app, a travel lock or a card that is turned off.
The answer is approve, decline or in some cases a request for more proof such as a PIN or a code. A decline comes with a reason code that the terminal may turn into a short message. Many different codes can sit behind the same "declined" on the screen, and the merchant usually sees only a generic result, which is why the issuer, not the shop, is the one who can tell you why. If the decline is a fraud-model suspicion, the issuer may text you or block the card until you confirm.
1 to 2 seconds: the answer returns
The issuer's answer travels back through the network to the acquirer to the terminal, and the terminal beeps. An approval includes an authorization code, a short identifier that ties this request to the later money movement. The merchant gets a receipt, and the sale is, for the shopper's purposes, done.
This round trip is why a payment can feel slow when a connection is poor, and why a very short outage at any hop (the shop's internet, the processor, the network, the issuer) can look to you the same as a decline. If the card has not been declined by the issuer, retrying is safe. But if you tap twice and see two approval messages, do not assume only one went through. Check the pending list in your app before paying again, and ask the merchant to cancel a duplicate.
What the approval did on your account
Approval does not move money. It places a hold. The issuer reduces your available credit by the approved amount, and the transaction appears in your account as a pending item. A pending transaction is a promise to pay that the merchant has not yet collected, and an authorization hold is the reduction in available credit that goes with it. Pending items are not final: the amount may change, the merchant may never collect and the hold can drop off on its own after some days if no final charge arrives.
Here is a worked example, with invented numbers, of how the hold and the final charge differ.
Say Alex has a $3,000 credit limit and a current balance of $1,850, so the available credit is $3,000 − $1,850 = $1,150.
| Step | Event | Balance | Available credit |
|---|---|---|---|
| Monday, 7:42 pm | Tap at a restaurant, authorized for $64.50 (food only, before tip) | $1,850.00 | $1,085.50 |
| Monday, 8:15 pm | Alex adds a 20% tip: 0.20 × $64.50 = $12.90, so the final total is $77.40 | $1,850.00 | $1,072.60 |
| Wednesday | Restaurant's charge clears and posts at $77.40 | $1,927.40 | $1,072.60 |
| Wednesday, 8:10 am | Gas pump places a $100 hold (an illustrative amount; stations differ) | $1,927.40 | $972.60 |
| Wednesday, 8:14 am | Alex pumps $41.27 and the final charge replaces the hold | $1,968.67 | $1,031.33 |
The arithmetic: $1,150.00 − $64.50 = $1,085.50. The tip raises the total to $77.40, so $1,150.00 − $77.40 = $1,072.60. When it posts the balance is $1,850.00 + $77.40 = $1,927.40. The pump hold reduces available credit by $100, to $972.60. Then the final charge of $41.27 replaces the hold, giving a balance of $1,927.40 + $41.27 = $1,968.67 and available credit of $3,000 − $1,968.67 = $1,031.33.
Three things stand out. The tip is added after the first authorization, so the pending amount and the final one can differ. The gas hold is larger than what you buy, so for a few minutes your available credit is lower than it will end up. And "pending" means the charge is real but unfinished, so the balance you see in an app is not the same as the amount a statement will show until things post. A very large hold at a hotel or a rental counter can reduce your available credit for days, which matters if you are near your limit.
Later that day: clearing
Authorization is a question; clearing is the invoice. At the end of the day, usually, the merchant's system gathers the approved sales into a batch and sends it to the acquirer. Each item carries the authorization code and the final amount, which can differ from the authorized amount (the tip, the actual fuel). The acquirer sends the batch through the network, which sorts the items and passes each to the right issuer. The issuer matches the final charge to the earlier authorization and replaces the hold with a posted transaction.
Some merchants clear immediately; some batch overnight; some, such as a hotel, finalize at checkout days after the first authorization. This is why the posting date on your statement can be a day or several days after the day you tapped. Statement closing and due dates run from posted charges, which is worth knowing at the edge of a billing cycle. A purchase made on the last day of a cycle may land in the next one, and a billing cycle day by day, from closing date to payment due date shows how that plays out.
A few days later: settlement
Settlement is where money actually moves. The issuer pays the amount owed for the day's cleared transactions to the network's settlement process, which passes it to the acquirer. The acquirer then pays the merchant, usually within a few business days, minus fees. The fee that goes from the merchant's side to the issuer, called interchange, and the smaller fees paid to the network and the processor, are the reason the merchant receives less than the price on the tag. one $100 sale: how interchange, network fees and the merchant's cut split splits a $100 sale to show where each piece goes.
You, meanwhile, owe your issuer the full amount. The issuer pays the acquirer on the card's behalf and then collects from you on your statement. If you pay your statement balance in full by the due date, you generally pay nothing extra (subject to your card's terms), and the whole chain has been funded by fees paid by the merchant rather than by you.
Where a payment can fail, and who can fix it
| Where it fails | What you see | Who can help |
|---|---|---|
| Reader cannot read the card or phone | Nothing happens or "try again" | The merchant; try chip or a different wallet |
| Merchant's connection or terminal fails | Error before any approval | The merchant |
| Acquirer or processor outage | Error or timeout | The merchant, who can contact its processor |
| Network outage | Error or timeout, no decline reason | Rarely you; try later or another card |
| Issuer decline | "Declined," sometimes a text or app alert | Your issuer, at the number on the back of your card |
| Approved but later reversed or adjusted | A pending charge that drops off or changes | The merchant, if the amount is wrong; your issuer if it never clears |
| Charged twice | Two pending or posted charges | The merchant first, then your issuer if not fixed |
If the amount posted is wrong, or you see a charge you did not make, tell the issuer promptly. For a billing error, the Fair Credit Billing Act gives you a written-notice window of 60 days after the statement showing it was sent. For a charge you do not recognize, call the number on the back of your card, and use the Consumer Financial Protection Bureau complaint process if it is not resolved.
For the same chain run through a phone wallet, see what actually happens when you tap your phone to pay in a store.
What the network does and does not see
The network sees the card number or token, the amount, the merchant's identity and category, the time and the issuer's response. It does not see your receipt, what you bought line by line (generally) or your balance. It does enforce the rules that merchants and issuers agreed to, including how disputes between them are handled. The details of chargebacks sit in later steps: the cardholder disputes with the issuer, which may send a chargeback through the network's dispute system and let the merchant respond. Those network rules are contract rules between the participants, separate from the federal billing-error law that protects you.
Two practical implications follow. First, a network rule such as the zero-liability policy is a policy of the network and issuer, with terms set by them, and not a statute. Second, merchants are free to decline to accept a given network, and cardholders are free to carry more than one. When a card is not accepted somewhere, the network is usually why.
Key takeaways
- A tap starts an authorization request that travels from the terminal through the acquirer and the network to the issuer, and back, usually in a second or two. Nothing is paid at that point.
- The network routes messages and enforces rules. It does not lend, set your APR or approve you, which is why it rarely takes calls.
- Approval creates a hold that lowers available credit. In the example, a $64.50 authorization became a $77.40 charge after a tip, and a $100 gas hold became $41.27.
- Clearing sends final amounts the same day or later, and settlement moves money to the merchant a few business days after that, net of fees. Your posting date and statement follow the cleared charge.
- For a decline, call the number on the back of your card. For a wrong or unknown charge, tell your issuer promptly and know the 60-day written-notice window for billing errors.