The Card Network Owns the Message. The Acquirer Owns the Merchant Problem.
A card scheme standardizes the transaction so strangers can trust its fields; the acquirer makes that standard enforceable at the merchant. That hand-off explains why a clean network message can still leave the acquirer with a reserve, a chargeback or an unpleasant call to its sub-merchant.
The rule
Put merchant risk with the institution that can suspend the merchant, not with the system that merely routes its message.
The Approved Dinner Is Not the End of Dinner
At 19:04 a restaurant enters an $86 bill.
The terminal supplies merchant, outlet, merchant category, currency, amount, terminal capability.
And the card application selected by tap, chip or manual entry.
It adds the channel evidence.
A contactless cryptogram.
Online credential data.
A cardholder-verification result.
Your acquirer, or the processor acting for it, checks that the message is syntactically usable and entitled to enter the arrangement.
The network routes it to the issuer by card-number range or token mapping.
None of that is yours to change.
Excellent industrial design, this.
An issuer that has never heard of the restaurant can read the request, because the network has made the fields intelligible to strangers.
The issuer then checks an open account.
A valid credential.
Available credit or funds.
Account restrictions.
Fraud signals.
It may approve.
Decline.
Refer.
Or demand another verification.
An approval creates an $86 hold against available credit. Or it earmarks $86 in a debit balance.
It is a decision about the account you issued.
It is not a small judicial finding that dinner occurred.
The distinction gets flattened, because the terminal beeps and the customer goes home.
It becomes much less flattenable later.
The restaurant completes the sale in its batch.
The issuer posts it.
An acquirer credits the merchant.
A cardholder complains.
And a sub-merchant has acquired the habit of accepting money for things that are to happen later.
The network owns the message.
The acquirer owns the merchant problem.
The two positions meet on every transaction, and they are not interchangeable, however handsome your dashboard.
A Network Is a Grammar With Consequences
A four-party network is a multilateral contract among financial institutions. It is not a retail relationship between the scheme and every merchant.
Its rulebook tells you what a credential must look like.
A transaction message.
A merchant acceptance arrangement.
A dispute.
That gives unrelated institutions a common grammar.
A large online sale carrying the wrong merchant category or country code can be routed and priced wrongly even where the amount is perfectly correct.
Pedantry has its occasions.
The network also makes the grammar enforceable among members.
Visa’s published structure puts charter documents, core rules, domestic rules, product-and-service rules and supplemental requirements into a precedence order. Its public rules say that where a rule assigns an obligation to a merchant, the acquirer is responsible for ensuring that it happens.
That is the hand-off.
The scheme needs no direct contract with the florist, the travel seller or your marketplace sub-merchant. It has a member with an acquiring identifier.
And that member has a contract.
A payout file.
A reserve clause.
A terminal configuration.
And eventually a telephone.
Which is why the network approved it is such a poor account of the event.
The network carried an issuer-facing request through a controlled syntax.
The issuer made a decision about its own account.
The acquirer permitted a merchant to use the syntax at all, and advanced merchant proceeds under its agreement.
Three real decisions.
None of them answers the others’ question, however firmly you say approved.
The Eleven Records, Because a Merchant Is Not a Field
Do not store transaction = approved.
That is not a transaction record. It is the opening line of a future disagreement.
The accountable chain has eleven records: network; issuer BIN; acquirer ID; merchant ID; payment facilitator; sub-merchant; terminal or gateway; authorisation; clearing record; settlement bank; reserve holder.
Complete, because each of them answers a different question you will one day be asked.
The network identifies the rule system and the routing arrangement.
The issuer BIN identifies the responsible issuer-side licence.
The acquirer ID identifies the member that submitted merchant activity, and carries its acquiring accountability.
The merchant ID identifies your acceptance location.
The payment facilitator and sub-merchant identify the distribution chain a merchant aggregator has inserted between your acquirer and the storefront.
The terminal or gateway identifies the device or service that gathered the channel evidence.
The authorisation retains the issuer decision.
The clearing record retains the completed financial presentment.
The settlement bank identifies how your institutional obligations are paid.
The reserve holder identifies where your contractual buffer actually sits.
Each BIN or acquiring identifier has one licensee under Visa’s published rules.
There may also be a processor.
A gateway.
A programme manager.
An independent sales organisation.
A payment facilitator.
Several splendidly branded onboarding screens. And a client success manager who has never met the acquiring institution.
There is still one named member for your identifier.
Sponsorship expands distribution. It does not turn responsibility into a communal art project.
Your merchant file has to connect those eleven records to the underwriting facts.
Legal entity.
Beneficial owners.
Business location.
Website or sales materials.
Products.
Bank account.
Historical volumes.
Refund terms.
Prior processing history.
Fraud or sanctions signals.
Expected monthly volume.
Maximum ticket.
Settlement account.
Data-security duties.
Ownership-change notice.
Rights to hold funds.
A merchant boarded as a local retailer can become a marketplace, a subscription seller, or a future-delivery business.
The code continues to parse beautifully. The commercial risk has quietly changed costume.
An Approval Is Not a Presentment
When the restaurant completes the $86 sale, the completed record goes to your acquirer, usually in a batch.
The acquirer checks that it relates to an eligible authorisation, or records a permitted exception, then presents it through the network.
In a dual-message network, authorisation and clearing are separate messages.
Your petrol-pump authorisation becomes a larger clearing record once the fuel is dispensed.
Hotel.
Car rental.
Restaurant tip.
Delayed fulfilment.
That is why the separation exists.
They are also why an approval code should never be treated as a deed of title.
Some products use single-message processing, where financial presentment and authorisation information travel together. Mastercard’s chargeback guide describes distinct single- and dual-message cycles.
So store the chronology.
Do not infer it from the logo on your card.
A late presentment and a disputed ATM withdrawal do not become the same operational event because the consumer calls both a card payment.
Clearing calculates your institutional obligations.
Settlement moves them.
Where an issuer’s cardholders buy more from other acquirers’ merchants than those acquirers’ cardholders buy from its own, that issuer has a net payable.
The relevant acquirers have net receivables.
Your individual restaurant sale is generally not an $86 transfer from issuer to restaurant. It is an item inside a net position, settled through designated settlement-bank and central-bank or commercial-bank arrangements.
Then comes the merchant payout, which is an acquirer credit under the merchant agreement. Next business day, a later scheduled payout, or a faster paid service.
A processor display showing an expected deposit below the sale amount is not a settlement narrative. The difference belongs to pricing.
Nor is your merchant paid when the cardholder pays the bill. The issuer has created a receivable from its cardholder. The merchant’s claim arose from clearing and the acquirer agreement.
Different balance sheets.
It is rude to ask one to keep the other’s diary.
The Reserve Is a Forecast of Awkwardness
Your acquirer normally pays the merchant before it knows whether every cardholder will accept every sale, and whether every promised item will be delivered.
That is the merchant problem in its least poetic form.
You can delay payout.
Set a rolling reserve.
Impose a volume cap.
Require a personal guarantee.
Terminate the relationship.
Not ceremonial punishments. Ways of deciding how much of your future reversal risk you will advance today.
Your reserve needs its calculation base.
Its percentage or target.
Its release conditions.
Its permitted deductions.
Its account segregation.
Its termination tail.
The OCC describes withholding part of each day’s proceeds until a stated balance is reached.
It then asks whether chargeback or loss reserves sit in individual deposit accounts, separate from settlement proceeds.
A distinction with a most inconvenient habit of mattering when the merchant is distressed.
The arithmetic is deliberately not a risk opinion.
A 10% holdback on your merchant’s weekly receipts creates a buffer after one week. It says nothing whatever about a half-million dollars of undelivered bookings.
A payout delayed by three business days may remain far too early where payment was collected 180 days before delivery.
One can admire a percentage and still fail to fund the refunds. Finance has produced entire committees to demonstrate the possibility.
So risk-based underwriting is not a ritual for making small businesses disclose their stationery.
Your café clearing same-day meals usually has point-of-sale evidence of fulfilment.
Your travel seller taking a deposit for a holiday nine months away can disappear after settlement and before delivery.
The same clean network message can carry radically different merchant exposure.
So you examine fulfilment lag.
Refund practice.
Sales pattern.
Adverse information.
The business itself.
Because you are the institution that can withhold, reserve, cap or suspend.
A Chargeback Is Three Arguments Wearing One Name Tag
Settlement ends the ordinary payment cycle. It does not end every complaint.
If a cardholder says the $86 transaction was unauthorised, or that service was not supplied, the issuer assesses the account claim and its own legal duties.
If it pursues a network dispute, the chargeback comes through the network to you. You ask your merchant for evidence, or you accept the reversal.
Your merchant may respond by representment.
A receipt.
Proof of delivery.
A cancellation record.
Authentication data.
Mastercard’s published process runs first chargeback.
Second presentment.
Pre-arbitration.
Arbitration.
In specified cases pre-arbitration carries a 30-calendar-day deadline after second presentment.
That timetable belongs to the scheme procedure. It does not touch your consumer-account duties.
In the United States, a Regulation Z billing-error notice must reach the creditor within 60 days of the first statement showing the error.
Regulation E generally requires an asserted electronic-fund-transfer error to be determined within 10 business days. Where the institution takes up to 45 days, it normally provisionally credits within 10 business days, subject to defined exceptions.
Three clocks on your desk.
Not interchangeable ones.
One is consumer protection.
One is a network process. One is your acquirer’s contractual claim against its merchant.
Calling all three the chargeback rule is how an investigation acquires a deadline and no owner.
The cardholder’s statutory protection does not prove merchant fraud.
A scheme reversal does not write the merchant contract.
The merchant agreement allocates reimbursement, evidence, reserve deductions and recovery between merchant and acquirer.
Each layer keeps its own record, and its own timetable.
Keep all three.
The Ladder, Because Someone Will Say the Payment Cleared
Message syntax?
Read the network specification.
Credential routing?
Go to the scheme.
Merchant admission?
Go to the acquirer.
Sub-merchant oversight?
Go to the payment facilitator and the acquirer.
Settlement obligation?
Read the network arrangements and the settlement-bank terms.
Chargeback?
Read the scheme rules and the merchant contract.
Exception release?
Demand a named acquirer officer.
The network makes a transaction legible enough for strangers to act on it.
A serious accomplishment.
It cannot inspect a sub-merchant’s fulfilment, hold back its payout, amend its reserve, or terminate its acceptance agreement.
Your acquirer can.
When a clean message meets a dirty merchant problem, that is the record that matters.
Put merchant risk with the institution that can suspend the merchant, not with the system that merely routes its message.
What the paper establishes
- A card authorisation, clearing presentment, network settlement, merchant payout, and cardholder repayment are separate events with different authoritative records.
- A card network standardises and routes transaction messages, while the acquirer contracts with the merchant and remains accountable for merchant compliance under the scheme rules.
- Each BIN or acquiring identifier has one licensed member, so sponsorship, processing, and payment-facilitator arrangements do not remove the named member's accountability.
- A merchant-risk record must identify the network, issuer BIN, acquirer ID, merchant ID, payment facilitator, sub-merchant, terminal or gateway, authorisation, clearing record, settlement bank, and reserve holder.
- A rolling reserve, delayed payout, volume cap, guarantee, or termination right allocates merchant reversal risk but does not prove that the reserve covers undelivered obligations.
- Chargeback treatment separates issuer consumer-account duties, scheme dispute procedures, and the acquirer's contractual recovery from the merchant.
- Network rules must be read by applicable edition and geography, then against public law and the acquirer-merchant contract.
- A manual exception requires a named acquirer officer because an exception changes the merchant risk the acquirer has agreed to carry.
Questions
- What does a card-network approval actually prove?
- A card-network approval is the issuer's time-sensitive decision that the account may be charged up to the authorised amount, subject to the network process. It can create an authorisation hold against credit or reserve funds on debit. It does not prove that the merchant performed, that a clearing record will be presented, that the merchant has been paid, or that a later dispute cannot reverse the transaction.
- Why can a perfectly valid card message still become the acquirer's problem?
- A valid message proves that the transaction uses the network's required syntax and can be processed by participating institutions. The acquirer separately contracts with the merchant, submits its activity into the scheme, pays the merchant under the merchant agreement, and must ensure merchant compliance where a scheme rule addresses merchant conduct. A later refund, fraud claim, or chargeback can therefore create a recovery claim against the merchant.
- Who is responsible when a payment facilitator boards a sub-merchant?
- A payment facilitator can enable sub-merchants, but sponsored participation does not remove the responsible network member. The acquiring member remains accountable for activity under its acquiring identifier and must monitor the relevant relationship under network requirements. The payment facilitator and sub-merchant also require clear contractual records, because the commercial brand handling onboarding may not be the institution carrying final network settlement risk.
- What records identify the accountable parties in a card sale?
- The accountable record identifies the network, issuer BIN, acquirer ID, merchant ID, payment facilitator, sub-merchant, terminal or gateway, authorisation, clearing record, settlement bank, and reserve holder. It also preserves the transaction context needed to interpret those records, including amount, currency, merchant category, channel evidence, authorisation response, completion data, and the applicable merchant agreement. Each record answers a different operational question.
- Is an authorisation the same thing as clearing?
- No. Authorisation is the issuer's decision that a requested transaction may proceed against the account. Clearing is the submission and exchange of a completed transaction record and the calculation of related obligations. In a dual-message network, the two are separate messages, so a petrol-pump authorisation of $50 can become a $63 clearing record after fuel is dispensed. An approval code is therefore not an irreversible sale.
- Does network settlement mean the merchant has finally been paid?
- No. Network settlement transfers the net or gross funds that discharge participating institutions' payment obligations through the applicable settlement arrangements. Merchant payout is a separate credit by the acquirer under the merchant agreement and can occur on a different timetable. Even a merchant deposit does not prevent a later network dispute, refund, or chargeback from creating a reversal or contractual recovery claim.
- What is a rolling reserve actually for?
- A rolling reserve is merchant proceeds withheld over time as a contractual buffer for refunds, fraud, chargebacks, fines, or other merchant obligations. It can be built by withholding part of each day's proceeds until a stated target balance is reached. It is not automatically acquirer revenue, and its percentage does not establish adequacy: a 10% holdback on $100,000 of weekly receipts creates only a $10,000 buffer against the merchant's actual reversal exposure.
- Why does a travel merchant receive different acquiring treatment from a café?
- Merchant risk depends on the relationship between payment, delivery, and possible reversal. A café that clears $40 meals on the same day can usually evidence fulfilment at the point of sale. A travel seller taking a $4,000 deposit for a holiday nine months away can fail before delivery, leaving refunds and disputes after settlement funds have been paid out. Risk-based underwriting can therefore support delayed settlement or reserves.
- Is a chargeback just a customer complaint?
- No. A chargeback can involve three separate layers. The issuer assesses the cardholder's account claim and applicable consumer duties; the scheme supplies the message and evidence process between issuer and acquirer; and the merchant agreement determines the acquirer's recovery from the merchant. A United States credit-card billing-error notice has its own 60-day timing rule, which does not itself decide the scheme dispute outcome.
- Which rules control a merchant's card acceptance?
- Merchant card acceptance is controlled by public law and regulation, the applicable network membership rules, the acquirer-merchant agreement, and the particular sale record. Network rules can bind a merchant indirectly because the acquirer must impose and enforce the relevant obligations. The applicable network edition and geography matter because rules change and domestic provisions can displace general requirements. A scheme rule is not automatically a universal legal right.
- Why does a manual merchant exception need a named acquirer officer?
- A manual exception changes the merchant exposure carried by the acquiring institution. It can alter permitted activity, expected volume, maximum ticket, settlement timing, reserve treatment, or a restriction imposed through underwriting. The exception therefore requires an identifiable acquirer officer with authority to approve it and a retained reason. A gateway, processor, payment facilitator, or sales agent can operate a workflow but cannot substitute for that accountable decision.