Money laundering red flags are facts about a customer, a payment or a wallet that suggest funds are disguised, split or unrelated to the customer's real business. No single flag proves a crime. In stablecoin payments they fall into customer behavior, wallet exposure and structure, and a team reads them together before it holds, asks or reports.
FinCEN, the US Financial Crimes Enforcement Network, lists 30 indicators for virtual currency in its advisory FIN-2019-A003 of May 9, 2019. This post turns them, with a typology collection from COAF, Brazil's financial intelligence unit, into 16 red flags for business payouts and collections, on rails such as Pix (Brazil's instant payment system, run by the Central Bank). Each comes with an innocent explanation and the document that settles it. The rules that run these checks are in monitoring rules and false alerts, and the legal duty is in stablecoin AML compliance for fintechs.
How money laundering shows up in a stablecoin payment
Laundering has three steps. Placement is getting dirty money into the system: deposits or wires from unrelated sources, quickly turned into stablecoin. Layering is breaking the trail: many small transfers, rapid conversions, hops across blockchains and mixers. Integration is spending the result as if it were clean, for example in a supplier payout or a payroll run.
A confirmed stablecoin transfer cannot be recalled, so the useful checks come before the payout leaves. They ask two questions: who really owns this money, and does this payment fit the business the customer described? Every flag below asks one of them.
On Lumx, the first question is answered at onboarding: every customer goes through KYC (know your customer, the verification of an individual) or KYB (know your business, the verification of a company and its owners) before funds move. The second is answered against what the customer declared at the same step.
Which money laundering red flags matter in B2B stablecoin payments?
Sixteen, in three groups: rows 1 to 11 are about the customer and the shape of the flow, rows 12 to 14 about the wallet and network, rows 15 and 16 about identity and change. Twelve trace to a numbered indicator in FinCEN's advisory. Four are additions for business flows and are marked as such.
Sixteen red flags for B2B stablecoin payments, the FinCEN indicator behind each, the innocent cause that trips it and the evidence that settles it.
# | Red flag | Basis | Innocent cause | What settles it |
1 | Flows differ from the business the customer declared | B2B addition | The business grew into a second line | Updated expected activity, plus invoices or contracts for the new line |
2 | Amounts cluster just under a limit, or one sum is split across senders or days | FinCEN 15, 21 | The customer sizes payouts to a provider or rail cap | The cap sitting above the cluster |
3 | Many unrelated senders pay one receiver, and the funds leave soon after | FinCEN 7, 14 | A marketplace or payroll run, where fan-in is the product | The declared model and the sender contracts |
4 | Funds arrive and leave in minutes, in near-equal amounts | B2B addition (COAF 2.84) | A treasury or payout flow where pass-through is intended | The declared flow of funds and who owns the money |
5 | The payer's name differs from the account holder | B2B addition | A parent company or the customer's own treasury entity | The relationship document and an ownership chart |
6 | The customer routes money for businesses nobody onboarded | B2B addition | An agency model the customer did not think to disclose | Onboarding each underlying party, or written approval of the structure |
7 | Deposits from disparate jurisdictions, quickly converted to stablecoin | FinCEN 6 | A multinational customer collecting from clients abroad | The customer invoice behind each deposit |
8 | Several rapid conversions between assets with no stated purpose | FinCEN 19, 21 | Treasury rebalancing or a hedge | The treasury policy or the trade rationale |
9 | The counterparty is an unregistered or offshore exchanger with no tie to where the customer operates | FinCEN 9, 10, 11 | A licensed exchange chosen for liquidity | The counterparty's licence and jurisdiction |
10 | The customer declines or stalls on KYC or source-of-funds requests | FinCEN 25 | The request reached the wrong person, or an accountant holds the document | The document, or a contact who can supply it. A refusal that persists is the flag |
11 | The volume or size of payments is not supported by the customer's means or history | FinCEN 26, 28; COAF 2.84 | A real step up: a new contract, a seasonal peak, a funding round | Revenue documents, contracts or bank statements |
12 | The wallet is linked to darknet markets, ransomware, extortion or sanctioned addresses | FinCEN 1, 2, 4, 16 | Indirect exposure through an exchange wallet that pools many users | The share of funds and the hops, not the mere presence of exposure |
13 | Funds pass through a mixing or tumbling service | FinCEN 5 | A privacy habit the customer can explain | The trace and the explanation. A direct hit rarely has a benign one |
14 | Access from Tor, a VPN, a sanctioned jurisdiction or an IP that contradicts the profile | FinCEN 3, 17, 18, 22 | A traveling employee or a corporate VPN | The customer's offices and countries on file |
15 | Credentials, identifying data or a wallet address shared across unrelated accounts | FinCEN 20, 27 | One finance team running several entities of the same group | Ownership documents showing the group |
16 | A new destination, wallet or contact detail, followed by a large payout | FinCEN 29, extended to destinations | A new bank, a new wallet or a new finance contact | Confirmation on a channel on file, and proof of control of the address |
The 16 rows cover 24 of the 30 indicators. The six left out are 8 (contact data tied to a peer-to-peer exchange), 12 (an unregistered money transmitter using an exchange's liquidity for offsetting trades), 13 (kiosks), 23 (a customer much older than the typical user), 24 (a customer who knows little about virtual currency) and 30 (illicit language in message fields). Most depend on kiosks, a consumer's profile or message text, which a business payout flow does not carry. Number 12 comes closest to B2B, and rows 5 and 6 are where a platform would see something like it, but they stay marked as additions. Those rows and row 16 matter more in B2B: a business has parents and agents, and each looks like a third party until someone asks. Rows 4 and 11 also match alert signals in COAF's typology collection, case 2.84: immediate transfer of received funds to third parties, and movement incompatible with the customer's financial capacity.
Each flag has an innocent cause on purpose: a flag opens a question, and the last column closes it. On Lumx, an on-ramp or off-ramp that monitoring flags is put on hold with an RFI (request for information, a compliance hold that asks for a document before a transaction clears), as the docs on RFI describe.
Why one red flag is never enough
The advisory says no single red flag is necessarily indicative of illicit conduct, and institutions should weigh the customer's history and whether more than one indicator appears before deciding that activity is suspicious.
The same holds for structuring. FinCEN's SAR FAQs of October 2025 say a transaction at or near the $10,000 currency reporting threshold is not, by itself, enough to require a suspicious activity report. That is a US cash threshold, so here it is an analogy: clustering under a limit is a reason to look, not a finding.
I would never act on a single row of the table. I would act when two flags from different groups meet, for example an address with indirect exposure plus a payer who is not the account holder, because the first is about the wallet and the second is about the customer, and one rarely explains the other. I would put the question to the customer before holding anything for longer, since most pairs resolve with one document.
On Lumx, a customer whose expected activity changes materially, or whose volumes or funding structure need more validation, is asked for source of funds or wealth documents through an RFI. Rows 10 and 11 are where that request is made. Accepted documents include bank statements, revenue invoices, wallet ownership evidence and exchange statements, like the last column of the table. More in source of funds for crypto off-ramps.
What should a payments team do when red flags stack up?
Hold the payment, not the relationship.
Ask one specific question, in writing, with a deadline. "Who is the payer and what is the invoice?" beats "please explain".
Record the flags, the answer and the decision, with the reviewer's name.
If the answer does not remove the flags, escalate to whoever files reports, and stop moving funds for that customer until they decide.
Reporting belongs to whoever has the legal duty. In Brazil, a report on a suspicious operation goes to COAF, and Lumx files it for its customers' operations as the virtual asset service provider that applied for BCB authorization and operates under the transition regime of Resolution BCB 520/2025, Article 88. What a report holds and when it is due is in the post on reporting from Brazil. In Colombia, per Lumx's own statements as of November 9, 2026, reports to the financial intelligence unit (UIAF) are made by the banking partner.
On Lumx, a transaction that Lumx's monitoring flags is put on hold and compliance reviews it. If it is not a false positive, compliance sends an RFI on the customer's usual channel, email or Slack, asking for the sender and receiver relationship, the purpose and the expected outcome. The customer has 24 hours to answer or the transaction may be refunded to the sender. Compliance decides whether to release it.
When a red-flag list is the wrong tool
It replaces knowing the customer. Rows 5 and 6 are only visible if someone knows the owners, and a hidden owner defeats every row. Who counts as an owner is in beneficial ownership across LatAm.
It becomes a refusal rule. Declining a customer for row 14 alone, because the finance lead logs in over a VPN, turns a question into a penalty.
It is aimed at a business that should not have been onboarded. The prohibited activities in the Lumx docs, among them unlicensed money services, shell banks and pass-through accounts for undisclosed parties, are decided before any flag exists.
What this looks like on a Lumx payment
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
Take a marketplace that collects over Pix and pays sellers abroad. Each seller is onboarded as its own Lumx customer, so rows 5 and 6 have an answer before any payment. The Lumx docs on nested payments allow a customer to move only its own funds for its own business, and name pooled buyer money paid out to sellers nobody onboarded as what is not allowed. Where named virtual accounts are available, the account carries the customer's own name, so row 5 has a hard fact to compare. Onboarding collects the source of funds, expected monthly revenue, expected transaction volume and counterparties, the profile row 1 compares against.
Before a payout, a new destination has to be approved. On BRL and Bre-B (Colombia's instant payment system) payouts the banking partners screen it for sanctions and check the payee name. A transfer to an external wallet from someone who is not a customer goes through pre-transaction screening and Chainalysis KYT, which covers blockchain activity across every type of wallet, so rows 12 and 13 are read on the wallet side. See wallet screening for stablecoin payouts for detail.
Rows 2 and 11 meet the limits. A transaction that would pass its type's single, daily or monthly limit is rejected with a 422 and the TRANSACTION_LIMIT_EXCEEDED code, and reading the customer with includeTransactionLimits=true returns used and remaining amounts per type (see the docs). Customers in a High-Risk jurisdiction go through Enhanced Due Diligence (supported countries). After Enhanced KYC or KYB, Lumx sets the limit to fit the financial capacity shown in the documents the customer submitted, which is the evidence row 11 asks for.
Methodology and sources
Checked November 21, 2026. The numbered indicators come from FinCEN's advisory FIN-2019-A003 (flags 1 to 30), read in full (flags on pages 8 to 10, OFAC on page 12). The typology cross-reference is COAF's Casos e Casos, 2021 National Risk Assessment edition, case 2.84. Product behavior is from the Lumx docs pages linked in the text, plus prohibited activities and identity verification, read the same day.
Two sources were not read. The Financial Action Task Force published "Virtual Assets: Red Flag Indicators of Money Laundering and Terrorist Financing" in September 2020, and a targeted update on virtual assets in 2024. fatf-gafi.org returned an access block (HTTP 403) for both paths tried on November 21, 2026, and no archived copy was found, so nothing is quoted from either. COAF's collection predates stablecoin payments, and no Central Bank of Brazil typology was read. Brazil's Law 9.613 of 1998 did not answer on planalto.gov.br that day, so no article of it is stated, and Resolution BCB 520/2025 is cited by number and article, without a link, for Lumx's transition status. The innocent causes, the settling evidence and the grouping of the flags are editorial judgment.
Verified on November 21, 2026. Operational context, not legal, tax, or investment advice. FinCEN advisory FIN-2019-A003 (May 9, 2019) checked against fincen.gov on November 21, 2026.
Cover photo: أخٌفيالله on Unsplash.
What are money laundering red flags in stablecoin payments?
They are facts about a customer, a payment or a wallet that suggest funds are disguised, split or unrelated to the customer's real business. Examples are amounts just under a limit or a payer who is not the account holder. A red flag opens a question and does not prove a crime. On Lumx, a flagged on-ramp or off-ramp is held and the customer is asked for the sender and receiver relationship, the purpose and the expected outcome.
Is one red flag enough to hold or report a payment?
Usually it is enough to ask a question, not to report. FinCEN says no single red flag is necessarily indicative of illicit conduct and that history and the presence of several indicators should be weighed. A direct hit on a sanctioned address is treated differently, because FinCEN's advisory describes OFAC sanctions screening as a separate obligation from the red-flag review. On Lumx, a held transaction is reviewed by compliance, and the customer has 24 hours to answer before the transaction may be refunded to the sender.
Which red flags are specific to stablecoins?
In this post's own grouping, not a sourced list, the wallet and network ones: addresses linked to darknet markets, ransomware or sanctions, plus mixers, chain hops, Tor or VPN access and IP addresses that contradict the customer profile. On Lumx, transfers to an external wallet from someone who is not a customer go through pre-transaction screening and Chainalysis KYT, which covers blockchain activity only.
What should a business do when it sees red flags?
Hold the payment, ask one specific question in writing with a deadline, record the answer, and escalate if it does not remove the flags. Reports go to the financial intelligence unit through whoever must file. On Lumx, compliance reaches the customer on its usual channel, email or Slack, and the response decides whether the transaction is released.
Do red flags change when a platform uses a payments provider?
The platform still owns knowing its own customers, but the provider sees the payment. Two flags matter most: a payer who is not the account holder and money routed for businesses nobody onboarded. On Lumx, each underlying business that moves funds has to be onboarded as its own customer, or the structure has to be approved in writing by compliance before it runs.





