Issuing Banks and Acquiring Banks | The Two Banking Sides of a Card Purchase

The issuer stands behind the cardholder

The issuing bank or issuer provides the card account to the customer. Depending on the product, that can be connected to a deposit account, a credit line or another permitted arrangement.

When a transaction arrives, the issuer decides whether to authorise it. It evaluates account status, available funds or credit, card controls, security data and fraud signals. If approved, it takes on obligations under the card network’s rules.

For a credit card, the issuer also carries the credit risk that the cardholder may not repay. For a debit card, the issuer manages access to the customer’s deposit balance and the resulting payment outflow.

The acquirer stands behind the merchant’s acceptance channel

The acquiring bank or acquiring institution enables the merchant to accept card payments. It receives transaction information from the merchant or payment processor, passes authorisation requests toward the card network and receives settlement value on the merchant side.

The acquirer also carries merchant-related risks. It needs to understand the merchant’s business, manage fraud and chargeback exposure, apply scheme rules, settle funds and reconcile merchant activity.

This is why merchant onboarding is a banking risk process rather than simply selling a card terminal.

The network is the common language between the two sides

The card network provides standards for messages, authorisation, clearing, settlement, dispute handling and other scheme rules. It allows an issuer and acquirer that may never have a direct customer relationship with one another to participate in the same payment transaction.

The network is not the cardholder’s bank and not the merchant’s bank. It is the infrastructure and rule system linking the two.

Participant	Primary relationship	Main decision
Issuer	Cardholder	Should this transaction be authorised, and what account or credit exposure results?
Acquirer	Merchant	Should this merchant be accepted, and how should its card transactions be processed and funded?
Card network	Issuer and acquirer participants	How should messages, rules, clearing and settlement connect the two sides?

Follow one card purchase across the two banks

1. The cardholder presents the card to the merchant.
2. The merchant sends the transaction through its acquiring channel.
3. The acquirer routes the authorisation request into the card network.
4. The network sends the request to the issuer.
5. The issuer approves or declines.
6. The response travels back through the network and acquirer to the merchant.
7. Approved transactions later enter clearing.
8. Settlement value moves from the issuing side toward the acquiring side under the scheme’s arrangements.
9. The acquirer funds the merchant under the merchant agreement.
10. The issuer posts the transaction against the cardholder’s account or credit balance.

The merchant never needed to open an account with the issuer. The cardholder never needed to open an account with the acquirer. Interoperability is the product.

Why the issuer and acquirer see different risks

Issuer-side risk	Acquirer-side risk
Cardholder fraud or account takeover	Fraudulent or collusive merchant
Credit-card borrower default	Merchant cannot repay chargebacks or refunds
Incorrect authorisation	Weak merchant underwriting or transaction monitoring
Customer dispute handling	Merchant evidence and dispute response
Card credential compromise	Merchant or processor data compromise

The same transaction therefore creates two different control problems. Good card systems divide responsibilities so the institution closest to each risk manages it.

Why merchant underwriting matters

An acquirer can face losses if a merchant generates transactions, receives settlement, then disappears before customers demand refunds or chargebacks. This can happen in fraudulent businesses, businesses selling long-future delivery or firms that fail suddenly.

The acquirer therefore needs to understand what the merchant sells, delivery timing, refund practices, transaction volumes, fraud patterns and financial capacity.

A merchant that appears attractive because of high sales volume can still be dangerous if those sales create future contingent liabilities.

Why issuer authorisation is not a promise that every dispute will fail

An issuer can approve a transaction based on the information available at purchase time. A later dispute may reveal that goods were not delivered, the amount was wrong, the credential was compromised or a network rule was breached.

Approval therefore says the transaction may proceed under the current state. It does not remove later dispute rights or guarantee that the merchant will keep the funds permanently.

Interchange-related economics connect issuer and acquirer

Card systems can include interchange fees and other network economics between the issuing and acquiring sides, subject to the scheme, product, jurisdiction and commercial arrangements.

These economics help compensate institutions for parts of the card service and risk. They can influence merchant costs, issuer rewards and competitive strategy, but they are only one component of the full card-payment cost structure.

One institution can sometimes perform multiple roles

A large banking group can issue cards to consumers and acquire merchants at the same time. Payment processors and fintechs can also perform technical or commercial functions around these roles.

The conceptual distinction remains useful even when one corporate group sits on both sides. It tells us which customer relationship and which risk function the institution is performing in a particular transaction.

Why the two-bank model creates scale

Without interoperability, every merchant might need a direct relationship with every customer’s bank. Card networks remove that impossible requirement.

The issuer can specialise in serving cardholders. The acquirer can specialise in serving merchants. The network coordinates the common rules. This division of labour allows millions of merchants and cardholders to transact across institutions.

Why settlement still matters beneath the card network

Even the most sophisticated card network cannot escape the fundamental banking question: after clearing determines what the issuer and acquirer owe, how will the obligation be discharged?

Card payments therefore reconnect to the settlement architecture explained in Clearing Versus Settlement and Why Banks Need Central-Bank Money to Settle With One Another.

Why disputes travel backward through the chain

A purchase moves forward from cardholder to merchant. A dispute often moves backward: cardholder contacts issuer, issuer raises the dispute under network rules, acquiring side contacts merchant, merchant supplies evidence, and the financial outcome is adjusted.

This backward path is one reason card systems require durable transaction records. The institutions need to reconstruct what happened after the physical sale may be long over.

Four misconceptions to remove

Misconception	Better model
“The merchant’s bank issued my card.”	The issuer serves the cardholder; the acquirer serves the merchant.
“The card network is my bank.”	The network connects issuing and acquiring participants through common rules and infrastructure.
“The acquirer only provides the card terminal.”	It also underwrites merchants, processes transactions, receives settlement and manages merchant risk.
“Issuer approval makes the transaction irreversible.”	Later refunds, disputes and chargebacks can alter the final financial outcome.

A mastery test

1. Who has the direct banking relationship with the cardholder?
2. Who has the direct acceptance relationship with the merchant?
3. Why does the acquirer need to underwrite merchants?
4. What role does the card network play between issuer and acquirer?
5. Why can a dispute move backward through the chain after settlement?

If those answers connect, the card transaction becomes a two-sided banking system rather than a mysterious message between a terminal and a card.

---