How Credit Cards Process a Payment

Tap a card at checkout and a purchase clears in about a second. Behind that second is a relay race between banks that have never directly dealt with each other, coordinated by a network whose entire business is making that handoff invisible. Understanding who does what clears up a lot of confusion about chargebacks, pending charges, and why a payment can be "approved" one day and still bounce a few days later.

The five parties in every transaction

Every card payment involves the same basic cast. The cardholder is you, presenting the card. The merchant is whoever is getting paid. The merchant doesn't have a direct relationship with your bank, so they use an acquiring bank (or a payment processor working on that bank's behalf) to accept card payments on their behalf. Your card was issued by an issuing bank, which is the institution actually lending you the money or holding your funds. And connecting the acquiring side to the issuing side is the card network — Visa, Mastercard, or a similar operator — which doesn't move money itself but defines the rules and message formats that let thousands of unrelated banks talk to each other as if they were one system.

Authorization: the instant part

When you tap or swipe, the merchant's terminal sends an authorization request through the acquiring bank to the card network, which routes it to your issuing bank. The issuer checks whether the account is active, has sufficient available credit or balance, and whether the transaction looks consistent with your normal spending pattern, since fraud-detection scoring happens at this stage too. If everything checks out, the issuer sends back an approval code, which travels the same path in reverse, and the terminal prints a receipt. This entire round trip typically completes in one to three seconds, even though it may be crossing between banks on different continents.

Approval at this stage places a hold on your available credit or balance for that amount, but no money has actually moved between banks yet. That's why a pending charge can sometimes disappear or change slightly in amount before it posts — a restaurant tip added after the initial swipe is a common example, where the final settled amount differs from the original authorization hold.

Settlement: where the money actually moves

Merchants don't process each authorized transaction individually as it happens; they typically batch up all of a day's approved transactions and submit them together for settlement, often at the close of business. The acquiring bank forwards this batch through the card network to each relevant issuing bank, which then transfers the actual funds. The issuing bank pays the acquiring bank the transaction amount minus an interchange fee, a percentage set largely by the card network that compensates the issuer for extending credit and absorbing fraud risk. The acquiring bank then pays the merchant, after subtracting its own processing fee, which is why the amount a merchant actually receives is somewhat less than what the customer was charged.

This batching is why settlement typically takes one to three business days after authorization, even though the authorization itself felt instant. It's also why a merchant can, within a limited window, still adjust or cancel a charge before it settles, since the actual transfer of funds hasn't happened yet.

Why chip and contactless payments are harder to counterfeit

Older magnetic stripe cards store static data that, if copied, can be used to create a working counterfeit card. Chip cards, following the EMV standard maintained by the major card networks, instead generate a unique cryptographic code for every single transaction, derived from a secret key embedded in the chip that never leaves the card. Even if that transaction code were somehow intercepted, it couldn't be reused for a different purchase, which is why widespread magnetic-stripe-style card cloning has become far less common in markets where chip and contactless payments are standard. Contactless payments using near-field communication work the same way, generating a fresh cryptographic token for each tap rather than transmitting a static card number.

What happens in a dispute

If a cardholder disputes a charge, the issuing bank can initiate a chargeback, reversing the transaction and pulling the money back from the acquiring bank, which in turn typically deducts it from the merchant. The merchant can contest the chargeback by providing evidence that the transaction was legitimate, such as a signed delivery receipt or matching billing information, and if that evidence is convincing the funds can be reinstated. This dispute machinery, along with the fraud liability rules that govern who eats the cost of an unauthorized transaction, is set out in consumer protection regulations enforced by the Consumer Financial Protection Bureau, which is why cardholders generally have much stronger recourse against fraudulent charges than someone who paid by cash or direct bank transfer.

None of this machinery is visible to a shopper tapping a card at a register, but it explains a lot of everyday quirks: why a hotel hold on your card disappears after checkout rather than an exact amount, why a merchant's payment processing fees show up as a line item on their own accounting even though you never see them, and why a dispute can take weeks to resolve even though the original charge cleared in under two seconds.