FinCEN Travel Rule Explained
If your business moves money or cryptocurrency, the FinCEN Travel Rule is one of the most important (and most misunderstood) AML requirements you’ll encounter. Despite its name, it has nothing to do with travel; it requires certain customer information to “travel” with qualifying payments between financial institutions.
What Is the FinCEN Travel Rule?
The Travel Rule is a Bank Secrecy Act (BSA) regulation, formally codified at 31 CFR § 1010.410(f), that requires financial institutions to pass on specific identifying information when they send funds to another financial institution on someone’s behalf. The idea is simple: the information about who sent the money and who’s supposed to receive it should “travel” with the transaction itself, so that every institution in the chain, and law enforcement, if needed, can see the full picture rather than just their own piece of it.
It was first adopted by the U.S. Treasury in 1995. It isn’t a blanket obligation for every financial institution in every context; it’s specifically tied to “transmittals of funds” and “funds transfers” as defined under the BSA framework. Within that scope, it applies equally to banks and non-bank financial institutions (NBFIs) alike, money transmitters, currency exchangers, and similar businesses.
The $3,000 Threshold
The rule applies to any transmittal of funds of $3,000 or more. For transactions at or above that amount, the sending institution must include the following in the transmittal order before passing it to the next institution in the chain:
- Name of the transmittor (sender), and the transmittor’s account number if the payment is ordered from an account
- Address of the transmittor
- Amount of the transmittal order
- Date of the transmittal order (the related recordkeeping rule also references the “execution date” — the day the receiving institution may properly act on the order)
- Identity of the recipient’s financial institution
- As much of the following as was received: name, address, and account number of the recipient, or any other specific identifier
Intermediary institutions have a related but slightly narrower duty: they must pass along whatever information they received from the previous institution in the chain; they’re not required to independently track down information that wasn’t given to them, but they can’t drop it either once it’s in hand.
Why This FinCEN Travel Rule Matters Beyond Traditional Wires
The Travel Rule was written in the mid-1990s with wire transfers in mind, but its language, “transmittal of funds” and “money,” has proven flexible enough that FinCEN has applied it well beyond that original context. In 2019, FinCEN guidance confirmed that convertible virtual currency (CVC) transactions are subject to the same Travel Rule obligations as fiat wires, meaning MSBs (exchanges, custodial wallet providers, bitcoin ATM operators, OTC desks, and similar businesses) must collect and transmit originator and beneficiary information once a transaction crosses the $3,000 threshold, the same as any bank or money transmitter would.
This has proven to be one of the more operationally difficult AML requirements for crypto platforms to implement, since the infrastructure to pass identifying data between counterparties simply didn’t exist when most exchanges were built. It’s also why “Travel Rule solutions” have become their own compliance-tech subcategory, with vendors building messaging protocols that enable VASPs to securely exchange the required data.
A Threshold Change Has Been on the Table Since 2020, But Isn’t Final
In October 2020, FinCEN and the Federal Reserve Board jointly proposed lowering the Travel Rule (and the related Recordkeeping Rule) threshold from $3,000 down to $250 for transactions that begin or end outside the United States. The domestic threshold would stay at $3,000. The same proposal sought to clarify that “money” under the rule includes convertible virtual currencies and other digital assets with legal-tender status.
That proposal has not been finalized. It’s still sitting as a pending rulemaking years later, meaning the operative threshold for now remains $3,000 for both domestic and cross-border transactions. Institutions should watch this space, though, if it does move forward, it would meaningfully expand the volume of cross-border transactions subject to full Travel Rule data collection.
Aggregated Transmittals
One nuance worth understanding: FinCEN guidance addresses what happens when an institution aggregates multiple customers’ transmittal orders into a single bulk transfer, a common practice among money transmitters moving funds through a correspondent bank. In that scenario, the institution doing the aggregating effectively becomes the “transmittor” (or “recipient”) of record for Travel Rule purposes on the bulk transfer, while remaining independently obligated to ensure the underlying customer-level information still travels through the chain via the individual transmittal orders it holds.
This is a different concept from simply totaling up a customer’s separate transactions over a day to see if they cross $3,000, that’s a related but distinct anti-structuring principle under the broader BSA framework (i.e., customers can’t break up transactions specifically to duck reporting thresholds), and it carries its own separate SAR-filing considerations rather than being a stated mechanical trigger within the Travel Rule’s text itself.
These are different concepts. The Travel Rule’s discussion of aggregated transmittals concerns how institutions transmit information when bundling multiple payment orders. It should not be confused with CTR aggregation or structuring analysis under the Bank Secrecy Act.
The FinCEN Travel Rule in a Global Context
The U.S. Travel Rule doesn’t exist in isolation. It’s the domestic implementation of a broader international standard: FATF Recommendation 16 (originally Special Recommendation VII, dating to 2001), which governs traditional wire transfers and value transfers. Note that R.16 itself doesn’t directly cover VASPs; the crypto-specific “Travel Rule” for virtual asset service providers sits under a separate standard, FATF Recommendation 15, which FATF extended to VASPs in 2019.
Other jurisdictions have gone beyond the U.S. threshold; the EU’s Transfer of Funds Regulation, effective December 2024, imposes a zero threshold for crypto-asset transfers, meaning every transaction requires full Travel Rule compliance regardless of size. FATF also revised Recommendation 16 in June 2025, adding fraud and the financing of proliferation as explicit objectives alongside its original anti-money-laundering and counter-terrorist-financing purpose. Financial institutions have until the end of 2030 to come into compliance with the revised standard, so this isn’t an immediate change in obligations.
For any business operating across borders, this creates a compliance patchwork: the threshold, the required data fields, and even what counts as a “transaction” for Travel Rule purposes can differ meaningfully across jurisdictions.
The Bottom Line
For crypto businesses, implementing the Travel Rule is no longer simply a matter of policy drafting. It requires operational processes that can collect, retain, and securely transmit customer information when required. As regulators continue to focus on digital asset compliance, businesses should periodically review their Travel Rule procedures to ensure they remain aligned with evolving U.S. and international standards.
References
- 31 CFR § 1010.410 (Travel Rule / Recordkeeping Rule) — eCFR: https://www.ecfr.gov/current/title-31/subtitle-B/chapter-X/part-1010/subpart-D/section-1010.410
- FFIEC BSA/AML Examination Manual — Funds Transfers Recordkeeping: https://bsaaml.ffiec.gov/manual/AssessingComplianceWithBSARegulatoryRequirements/09
- FinCEN, “Funds ‘Travel’ Rule” Advisory (Ref. Interpretive Guidance): https://www.fincen.gov/system/files/advisory/advissu7.pdf
- Federal Register, “Threshold for the Requirement To Collect, Retain, and Transmit Information on Funds Transfers…” (Oct. 27, 2020 NPRM): https://www.federalregister.gov/documents/2020/10/27/2020-23756
- Davis Polk, “FinCEN and the Federal Reserve Board Propose Travel Rule Amendments”: https://www.davispolk.com/insights/client-update/fincen-and-federal-reserve-board-propose-travel-rule-amendments-lower
- Elliptic, “What Is the Travel Rule?”: https://www.elliptic.co/blockchain-basics/what-is-the-travel-rule
- Corporate Compliance Insights, “FinCEN’s Proposed Changes to the Recordkeeping and Travel Rule Thresholds”: https://www.corporatecomplianceinsights.com/fincen-changes-recordkeeping-travel-rule-thresholds/
- FinCEN, Funds “Travel” Rule Advisory — aggregated transmittals guidance (Q&A 14): https://www.fincen.gov/system/files/advisory/advissu7.pdf
- FATF, “Update to Recommendation 16 on Payment Transparency” (June 2025): https://www.fatf-gafi.org/en/publications/Fatfrecommendations/update-Recommendation-16-payment-transparency-june-2025.html
- ABA Banking Journal, “FATF releases revisions to international standard for payment transparency” (June 2025): https://bankingjournal.aba.com/2025/06/fatf-releases-revisions-to-international-standard-for-payments-transparency/
This post is intended for general informational purposes and does not constitute legal advice. Contact Hodder Law now for specific advice related to your situation.
