Transaction Laundering: How Hidden Activity Creates Fraud, Chargebacks, and Merchant-Account Risk

Transaction laundering is when a payment provider processes card payments for a business it never approved, reviewed, or even knows exists, using someone else’s merchant account. Card networks also call it factoring or undisclosed aggregation. A storefront selling shoes or supplements on the surface can be quietly running card payments for an unlicensed pharmacy, a gambling site, or counterfeit goods behind it, and the acquirer underwriting that merchant account has no idea until a pattern of disputes or a card network audit surfaces it.

The fallout lands in three places at once. The merchant whose account gets used, knowingly or not, faces card network fines and account termination. Their acquirer or payment service provider takes on underwriting risk it never agreed to. And the cardholder who spots an unfamiliar charge from a business they never bought from files a dispute against whatever merchant name shows up on their statement, which is what turns a hidden underwriting problem into an unauthorized-transaction chargeback that counts against a real merchant’s account.

What Is Transaction Laundering?

Transaction laundering happens when a business processes card payments on behalf of a different, unapproved business, using a merchant account it was not underwritten for. It is a form of payment fraud aimed at the acquirer and card networks rather than directly at a cardholder, though cardholders end up caught in the middle when they see charges that do not match what they actually bought.

Legitimate versions of “processing on behalf of another business” exist and are fully disclosed. A merchant of record or a registered payment facilitator takes on that role openly, with the card networks and acquirer aware of exactly who is selling what through the account. Transaction laundering is the undisclosed version: the acquirer has no idea a second business is running transactions through an account it approved for someone else.

How Transaction Laundering Happens

Card network guidance generally breaks transaction laundering into three patterns:

The businesses hiding behind the approved storefront are often ones that would fail underwriting on their own: unlicensed pharmacies, gambling operations, counterfeit goods, or other high-risk categories that struggle to get a standard merchant account.

Red Flags That Point to Transaction Laundering

Acquirers and fraud teams typically look for signals across three areas:

Website Signals

• Hidden pages, subdirectories, or an alternate domain not disclosed at underwriting
• Product categories on the live site that drift from the approved business description
• Page content that changes depending on referral source, geography, or session, masking what is actually being sold

Transaction Signals

• Sudden volume spikes with no matching change in the approved business
• Transactions originating from geographies the merchant does not operate in
• Statement descriptors that do not match the products a cardholder remembers buying
• A chargeback ratio or dispute reason mix that does not fit the merchant’s stated product category

Structural Signals

• Multiple “unrelated” merchants sharing a payment gateway, hosting provider, or domain registrar
• Ownership structures complex enough to obscure who actually controls the business
• Coordinated networks of shell merchants that appear designed to spread transaction volume thin

From Red Flag to Account Risk: How Transaction Laundering Becomes a Monitoring-Program Problem

A red flag on its own does not terminate a merchant account. What actually triggers action is what that red flag turns into downstream: disputes. Every cardholder who does not recognize a laundered charge and files it as unauthorized adds a data point to the exact ratios Visa and Mastercard use to decide whether an account, or an entire acquirer portfolio, is a risk worth keeping. That is the real compliance trigger, and it is why transaction laundering belongs in the same conversation as chargeback thresholds, not filed separately as a fraud footnote.

Visa tracks this through the Visa Acquirer Monitoring Program (VAMP), which folds fraud reports and disputes into a single ratio at both the merchant and acquirer level. Mastercard runs a parallel Excessive Chargeback Merchant program based on dispute volume. The table below reflects both programs’ current, published 2026 thresholds, so the two rows are directly comparable: same year, same ratio-based metric, same source type.

Even a merchant who never touched the laundered activity can watch its own ratio move because of it, since the dispute still posts against the merchant name on the statement.

Disputes, Refunds, Fraud Reports, and Fulfillment Signals That Feed the Ratio

Understanding what is a chargeback is the starting point, but the ratio that gets an account flagged is built from more than chargeback count alone. Five signal types typically feed it:

• Unauthorized-transaction disputes: a cardholder who does not recognize a charge usually files a chargeback for an unauthorized transaction, and this is the reason code laundered activity almost always produces.
• Fraud reports (TC40): issuers can flag a transaction as fraudulent separately from a dispute, and both can count against the same ratio in the same month.
• Refund and return spikes: a sudden jump in refund volume with no matching change in the approved business is often the first internal signal, well before a dispute posts.
• Volume and geography drift: transactions from regions or at a scale the merchant does not normally serve.
• Fulfillment and support complaints: customers contacting support about products the merchant does not actually sell.

Folding this into an existing ecommerce fraud prevention program, rather than treating chargebacks as a separate line item, is what catches a transaction-laundering incident before it has months to compound.

Reserves, Holds, and Termination: What Acquirers Do When the Ratio Slips

An unknowing merchant does not need to have done anything wrong to feel the consequences. Once a merchant crosses into Above Standard or Excessive territory, acquirers typically respond in a predictable sequence:

1. Enhanced monitoring: the acquirer starts reviewing the account's dispute and fraud activity more closely, often monthly instead of at renewal.
2. Rolling reserves or holds: a portion of processing volume gets held back to cover potential future chargebacks and network fines.
3. Fee pass-through: per-dispute non-compliance fees from the card network get passed to the merchant, on top of standard chargeback fees.
4. Account termination: sustained non-compliance can end in the acquirer closing the account outright.

Rebuilding a merchant account after a network-flagged termination is slow and expensive, especially for businesses already in high-risk processing categories. The acquirer's exposure is the same whether the merchant knew about the hidden activity or not, which is why detection speed matters more than intent.

Building a Daily and Monthly Risk Dashboard

Catching transaction laundering, and any other activity that quietly moves your ratio, means tracking signals on two different clocks:

• Daily: new disputes by reason code, refund velocity against the trailing 30-day average, fraud alerts caught before they became chargebacks, and any transactions flagged from unrecognized geographies.
• Monthly: VAMP Ratio and ECM ratio trend line, chargeback-to-order ratio by product line, volume against your underwritten business description, and a running count of days since the last website content review.

Routing chargeback prevention alerts into this same dashboard closes the loop between a brewing dispute and a resolved one, before it has a chance to post against the ratio at all.

The Processor Remediation Evidence Package

If an acquirer flags the account, a canned explanation will not move it back to good standing. What does is a documented package:

• A written incident summary: what was found, when, and how
• A timeline showing detection and response speed, from first signal to resolution
• Evidence of the control that closed the gap, such as domain and content-monitoring logs
• A chargeback ratio trend line showing measurable improvement since the incident
• Documented policy or vendor changes made as a direct result

Contingency and Multi-Provider Planning

A single processing relationship is a single point of failure. Merchants that maintain a backup processor relationship, even a dormant one that is ready to activate, avoid the worst outcome of a monitoring-program termination: a total processing gap while a new account gets underwritten from scratch. Keep the remediation evidence package current at all times, not just after an incident, so it is ready the moment a second provider asks for it. The same underwriting scrutiny is expanding to new sales channels too: as more purchases route through third-party marketplaces or autonomous shopping agents, AI agent chargeback liability raises the same undisclosed-party questions that transaction laundering does, and belongs in the same contingency plan.

Why Chargeback Management Has to Catch Laundered-Transaction Disputes Too

Transaction laundering is ultimately an acquirer and underwriting problem, but merchants downstream still absorb the disputes it generates: cardholders disputing charges they never authorized, filed under whatever business name ended up on their statement. A chargeback management process built only around your own storefront's transactions will not catch disputes that originated from someone else's hidden activity.

Chargeflow is a fully automated chargeback management solution that builds evidence for every dispute you actually receive, whatever triggered it, so unauthorized-transaction claims get a real response instead of an automatic loss.

Here is what that gets you:

• Save time: evidence gathering and submission run automatically, without manual case-by-case work.
• Higher win rate: responses are built around the specific reason code and the evidence available for each case.
• Lower costs: fewer lost disputes and less manual review work reduce overhead.
• Pattern visibility: Chargeflow Insights surfaces the dispute patterns behind your chargebacks, so you can spot something like a compromised account before it pushes your ratio past a threshold.

Transaction Laundering FAQs

Is transaction laundering the same as money laundering?

They are related but not identical. Money laundering disguises the origin of illegally obtained funds. Transaction laundering is the payment-processing mechanism that often enables it in a card-payments context, letting a business that could not pass underwriting on its own run transactions through someone else's approved account.

Who gets penalized for transaction laundering, the merchant or the acquirer?

Both can be. Card networks fine the acquirer for underwriting failures, and the acquirer's agreement with the merchant typically allows it to pass some of that liability, along with account termination, downstream to the merchant whose account was used.

Does a transaction-laundering dispute count against my VAMP Ratio or Mastercard ECM ratio?

Yes. Once a cardholder disputes a laundered charge, it posts as an unauthorized-transaction chargeback against whatever merchant name appears on the statement, and that dispute counts toward that merchant's ratio under both Visa's VAMP and Mastercard's ECM, regardless of whether the merchant knew about the hidden activity.

How is transaction laundering different from friendly fraud?

Friendly fraud is a cardholder disputing a legitimate charge after the fact. Transaction laundering is a merchant-account-level problem: the dispute a cardholder eventually files over a laundered transaction is usually a genuine unauthorized-charge claim, not friendly fraud, because they really did not buy anything from the business named on their statement.

Can a legitimate merchant get flagged for transaction laundering by mistake?

Yes, this is exactly what happens to an "unknowing merchant." A hacked account, compromised credentials, or a rogue employee can route unauthorized transactions through a legitimate business's merchant account without the owner's knowledge, and the business still faces the ratio impact and fallout when it gets caught.

How fast can transaction laundering push a merchant account into a monitoring program?

It depends on volume, not time. Because Visa's merchant-level ratio only applies once an account clears roughly 1,500 transactions in a month, a lower-volume merchant can absorb a laundered pattern for longer before it becomes statistically visible, while a high-volume account can cross a threshold within a single monitoring cycle.

If unfamiliar disputes are showing up against your business, see how Chargeflow builds a real case for each one, before it ever reaches your acquirer's desk.