An AML policy is the written document that sets how a financial business prevents money laundering and terrorist financing: who is accountable, how risk is rated, how customers are verified, how activity is watched and reported, and how the program is trained and tested. Brazilian and US rules both require it in writing.
A fintech that adds stablecoins does not need a second policy. It needs the existing one to describe the new product, the new risks and a new vendor, and to say which controls someone else runs.
Picture a banking partner asking for the policy during a review. It describes bank-transfer customers, and the product now moves stablecoins to wallets. The reviewer asks for the files that match the text, and there are none. The usual outcome is a rewrite under the partner's eye, with the new flow waiting on it.
What an AML policy is and who needs one
The policy sits at the top of an AML program. It states principles and roles, and records who signed off. Procedures and manuals say how each step is done, and the program is the whole set. The Circular keeps them apart, with the policy in art. 2 and the procedure manual in art. 13, while the US rule calls the whole thing a program.
In Brazil, Circular BCB 3.978 of January 23, 2020 applies to institutions authorized by the Central Bank of Brazil (BCB) (art. 1). It requires a policy that fits four risk profiles: customers, the institution, its services, and its staff and providers (art. 2). The policy has to be documented, approved by the board or, where there is none, the executive board, and kept up to date (art. 7).
In the US, 31 CFR 1022.210 requires each money services business (MSB, the FinCEN registration category) to keep a written program that fits the risks of its location, its size, and the nature and volume of its services (paragraphs (b) and (c)). Whether either rule covers your entity is a question for counsel. Mexico and Colombia have their own regimes, covered in the Mexico guide and the Colombia guide.
Which parts of an AML policy can a provider run for you?
A provider can run the controls that need sight of every transaction. It cannot run the parts about your own business, such as who is accountable and who tests the program. The full responsibility split has fifteen rows, and a policy needs ten sections.
What each policy section states, and who runs it when a stablecoin provider sits in the flow.
Policy section | What it states | A provider can run | Stays with you |
Governance | Roles, named officer, management sign-off | Nothing | All of it |
Risk assessment | Risk by customer, business model and country | Publishes its own country tiers | Your dated, approved assessment |
Customer verification | Who is verified, with what, at which tier | The checks and the decision | Your tiers and the data you send |
Sanctions and wallet screening | Lists, frequency, match handling | Screening inside its flow | What it never sees |
Monitoring and holds | Scenarios, alert owner, escalation | Its own transactions | Your ledger and your answers to holds |
Travel Rule data | Fields that travel with a transfer | Carrying the data | Supplying it correctly |
Suspicious activity reporting | Who decides, how fast, who files | Its own filings | Yours, if your status requires them |
Records | What is kept and for how long | Exports of its side | The join with your records |
Training | Who is trained, on what, how often | Nothing | All of it |
Independent testing | Who tests and what happens to findings | Its own audits | Your review of the program |
On Lumx, verification and screening run inside the API, along with monitoring. Governance, training and independent testing stay with the client. Lumx says it is aligned with the Travel Rule.
Risk assessment: the section stablecoins change first
The assessment decides how heavy every other control is. Circular BCB 3.978 asks for an internal assessment of four profiles: customers, the institution (business model and geography), operations and products across every channel, including new technology, and the activities of staff and providers (art. 10, paragraph 1). Each risk is rated by probability and impact, with heavier controls for higher risk (paragraphs 2 and 3).
The assessment is documented, approved by the officer named to the BCB, and reviewed every two years and whenever the profiles change significantly (art. 12). Adding stablecoins is such a change. An assessment written for bank transfers says nothing about wallets or issuer freezes. Add the rails, the customer types, the countries on each leg and how funds could reach a wrong wallet. An assessment that stops at bank transfers leaves the first wallet alert with no rated risk to point to.
On Lumx, the supported countries page sorts each country into Supported, High-Risk (EDD Required) or Restricted, and the prohibited activities page lists what is refused and what triggers enhanced due diligence. Treat them as inputs, since Lumx's risk appetite is not yours.
Customer verification and screening: what to write down
The policy says who is verified, what evidence each tier needs, what happens on each outcome (approve, ask for more, reject) and when a file is reviewed again. The Circular puts the procedure in a separate manual approved by management (art. 13) and bars a relationship before identification is complete, with a 30-day allowance while monitoring still runs (art. 23). A tier that exists in the policy and not in the onboarding flow is the first gap a reviewer pulls a file to check.
Three decisions belong here. The first is the owner threshold and what happens when no owner can be identified, which the Circular lists as a monitoring trigger (art. 39), with what KYB is as the background. The second is how PEPs (politically exposed persons) are found and approved, where PEP screening in Latin America sets the lists. The third is the sanctions cadence and the trigger for enhanced due diligence. Wallets add a fourth, in wallet screening for stablecoin payouts.
On Lumx, a customer must complete KYC (know your customer, the verification of an individual) or KYB (know your business, the verification of a company and its owners) before transacting. KYC Standard takes about 60 seconds when automated, and Lumx targets one business day for KYB. A business supplies documents for its representative, its UBOs and any shareholder holding 25 percent or more. Smaller holders can be registered as associated parties without documents. An invalid file moves the customer to RFI (request for information, a compliance hold that asks for a document before a transaction clears), and the customer.rfi webhook names the document. Screening runs before every transaction in either direction, and a destination must be approved before a payout, a check that includes sanctions.
Monitoring, escalation and reporting: the clocks the policy sets
The policy sets a clock for each step, and each clock needs an owner.
Clocks the policy has to state, with the rule each comes from.
Step | Clock | Rule |
Monitoring and selection of an operation | 45 days from the operation | Circular, art. 39 |
Analysis, written up in a dossier | 45 days from selection | Circular, art. 43 |
Report to Coaf (Brazil's financial intelligence unit), once the dossier supports it | Next business day after the decision | Circular, art. 48 |
Suspicious activity report, US MSB | 30 calendar days from first detection, copy kept five years | 31 CFR 1022.320(b) and (c) |
A clock the policy sets and the team cannot meet is a finding on its own, since the policy is the thing being tested. Name who reviews an alert, who closes it and who files. The US rule makes a filed report confidential, so add a no-disclosure line (paragraph (d)). Scenarios and thresholds belong in a procedure (stablecoin transaction monitoring), and Travel Rule data gets its own clause (Travel Rule workflow).
On Lumx, a flagged on-ramp or off-ramp is held for review. Compliance asks on the client's usual channel about the relationship between sender and receiver and the purpose, and a transaction unanswered for 24 hours may be refunded. Blockchain legs are monitored with Chainalysis KYT, and fiat legs with an internal stack of AI agents and bureaus plus banking-partner oversight. Thresholds are internal. In Brazil, Lumx identifies and reports external transfers to Coaf as the provider (SPSAV, the company type that holds a virtual asset service authorization) that filed its application and operates under the transition regime, and it says it is aligned with the Travel Rule.
Records, training and testing: the sections that stay yours
Circular BCB 3.978 asks for a record of every operation (art. 28), with its type and channel, plus the name and CPF (the Brazilian individual taxpayer ID) or CNPJ (the company taxpayer ID) of holder and beneficiary. Customer files and operation records are kept for ten years, counted from the first day of the year after the relationship ends or the operation happens, and the analysis dossier is kept for the same minimum (art. 67). When a file is missing, a reviewer reads it as a control that did not run, whatever the policy says. AML audit readiness for stablecoin payments covers the evidence.
The Circular requires staff training (art. 3), due diligence on staff and providers (arts. 56 to 58), and an annual effectiveness report passed to management by March 31 (art. 62). The US rule requires training and an independent review by someone other than the designated officer (31 CFR 1022.210(d)(3) and (d)(4)).
I recommend writing the delegation table into the policy itself and having the compliance officer sign it, instead of leaving it in the vendor contract. A split that lives only in a contract is read once, at signing, and nobody can say later what was handed over. I would also add a list of what the provider cannot see, starting with transfers between your own users inside your own ledger, because no provider can monitor a movement it never receives.
On Lumx, a client can export transactions as CSV and pull account statements, fee statements and an audit trail. A provider's audit goes in your vendor file and does not replace your own independent review.
What changes in the policy when stablecoins are added?
The Circular asks for a prior risk analysis of any new product or technology (art. 3), so write it before launch. Five places change.
The product list names the new flows: collection, then holding, then conversion and payout.
The risk assessment gains wallet exposure, issuer freezes and each country on the route.
Screening and monitoring cover wallet addresses and read two ledgers, the bank leg and the blockchain.
The provider is classed as an outside provider under the Circular and gets its own due diligence, for which the provider due diligence questionnaire is a starting list.
Each end user who moves money is onboarded as a customer of the provider, instead of being pooled under your account.
On Lumx, each such end user is its own customer with its own KYC. A pass-through structure counts as nesting, which the nested payments page prohibits because Lumx cannot screen parties it cannot see.
When writing your own AML policy is the wrong project
A policy that describes controls you do not run is worse than a short true one, because a reviewer tests the text against the files, and the Circular expects audit trails for what it describes (art. 61). A provider's policy with your logo fails the same test, because it describes the provider's customers while the Circular builds the policy on yours (art. 2).
Writing is also premature until counsel settles whether you operate under a partner's authorization or need a registration of your own, since that decides which rule applies. A failed review costs the reader the partner's trust and the time to rewrite under scrutiny, while the product waits. The broader AML guide covers what the rules require.
What this looks like when a fintech adds stablecoin payouts on Lumx
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.
For the policy, the verification and screening sections, along with monitoring, can point to a system that records its own decisions. A customer reaches APPROVED before it can transact, a payee reaches destination.approved before it is paid, and a held payment becomes an RFI. Circular BCB 3.978 applies to Lumx, and Lumx runs its own written AML policy under it. The client's policy sits on top of it.
What joins the two documents is the data the client sends. Each payout carries a purpose and a holder relationship, so the policy should say who checks them. The global payments page shows the flow, and the supported countries list shows where onboarding is open.
Methodology and sources
The BCB text is the consolidated PDF of Circular BCB 3.978, read on November 21, 2026. The Circular implements Law 9.613 of March 3, 1998, which planalto.gov.br did not serve to automated requests that day, so it is cited without a link.
US text was read on November 21, 2026 in the eCFR version of November 19, 2026, 31 CFR 1022.210 and 31 CFR 1022.320. Lumx behavior was read on docs.lumx.io the same day: identity verification, request for information, supported countries, prohibited activities and nested payments. The rest is Lumx's own statement as of that date.
Verified on November 21, 2026. Operational context, not legal, tax, or investment advice. Circular BCB 3.978/2020 checked against bcb.gov.br on November 21, 2026. 31 CFR 1022.210 and 1022.320 checked against ecfr.gov on November 21, 2026.
Cover photo: Viktor Talashuk on Unsplash.
What is an AML policy?
An AML policy is the written document that sets how a financial business prevents money laundering and terrorist financing. In Brazil, Circular BCB 3.978 requires it to be documented, approved by management and kept current. On Lumx, the verification and screening the policy describes run inside the API, along with monitoring.
What should an AML policy for a fintech adding stablecoins include?
The same sections as any AML policy, with the new product analysed before launch. The additions are wallet exposure, issuer freezes, the blockchain ledger and the provider as a vendor. On Lumx, destination checks run before a payout, and the client's own policy covers the rest.
Does a fintech need its own AML policy if its provider has one?
A provider's policy covers its own customers and staff and cannot say who is accountable inside your company. Whether a rule requires your own document is a question for counsel, but a partner will ask what you run yourself. On Lumx, Circular BCB 3.978 applies to Lumx, and Lumx runs its own written AML policy under it. The client's policy sits on top of it.
How often does an AML policy have to be reviewed?
Under Circular BCB 3.978, the policy must be kept up to date, the risk assessment is reviewed every two years and when risk profiles change significantly, and an effectiveness report is due to management by March 31 each year. On Lumx, customer files are reviewed periodically according to risk, and an ownership change after approval enters that flow and raises an RFI.
Who should own the AML policy inside a fintech?
One named officer, with senior management signing the document. The Circular requires a director indicated to the BCB (art. 9), and the US rule a designated person who cannot also be the independent reviewer. On Lumx, the client's named contact answers held transactions on the usual channel and requests written approval for any nested structure from compliance@lumx.io, while decisions inside the client's policy stay with its officer.





