Transaction Laundering Red Flags: 12 Checks for Acquirers

Transaction laundering red flags: a site that sells what it never declared, no checkout, a mismatched name or MCC, unreachable support, and odd authorization patterns. Visa and Mastercard list them.

Transaction laundering is a hidden seller running card payments through an approved merchant’s account: what it is and the fines. These are the flags the card networks tell acquirers to look for. Each flag is a reason to look, not proof.

Run it: website cloaking checker covers flags 1 to 7 on one URL; SMMP trigger checker covers the numbers behind Mastercard’s 72-hour rule. Flags from the 4 Aug 2026 Mastercard manual and the October 2024 Visa guide.

The 12 flags at a glance

group flags where to look network
website 1-3 the merchant’s storefront and contact pages Mastercard 6.2.2.8 (Europe Region e-commerce, recommended)
website 4-7 declared business, checkout, name and MCC, links Visa AACQ.C8
transactions 8-12 authorization data Mastercard 6.2.2.8
Visa transaction data similar amounts, unusual count, mismatch with the underwritten business, repeat IP or location the acquirer’s data Visa AACQ.C8
scam-merchant triggers approval-rate collapse, GRIP letter, new-merchant scam signals, MMSP alert Mastercard SMMP explained Mastercard 7.2.1

On the website

Mastercard’s rulebook recommends these checks at onboarding and rescreening for e-commerce merchants in its Europe Region (Security Rules and Procedures, Merchant Edition, 4 Aug 2026, rule 6.2.2.8):

# flag
1 unrealistic promotions, including countdown timers
2 products unrelated to the merchant’s business or MCC
3 customer service contact that is unreachable, unanswered, or has no merchant name (generic emails, help-desk sites)

Visa’s Acceptance Risk Standards add (Oct 2024):

# flag
4 the site sells something other than what was declared
5 the site has no checkout or no way to take payments
6 a mismatch in merchant name or MCC
7 suspicious links to the URL and backlinks

In the transactions

Mastercard, same rule, as part of transaction monitoring:

# flag
8 very low authorization approval rate
9 many authorizations without a CVC 2
10 low CVC 2 match rate
11 no 3DS when adding a card on file, except where PSD2 or its successor requires it
12 big authorization volume from issuer countries that do not match the merchant’s target market

Visa adds: transactions with similar amounts, an unusually high count, transactions that do not fit the underwritten business, and recurring transactions from the same IP address or location.

What to do when one fires: steps

  1. Capture the merchant site now, as a reviewer and as a customer, with the time.
  2. List every URL linked to the merchant: approved, redirected, on the checkout.
  3. Compare the descriptor, the legal name and the MCC: merchant descriptor.
  4. Pause payment or block temporarily if the alert is strong (Mastercard: “should take measures, such as pausing payment”).
  5. If the investigation confirms a scam merchant, block authorization (rule 7.2.1).
  6. After a termination, add it to MATCH Pro within 5 calendar days: MATCH list.

Mastercard: “Where such alerts are triggered, the Acquirer should take measures, such as pausing payment to the Merchant and/or temporarily blocking such payment.”

What a website scan adds

The first seven flags sit on the site. A scan loads it the way a reviewer would and the way a customer would, and compares. A site that shows a clean shop to the first and something else to the second is the strongest flag of all: website cloaking checker. More: how we check websites.

Shell merchant · Merchant descriptor · Mastercard BRAM program · Merchant monitoring

Want this run on your portfolio? For acquirers and PayFacs.

See also: for payment processors · KYB website verification

Questions

What are the signs of transaction laundering?

On the site: products unrelated to the merchant's business or MCC, unrealistic promotions, unreachable support. In the data: very low approval rate, low CVC 2 match, volume from issuer countries that do not fit the market. Mastercard and Visa list these.

How do you detect transaction laundering?

Visa's guide: use web crawling, review transaction data for unusual patterns, verify that each merchant website sells only what was declared and has a checkout, and monitor for mismatched merchant names and MCCs.

What should an acquirer do when an alert fires?

Mastercard says the acquirer should take measures such as pausing payment to the merchant or temporarily blocking it.

Is a mismatch proof of laundering?

No. A flag means a human looks at the site. Proof is a different business behind the checkout.

How many red flags does it take to call it transaction laundering?

None is proof, and the rulebooks give no count. One strong flag, such as a site that shows reviewers a clean shop and customers another, is enough to open an investigation.

Where do the flags come from?

From rulebooks: Mastercard Security Rules and Procedures, Merchant Edition, rule 6.2.2.8 (flags 1-3 and 8-12), and Visa's Acceptance Risk Standards, control AACQ.C8 (flags 4-7).