Who is exposed when a merchant fails
Most fraud training looks at the card from the cardholder's side. This course looks at it from the other end, where the money lands, because that is where a different set of frauds lives and where the losses are absorbed.
Start with the structure. European law defines a four party payment card scheme as one in which payments move from the payer's account to the payee's account through the intermediation of the scheme, an issuer on the payer's side and an acquirer on the payee's side. The same Regulation defines an acquirer as a payment service provider contracting with a payee to accept and process card-based payment transactions, resulting in a transfer of funds to the payee.
Read that definition again with a fraud eye. The acquirer has contracted to pay the merchant. It does so before anyone knows whether the goods will arrive.
That is why acquiring is a credit business as much as a payments business. When a cardholder disputes a transaction successfully, the money is taken back from the acquirer, and the acquirer recovers it from its merchant. If the merchant has gone, the acquirer carries the loss. A travel company or a furniture retailer that collects payment months before delivery and then fails leaves its acquirer facing every one of those disputes at once.
So the acquirer's risk is not mainly that criminals will use stolen cards at its merchants, though that happens. Its risk is:
- a merchant that was never real, set up to take money and disappear;
- a merchant that is real but is processing somebody else's sales, which is the subject of a later lesson;
- a merchant that is real, trading and unable to deliver what it has already been paid for;
- a merchant whose customers dispute at a rate that makes it unprofitable, or breaches the scheme's own monitoring thresholds.
Each of those is a different control problem, and none is solved by the fraud screening a merchant runs on its own checkout.
One more piece of vocabulary. The scheme rules call an individual trading location, physical or online, a Merchant Outlet, and much of what follows is about what an acquirer must know about each outlet rather than about the company as a whole. A single company can hold many outlets, and in the frauds that follow, that is usually the point.
Merchant onboarding, and the name rule
The strongest control in acquiring is the one applied before any money moves: deciding whether to take the merchant on at all.
What a bogus merchant looks like. The application is for a business that either does not exist or does not do what it says. Common shapes are a website built to pass review and taken down afterwards, a company registered weeks earlier with nominee officers, a trading name that resembles an established business, a business classification code chosen to attract a lower level of scrutiny than the real activity deserves, and a bank account for settlement that has no visible connection to the applicant.
What underwriting is really establishing is not whether the paperwork is in order. It is three things: that the business exists and trades as described, that the people behind it are who they say and have not been terminated elsewhere, and that the money the acquirer will advance is proportionate to the business it can see.
The name rule is more powerful than it looks. Visa's rules require that the name used to identify a merchant is the name it primarily uses with its customers, that it is displayed at each outlet or on the merchant's website or application, and that it is used consistently, in the same spelling, everywhere it appears: on the transaction receipt given to the cardholder, in the authorisation request, in the clearing record, and in dispute and pre-arbitration records.
That single requirement does a great deal of work. A cardholder who cannot recognise the name on a statement raises a dispute, and a merchant whose statement name does not match the shop they bought from is either careless or hiding. The rule removes the ambiguity that several of the frauds in this course rely on.
One company, several businesses. The rules deal with this directly. Where two or more lines of business operate at the same outlet, each needs its own treatment where any of the following applies: a separate merchant agreement exists for each line, several outlets on the same premises display different merchant names, one line of business is designated by Visa as a high-integrity risk merchant, or an online outlet links to a separate website that qualifies for a different classification code.
That last case is the one to remember. A link from an approved site to a second site selling something quite different is a structure the rules already anticipate, and reviewing only the page submitted with the application misses it entirely.
Transaction laundering
Transaction laundering is the practice of putting one business's card sales through another business's merchant account. The account is genuine, the acquirer's records describe a real and acceptable trade, and the sales flowing through it come from something else entirely.
It defeats almost everything upstream of it. The underwriting was correct about the merchant it examined. The monitoring compares activity with the profile of that merchant. The classification code describes that merchant's trade. None of it is wrong, and none of it is about the business actually making the sales.
Why it is attractive. A business that cannot get a merchant account, because its trade is prohibited, because it has been terminated before, or because no acquirer will underwrite it, does not need one if it can use someone else's. The host may be complicit and paid for the service, may be a shell set up for the purpose, or may be a struggling real business that has been offered a share of the revenue.
What the rules do about it. The scheme rules attack the structures that make it possible, and the clearest examples are in the obligations placed on a payment facilitator, the intermediary that signs merchants under its own acquiring arrangement. Among the requirements in Visa's rules, a payment facilitator:
- must not deposit transactions on behalf of another payment facilitator, which blocks the layering of one intermediary behind another;
- must not contract with a sponsored merchant whose contract to accept transactions was terminated at the direction of Visa or a government agency, which closes the loop that lets a terminated business reappear under a new sponsor;
- must provide the names of principals and their country of domicile for each of its sponsored merchants, along with transaction reports, to its acquirer and to Visa on request;
- must ensure its sponsored merchants comply with the Payment Card Industry Data Security Standard and the Software Security Framework standards.
Read as a set, those obligations are a description of how transaction laundering works, written as prohibitions. Each one blocks a step: hiding behind another intermediary, re-entering after termination, and concealing who is behind the trading entity.
What it looks like from the acquirer's chair. Sales that do not fit the merchant's stated trade: unexpected countries, unexpected hours, average amounts that do not match the goods, a sudden rise with no marketing behind it, refund patterns unlike the sector, or dispute reasons mentioning products the merchant does not sell. The last of those is the most telling, because it comes from the cardholder.
Payment facilitators and sponsored merchants
The payment facilitator model exists for a good reason. A small trader cannot easily obtain its own acquiring arrangement, and an acquirer cannot profitably underwrite thousands of very small merchants one at a time. The facilitator signs them under its own arrangement, and in the scheme's language they become its sponsored merchants.
What moves with that convenience is knowledge. The acquirer no longer meets the merchant; the facilitator does. The acquirer's view of who it is ultimately paying is only as good as the facilitator's own onboarding, which is why the rules place specific obligations on both.
Registration is the main lever. Visa's requirements for an acquirer include registering with Visa each of the following: high-integrity risk merchants, high-integrity risk payment facilitators together with their high-integrity risk sponsored merchants, high-integrity risk ramp providers and their conversion affiliates, and agents that solicit high-integrity risk merchants. Note what that list implies. The scheme wants to know not only the risky merchant but the intermediary that signed it and the agent that went looking for it.
The inclusion of ramp providers and conversion affiliates is worth pausing on, because that is the language of moving between currencies and digital assets. The rules have been extended to cover the intermediaries at that boundary in the same way as any other high-risk acceptance.
What else an acquirer must satisfy. The same requirements call for conducting appropriate due diligence to ensure compliance with the Visa Acceptance Risk Standards, being in good standing in Visa's risk management programmes, completing and fully remediating an on-site operational review of those standards where required, and being investment grade or committing to compensating controls such as collateral requirements as determined by Visa.
That last clause is the commercial reality of acquiring risk in one line. Where the acquirer's own balance sheet cannot absorb the exposure, it posts security, because somebody has to be able to pay the disputes.
Two further prohibitions matter for fairness as much as fraud. A facilitator must not permit a sponsored merchant to transfer or attempt to transfer its financial liability by asking or requiring cardholders to waive their dispute rights. And for a staged digital wallet, the rules restrict what may be deposited at all. Both exist because the dispute right is the cardholder's protection, and a business that can contract out of it has quietly moved its risk onto its customers.
What a dispute actually is
People in this field say chargeback to mean several different things. The scheme rules are more precise, and the precision matters, because the category a dispute is raised under decides what evidence answers it and who ends up paying.
Visa's rules group disputes into four categories, each with numbered conditions:
- Category 10, Fraud. Condition 10.1 and 10.2 cover the liability shift for counterfeit and non-counterfeit transactions at chip terminals, 10.3 covers other fraud where the card was present, 10.4 covers other fraud where the card was absent, and 10.5 covers Visa's own monitoring programmes.
- Category 11, Authorization. Condition 11.1 for a card on the recovery bulletin, 11.2 for a declined authorisation, and 11.3 for no authorisation or late presentment.
- Category 12, Processing Errors. Conditions for an incorrect transaction code, incorrect currency, incorrect account number, incorrect amount, duplicate processing or payment by other means, and invalid data.
- Category 13, Consumer Disputes. The goods did not arrive, were not as described, the service was not provided, the subscription was cancelled.
Three practical consequences follow from that structure.
The category tells you whose problem it is. A category 12 dispute is usually the merchant's or acquirer's own processing mistake and is cheap to prevent. A category 13 dispute is a commercial failure: a delivery, a description or a cancellation that went wrong. A category 10 dispute is the only one that is really about fraud, and a portfolio whose disputes sit mostly in 12 and 13 does not have a fraud problem, however it is being reported internally.
Evidence has to match the condition. The rules provide for the use of compelling evidence in answering certain disputes, and what counts depends on the condition. Delivery confirmation answers a claim that nothing arrived; it says nothing about a claim that the card was used without authority.
Card-absent is its own world. Condition 10.4, other fraud in the card-absent environment, is where online merchants live, and it carries its own pre-arbitration processing requirements and its own monitoring, which the next lesson takes up.
If you take one thing from this lesson, take the habit of asking which condition a dispute was raised under before discussing what to do about it. Most arguments about chargebacks turn out to be two people talking about different categories.
First-party misuse, and the limits of calling it friendly fraud
Some disputes come from the cardholder who really did buy the thing. The trade calls this friendly fraud, which is a poor name for two reasons: there is nothing friendly about it, and a good share of what gets filed under it is not fraud at all.
Three different things wear the same label. The customer who genuinely does not recognise a statement entry, which is a descriptor problem and the merchant's to fix. The customer who is dissatisfied and finds the dispute easier than the merchant's returns process, which is a service problem. And the customer who knows exactly what they bought and disputes it anyway, which is the only one of the three that is dishonest. Lumping them together guarantees the wrong fix, because two of the three are cheaper to solve than to fight.
The scheme's position, and its warning. Visa's rules provide for merchants to certify data that identifies transactions as first-party, which can earn dispute protection under the card-absent fraud condition. They also set out what happens if that is abused. Where Visa determines that a merchant is falsifying data submitted to gain the protection, both of two things follow: Visa contacts the acquirer, merchant or service provider to notify them of the violation, and the merchant loses the ability to use the pre-arbitration processing requirements of that condition altogether.
That is worth reading twice, because it is the shape of every scheme control. The protection is real, it depends on the accuracy of what the merchant submits, and the penalty for gaming it is losing the protection rather than a fine.
What actually reduces it. In order of effect, and none of it is clever: a statement descriptor the customer will recognise, which the name rule already requires; a returns process easier than raising a dispute; clear delivery and cancellation terms with evidence kept; proactive contact when something is late; and retaining the evidence that answers the specific dispute condition rather than a general file of correspondence.
And what to watch in the numbers. A merchant whose disputes are concentrated in consumer-dispute conditions has a delivery or description problem. One whose disputes are concentrated in card-absent fraud has either an acceptance problem or a customer base being targeted. Those two need different work, and the merchant that reports both as fraud will do neither.
Monitoring a portfolio of merchants
An acquirer cannot examine every transaction, and does not need to. What it watches is each merchant against that merchant's own history, and against what the stated trade implies. The measures below are ordinary industry practice rather than rules, and they are chosen because each one has a fraud it detects.
- Deposit volume against forecast. A merchant that applied with an expected monthly volume and submits several times that amount is either growing, which it will be glad to explain, or processing something it did not describe.
- Average transaction value drift. A rising average can mean a new product line; it can also mean the trade has changed into something that was never underwritten.
- Refund ratio, and refunds to cards that never paid. Refunds are a payment out of the acquirer's exposure, and a credit to a card with no matching purchase is one of the oldest ways to move money out of a merchant account.
- Dispute ratio by condition, not in total. A total is a number; the split between the four categories is a diagnosis, as the previous lessons set out.
- Delivery lag. The longer the gap between payment and delivery, the larger the acquirer's exposure if the merchant stops trading, which is why travel, events and furniture are treated as higher risk regardless of the merchant's own conduct.
- Concentration. Many transactions from one card range, one country or one device, at a merchant whose customers should be diverse, is the signature of either testing or laundering.
- Authorisation decline rates. A high proportion of declines with occasional approvals is the pattern of someone trying card numbers rather than selling goods.
What supervisors add to that list. Bank regulators have looked at the same problem from the other side, through the institution that banks a payment processor rather than the merchant. The FDIC's guidance on payment processor relationships, revised in February 2026, asks institutions to set a risk tolerance for this activity and to have policies for due diligence, underwriting and ongoing monitoring of higher-risk processor relationships, and to be alert to consumer complaints suggesting that a processor's merchant clients are obtaining personal account information inappropriately. The OCC's guidance adds a structural signal worth stealing: be alert for processors using more than one bank to process payments for merchant clients. It also states the exposure plainly, warning that a bank without appropriate controls may be viewed as facilitating the fraud of a processor or its merchant client.
Two cautions. First, every one of these produces false alarms, because genuine businesses have good months, change product lines and run promotions. The purpose is to generate a question for the merchant, not a termination. Second, none of it works if nobody can reach the merchant: an acquirer whose contact details are out of date has monitoring it cannot act on, and the frauds in this course all end with a merchant that stopped answering.
The point of a portfolio view is to see the exposure before the disputes arrive, because once they arrive the money has usually already been paid out.
Bust-out, refund abuse and collusion
Three frauds share one mechanism: the merchant is the one committing them, and the acquirer finds out after the money has gone.
Merchant bust-out. The merchant trades normally long enough to earn trust, a higher processing limit and a shorter settlement period. Then it submits a large volume of sales for goods it will not deliver, takes the settlement, and disappears. Every one of those sales becomes a dispute, the scheme takes the money back from the acquirer, and there is no merchant left to recover it from. The tell is almost always the same: a sudden and unexplained rise in volume at a merchant whose delivery lag is long, often just after a limit increase was granted.
Refund and credit abuse. The merchant processes credits to cards that never bought anything, which moves money out of the merchant account to cards the fraudster controls. A variant pays a genuine customer's refund to a different card. This is why a credit without a matching original transaction is a monitoring rule in its own right, and why the authority to issue refunds should not sit with one person at a small merchant.
Collusion with the cardholder. The merchant and the cardholder agree to process a sale that never happened, then split the proceeds, often leaving the issuer to absorb a dispute later. At its simplest this is cash advance disguised as a purchase. It is hard to detect from one transaction and straightforward to see across a portfolio, because the same cards appear repeatedly at the same small merchant.
What makes all three worse. Speed of settlement, long delivery lags, generous limits granted on short trading histories, and a limit-increase process that looks at growth without asking what the growth is for. Each of those is a commercial decision taken for good competitive reasons, and each one enlarges the exposure.
What reduces them. A reserve or collateral against part of the settlement, which the scheme rules themselves anticipate in requiring compensating controls where the acquirer is not investment grade. Delayed settlement for merchants with long delivery cycles. Limit increases that require evidence of the trade behind them. And a termination process that records the principals, so that the same people cannot reappear at another acquirer, which is exactly what the registration and termination rules in the previous lessons are for.
Running acquiring risk honestly
Everything in this course sits against one commercial fact: acquirers compete on how quickly and easily a merchant can start taking payments. Every control described here adds friction to precisely the thing being sold. Pretending otherwise produces policies nobody follows.
So be explicit about where the risk is priced. An acquirer that onboards in minutes is making a deliberate choice to accept a level of merchant fraud, and the honest version of that choice sets a loss budget, holds reserves against it, and reviews it when the losses move. The dishonest version writes a careful policy and quietly approves around it.
Decide what is checked before money moves and what is checked after. Some things can only be done before: who the principals are, whether they have been terminated elsewhere, what the business claims to sell. Others are better done after, with real data: volume against forecast, dispute conditions, refund patterns. A programme that tries to do everything in underwriting is slow and still blind; one that leaves everything to monitoring pays out first and asks afterwards.
Use the scheme's own machinery. Registration of high-risk merchants, facilitators, ramp providers and the agents who solicit them, the acceptance risk standards and their on-site reviews, and the termination records are not paperwork. They are a shared memory across acquirers, and an acquirer that treats them as a filing exercise loses the only view it has of a merchant's history elsewhere.
Keep fraud and financial crime in the same conversation. Transaction laundering is a payments fraud and a money laundering typology at once, and the obligations in the rules sit alongside the anti-money laundering duties the acquirer already has. An institution that reviews merchants twice, in two teams, with two sets of notes, sees less than one that reviews them once properly.
Three questions for any acquiring programme. How much would we lose tomorrow if our largest long-delivery merchant stopped trading? How would we first learn that one of our merchants is processing someone else's sales? And how long after we terminate a merchant can the same people be trading at another acquirer under a new name?
An acquirer that can answer those three has an acquiring risk programme. One that cannot has an underwriting form and a monitoring report.
Thirty questions
Answer all thirty questions, then check your answers. You need 27 out of 30 to pass and receive a certificate. If you score less, you will see which answers were right and wrong, and then go through the course again before you retake the check. Your answers, progress and times are kept only in this browser.
Your answers
Your certificate of completion
Enter your name as you want it to appear, then save the certificate as a PDF. In the print window, choose Save as PDF. A certificate is issued once per completion of the course.
Rate this course
How would you rate this course? Your rating is anonymous — just a number, with no name and no account.
Bring this to your team
Your colleagues can take this course too — it is free, needs no sign-up, and nothing they enter leaves their browser. If your institution wants the same ground covered as structured training for a team, with an instructor and your own cases, we run courses in a classroom or online for groups of ten or more.
Talk to us about training your team → See the paid courses →
Saolix does not record who takes this course, so it cannot verify these certificates. The certificate confirms completion of a free self-paced course and is not an accredited qualification.
Sources
The official documents this course relies on. Laws and guidance change, so check the current version.
- Visa Core Rules and Visa Product and Service Rules, public edition of 24 October 2026 · Visa
- Regulation (EU) 2015/751 on interchange fees, Article 2 (definitions of acquirer, issuer and four party scheme) · EUR-Lex
- Guidance on Payment Processor Relationships, FIL-127-2008 (revised July 2014 and February 2026) · US Federal Deposit Insurance Corporation
- Bulletin 2008-12: Payment Processors - Risk Management Guidance · US Office of the Comptroller of the Currency



