The Transaction Lifecycle
What happens in the two seconds between tap and "approved."
Every day, billions of payment transactions flow across the global financial system. Each one follows a precise sequence of handoffs between multiple parties, all completed in roughly two seconds. Most people in payments, fintech, and e-commerce have a general sense of how this works. Far fewer understand the detail.
This module maps the complete journey of a card transaction from the moment a customer taps, dips, or enters their card details to the moment the merchant sees funds in their account. We will introduce the key actors, explain how they interact, and lay the foundation for every module that follows.
If you understand the transaction lifecycle, you understand why payments companies are structured the way they are, why certain problems are hard, and where the real opportunities sit.
The Cast: Who Does What
Before we trace a transaction, we need to know who is involved. There are five core parties in every card payment. Each one has a distinct role, a different economic incentive, and a different relationship with the money.
| Actor | Role |
|---|---|
| Cardholder | The customer making the purchase. They hold a card issued by their bank (the issuer) and use it to pay for goods or services. |
| Merchant | The business accepting the payment. The merchant has a relationship with an acquirer (directly or via a payment facilitator) that allows them to accept card payments. |
| Acquirer | The merchant's bank or payment provider. The acquirer underwrites the merchant, manages risk, and routes transactions to the card network. Also called the "merchant acquirer" or "acquiring bank." |
| Card Network | Visa, Mastercard, Amex, or similar. The network operates the rails: the technical and rules infrastructure that connects acquirers and issuers. It sets interchange rates, mandates, and scheme rules. |
| Issuer | The cardholder's bank. The issuer provides the card, extends credit (for credit cards) or manages the account (for debit), and makes the approve/decline decision. |
These five actors form what the industry calls the "four-party model" (counting the cardholder, merchant, acquirer, and issuer as the four parties, with the network as the connecting infrastructure). American Express and Discover operate slightly differently as "three-party" or "closed-loop" networks, acting as both the network and the issuer. We will cover these distinctions in Module 3.
The Authorisation Flow: What Happens When You Tap
Authorisation is the first and most visible phase of a card transaction. It is the real-time check that determines whether a payment is approved or declined. Here is how it works, step by step.
Capture
The transaction begins at the point of interaction. In a physical store, this is the payment terminal (POS device) that reads the card via chip (EMV contact), contactless (NFC), or magnetic stripe. In e-commerce, it is the checkout page where the customer enters their card number, expiry date, and CVV. The terminal or gateway packages the card details, amount, currency, merchant identifier, and a unique transaction reference into an authorisation request message.
Routing to the Acquirer
The authorisation request is sent to the merchant's acquirer (or their processor, acting on the acquirer's behalf). The acquirer performs initial checks: is this merchant active? Is the transaction within acceptable parameters? Does anything flag for fraud? If the checks pass, the acquirer forwards the request to the appropriate card network, identified by reading the card's BIN (Bank Identification Number), the first six to eight digits of the card number.
Network Routing
The card network receives the authorisation request and routes it to the correct issuer. This is one of the network's core functions: maintaining the directory that maps every card number to an issuing bank, and providing the technical infrastructure to move messages between acquirers and issuers globally. Both Visa and Mastercard run real-time fraud detection systems that analyse transactions as they pass through the network.
Issuer Decision
The issuer receives the authorisation request and makes the approve/decline decision. This considers: sufficient funds or available credit, spending pattern match, whether the card is reported lost or stolen, fraud rules and machine learning models, velocity checks, and whether Strong Customer Authentication (SCA) has been satisfied in regulated markets.
Response to Merchant
The acquirer passes the response back to the merchant's terminal or payment gateway. The customer sees "Approved" or "Declined." The entire round trip, from tap to response, typically takes between one and three seconds.
Authorisation is a promise, not a payment. The issuer has agreed to pay, but no money has moved yet. The actual transfer of funds happens later, during clearing and settlement.
Clearing and Settlement: Where the Money Actually Moves
Most people think the transaction is finished when the terminal says "Approved." In reality, the financial heavy lifting has not started. Clearing and settlement are the processes that reconcile authorisations and move actual funds between institutions.
Clearing
Clearing is the process of exchanging transaction details between acquirers and issuers through the card network. At the end of each business day (or more frequently for high-volume processors), the acquirer submits a batch of completed transactions to the network. The network sorts these transactions, calculates the net amounts owed between parties, and distributes the information to the relevant issuers.
During clearing, the network also calculates interchange fees (the fee the acquirer pays to the issuer for each transaction) and scheme fees (the fees both parties pay to the network itself). These fees are deducted at source, which means the amounts that arrive at each party's account are already net of fees.
Settlement
Settlement is the actual transfer of funds. After clearing has determined who owes what, the network facilitates the movement of money between acquiring banks and issuing banks. In most markets, settlement happens on a T+1 or T+2 basis (one or two business days after the transaction), though some networks and processors are moving toward faster cycles.
The settlement flow works like this:
- The issuer transfers the transaction amount (minus interchange) to the network.
- The network transfers the funds (minus scheme fees) to the acquirer.
- The acquirer deposits the funds (minus the acquirer's processing fee) into the merchant's bank account.
The merchant ultimately receives the transaction amount minus three layers of fees: interchange (to the issuer), scheme fees (to the network), and acquirer/processor margin (to their payments provider). This is the "merchant discount rate" or MDR.
The Fee Stack
| Fee Layer | Paid To | Typical Range |
|---|---|---|
| Interchange | Issuing bank | 0.2 to 1.8 percent depending on card type, region, and regulation (EU interchange is capped at 0.2 percent debit / 0.3 percent credit) |
| Scheme fees | Card network | Variable and increasingly complex. Typically 0.02 to 0.15 percent plus fixed per-transaction fees. Scheme fees have been rising steadily. |
| Acquirer margin | Acquirer / processor | 0.1 to 1.0+ percent depending on merchant size, risk profile, volume, and pricing model (interchange-plus vs. blended). |
Understanding the fee stack is essential for anyone working in payments. Every product decision, every pricing negotiation, and every competitive dynamic in the industry connects back to how these fees are structured and who captures what share.
Speaking the Language: Message Standards
Payments transactions are communicated using standardised message formats. Two standards dominate the card payments world.
ISO 8583
ISO 8583 is the legacy message format used for card transaction authorisation, clearing, and settlement. It has been the backbone of card payments since the 1980s. The standard defines a bitmap-based message structure where each data element (amount, currency, card number, merchant ID) occupies a specific numbered field. ISO 8583 is compact and efficient, designed for an era when bandwidth and processing power were scarce.
Most acquiring processors, card networks, and issuers still use ISO 8583 internally. If you are working with a traditional processor, terminal manufacturer, or bank, you will encounter ISO 8583.
ISO 20022
ISO 20022 is the modern replacement, built on XML (and increasingly JSON). It offers richer data fields, better structure, and more flexibility. ISO 20022 is the standard for SWIFT's cross-border messaging, real-time payment systems (like the UK's Faster Payments and the EU's SEPA Instant), and is gradually being adopted across card payments as well.
The migration from ISO 8583 to ISO 20022 is a multi-year industry effort. For card payments, this transition is still in its early stages, but it is accelerating. The richer data in ISO 20022 enables better fraud detection, more detailed remittance information, and improved reconciliation.
Beyond Authorisation: The Full Transaction Lifecycle
Authorisation, clearing, and settlement are the core phases. But a transaction can take several other paths after authorisation, and understanding these is critical.
Capture
In some scenarios, authorisation and capture are separate steps. A hotel, for example, may authorise a card at check-in (reserving funds) but only capture the final amount at checkout. Restaurants authorise the bill amount and capture after the tip is added. In e-commerce, some merchants authorise at order and capture at shipping. The time between authorisation and capture is called the "auth window," and it varies by card network and transaction type.
Voids and Reversals
If a transaction needs to be cancelled before it has been settled, the acquirer sends a reversal (also called a void). This releases the hold on the cardholder's funds without requiring the full chargeback process. Reversals are cheaper and faster than refunds.
Refunds
After settlement, cancelling a transaction requires a refund, which is effectively a new transaction in reverse. The acquirer sends the refund amount back through the network to the issuer, who credits the cardholder's account. Refunds typically take three to five business days to appear.
Chargebacks
A chargeback occurs when a cardholder disputes a transaction. The issuer reverses the transaction and debits the acquirer, who in turn debits the merchant. The merchant can contest the chargeback by providing evidence (known as representment). Chargebacks carry additional fees and, if a merchant's chargeback rate exceeds network thresholds (typically one percent of transactions), they face penalties, monitoring programmes, or even termination of their merchant account.
Chargebacks are one of the most consequential mechanisms in the payments system. They shape fraud strategy, merchant risk management, product design, and customer service policy. We will explore them in depth in Module 4.
Putting It All Together
Here is the complete lifecycle of a standard card-present transaction, summarised end to end:
- The cardholder taps or inserts their card at the terminal.
- The terminal reads the card data and creates an authorisation request.
- The request is sent to the acquirer/processor.
- The acquirer routes the request to the correct card network (identified by BIN).
- The network routes the request to the issuing bank.
- The issuer approves or declines based on funds, fraud checks, and authentication.
- The response flows back through the network and acquirer to the terminal.
- The transaction is captured and batched for clearing.
- The network clears the transaction, calculating interchange and scheme fees.
- Settlement occurs: funds flow from issuer to network to acquirer to merchant account.
Each step in this chain is a product, a business, and an opportunity. The companies that operate at each layer, and the ones building new layers on top, are the subjects of this course.
Key Takeaways
- A card transaction involves five core actors: cardholder, merchant, acquirer, card network, and issuer. Each has a distinct role and economic incentive.
- Authorisation is a real-time approval but not a transfer of funds. Clearing and settlement happen later.
- The merchant discount rate is the sum of interchange, scheme fees, and acquirer margin. Understanding this fee stack is fundamental.
- ISO 8583 remains the dominant message standard for card payments, but ISO 20022 is the future.
- Post-authorisation events (capture, voids, refunds, chargebacks) are where much of the complexity and commercial risk in payments lives.
- The transaction lifecycle is the foundation. Everything in this course, from acquiring to settlement to hardware, connects back to this flow.
Glossary
Which part of the transaction lifecycle do you think is most ripe for disruption? And where does the current system work well enough that nobody should touch it?