How do card payments work, from tap or click to money in the merchant’s account?
By Kumar Shanu · Published · 6 min read
Not legal, tax or investment advice.
How card payments work comes down to four parties and a network. The cardholder’s bank (the issuer) and the merchant’s bank (the acquirer) are connected by a card network such as RuPay, Visa or Mastercard. In seconds, the acquirer asks the issuer through the network to approve the payment: that is authorisation. Later, often in daily batches, the transactions are confirmed (clearing) and the money moves from issuer to acquirer to merchant (settlement), less fees. Chip cryptograms, 3-D Secure and tokens protect each step.
Indian exporter or freelancer? Payzoplus gets you paid from abroad, in rupees.Open a free account →
On this page
Who is involved in a card payment?
Most card payments run on what is called the four-party model: two customers, two banks, and a network in between.
| Party | Who they are | What they do |
|---|---|---|
| Cardholder | The customer | Presents the card, phone or saved token; authenticates if asked |
| Merchant | The seller | Accepts the card through a terminal, website or app |
| Acquirer | The merchant’s bank or its acquiring partner | Signs up the merchant, sends its transactions into the network, pays the merchant |
| Card network | RuPay, Visa, Mastercard and others | Routes messages between acquirers and issuers, sets the scheme rules, runs clearing |
| Issuer | The cardholder’s bank | Approves or declines, debits the cardholder, pays the acquirer |
Between merchant and acquirer there are often more layers: a payment gateway for online payments, a payment aggregator that signs up many small merchants under one acquiring relationship, and a processor that runs the technology for a bank. They change who does the work, not the basic flow. Where one company is both the issuer and the acquirer, as some closed card schemes are, the model is called "three-party".
Step 1: What happens during authorisation?
Authorisation: a question and an answer in seconds
Merchant
Card read or details entered
Acquirer
Builds the authorisation request
Card network
Routes by the card’s BIN
Issuer
Checks funds, limits, risk
Approve or decline
Code travels back the same path
The merchant’s terminal or checkout collects the card data and the amount. The acquirer packages it as an authorisation request and passes it to the card network, which reads the first digits of the card number, the bank identification number or BIN, to find the issuer. The issuer checks that the card is valid and not blocked, that the cardholder has the funds or credit, and whether the transaction looks risky. It answers approve or decline, and the answer goes back the same way.
An approval is a promise, not money. On a credit card, the issuer reduces the available limit; on a debit card it usually places a hold on the funds. Nothing has yet moved between banks. For hotels, car hire or fuel, the merchant may authorise an estimate first and adjust it later.
How the card proves it is real
In a shop, an EMV chip card generates what EMVCo calls a one-time-use security code, a cryptogram, for every transaction. The issuer can verify it, and it cannot be reused, which is why chip cards are far harder to counterfeit than magnetic stripes. Contactless cards and phones use the same idea.
How the cardholder proves it is them online
Online, there is no chip to read, so issuers use EMV 3-D Secure, EMVCo’s protocol for authenticating card-not-present purchases. The merchant sends the issuer data about the transaction, the payment method and the device. For many low-risk purchases the issuer approves without bothering the customer; for riskier ones it challenges with an OTP, a biometric or another check. In India, RBI’s authentication rules require two factors for most domestic digital payments, and from 1 October 2026 card issuers must have a mechanism to validate non-recurring cross-border card-not-present transactions when an overseas merchant or acquirer asks for authentication.
Step 2: What are clearing and settlement?
After authorisation, the merchant captures the transaction, confirming the final amount, often in a batch at the end of the day. That starts the back-office half of the payment, which runs on a slower rhythm.
From approval to money in the bank
- 1
Capture
The merchant confirms the final amount for each authorised sale, usually in a batch.
- 2
Clearing
The acquirer submits the captured transactions to the network, which passes each one to the right issuer and works out what each bank owes.
- 3
Settlement between banks
Issuers pay acquirers the net amounts through the network’s settlement arrangement, less interchange.
- 4
Merchant payout
The acquirer or aggregator credits the merchant, less its merchant discount, on the agreed cycle.
- 5
Cardholder billing
The issuer posts the transaction to the account or statement.
This split explains a common puzzle: a customer sees a payment "pending" in their app while the merchant has not been paid yet. Authorisation has happened; clearing and settlement have not.
Also readWhat is PCI DSS v4, and what does it mean for a business that takes cards?Where do the fees go?
The merchant pays its acquirer a merchant discount rate (MDR), a percentage or fixed charge per transaction. Out of that, the acquirer pays interchange to the issuer and scheme fees to the network, and keeps the rest. Visa describes interchange as transfer fees between acquiring banks and issuing banks, and notes that merchants do not pay interchange directly: they negotiate and pay a merchant discount to their own financial institution. Interchange rates are published by each network and differ by card type, merchant category and country, so it is worth asking your acquirer for a breakdown rather than relying on a single figure.
Who pays and who receives
| Paid by | Received by | |
|---|---|---|
| Merchant discount | Merchant | Acquirer (shares it out) |
| Interchange | Acquirer | Issuer |
| Scheme fees | Acquirer and issuer | Card network |
| Cardholder fees, interest | Cardholder | Issuer |
What happens with refunds, failures and chargebacks?
A refund is a new transaction in the opposite direction, started by the merchant. A failed transaction, where the customer is debited but the payment does not complete, is a different matter. In India, RBI’s circular of 20 September 2019 on harmonising turnaround times (RBI/2019-20/67) fixes the limits. For a card payment at a point of sale where the account is debited but the merchant does not receive confirmation, the auto-reversal must happen within T+5 days; for a card-to-card transfer not credited to the beneficiary, within T+1 day; and for an ATM that does not dispense cash, within T+5 days. Beyond those limits, the bank owes the customer ₹100 a day of delay.
A chargeback is the cardholder disputing a payment with the issuer: for fraud, goods not delivered, or a duplicate charge. The issuer takes the money back from the acquirer, which recovers it from the merchant, who can contest it with evidence under the network’s rules. Our guide to chargebacks and disputes covers the process for exporters.
How do tokens change the picture?
In a tokenised payment, the merchant never handles the real card number. A phone wallet or a saved card holds a token issued for that device or merchant, and the network maps it back to the card for the issuer. In India, RBI’s card-on-file rules mean merchants and gateways may not store card numbers at all, so saved cards are tokens. The flow above stays the same; only the data in the messages changes. See card tokenisation in India and network tokens vs PCI vaulting. Businesses that still handle card data must meet PCI DSS v4.
For an exporter billing overseas clients, card acceptance is one option among several. Large B2B invoices are more often paid by bank transfer, where a local receiving account avoids both card fees and chargeback risk.
How Payzoplus helps you
The payments tech, without building it
- Payzoplus gives you receiving accounts, invoice matching and settlement to your bank in one dashboard and app — no integration needed to start.
- Every payment arrives already matched to the customer who sent it, so reconciling is one step, not a hunt.
- Rupees reach your own bank account on T+1 after you reconcile.
No setup fee · No monthly fee · Verification usually takes one working day
Frequently asked questions
What is the difference between an acquirer and an issuer?
The issuer is the cardholder’s bank; it issued the card and approves or declines each payment. The acquirer is the merchant’s side; it signs up the merchant, sends its transactions into the card network and pays the merchant.
Why does a card payment show as pending?
Because it has been authorised but not yet cleared and settled. The issuer has approved and reserved the amount, but the final transaction has not been submitted and settled between the banks.
How long does a bank have to reverse a failed card payment in India?
Under RBI’s 2019 turnaround-time circular, a failed point-of-sale card transaction must be auto-reversed within T+5 days, and a failed card-to-card transfer within T+1 day. After that, the bank pays ₹100 a day of delay.
Who pays interchange?
The acquirer pays it to the issuer. The merchant does not pay interchange directly; it pays a merchant discount to its acquirer, which covers interchange, network fees and the acquirer’s own margin.
Sources
The primary texts this article was checked against, on 30 October 2026.
General information, not tax, legal or investment advice. Rules and products change: confirm the details for your business with your CA, your bank or the regulator.
How useful was this article?
Be the first to rate it.

Comments
Be kind and stay on topic. Comments with links or contact details are checked before they appear.