FinCEN Travel Rule: The $3,000 Threshold Remains
FinCEN and the Federal Reserve withdrew a plan to lower the Travel Rule threshold to $250. Learn what stays at $3,000 and what crypto firms should watch next.

The $250 Crypto Travel Rule Plan Is Gone. What Happens Now?
For crypto firms and financial institutions, regulatory uncertainty can matter as much as a new rule. A proposed change can set off years of compliance planning - even when it never comes into force. That's why FinCEN and the Federal Reserve's decision to withdraw their 2020 Travel Rule proposal is worth a closer look.
The plan would have lowered the threshold for certain cross-border transfers from $3,000 to $250 and clarified how the rules would apply to transactions involving convertible virtual currency. The agencies now say they will not move forward with that proposal. The $3,000 threshold remains, and the current Travel Rule hasn't been amended.
This is a real outcome, but it doesn't answer how crypto transfers will be regulated going forward. With the withdrawal, one path to expanded requirements disappears - but the agencies could still come back later with a different approach. Here's what the 2020 proposal would have changed, why regulators stepped back, what businesses and users should do right now, and what to watch next.
What the 2020 proposal would have changed
The proposal, issued by the Financial Crimes Enforcement Network and the Federal Reserve's Board of Governors on October 27, 2020, focused on two related requirements under the Bank Secrecy Act: recordkeeping and the Travel Rule. In practice, the rules require financial institutions to collect and retain certain information about funds transfers and pass relevant information to the next institution in the payment chain.
The existing threshold for those requirements is $3,000. The proposal would have lowered it to $250 for transfers that begin or end outside the United States. That cross-border focus mattered. It wasn't simply a blanket reduction for every domestic payment - it targeted situations where institutions may have less visibility across the full payment path.
The proposal also addressed how the rules define money. It would have clarified that the requirements covered transactions involving convertible virtual currency, along with digital assets that have legal tender status for a recipient. In other words, it aimed to make it clearer that the rules could apply to certain crypto transfers, rather than relying only on definitions built around traditional funds transfers.
These were proposed changes, not requirements that took effect. A proposal can influence compliance planning and systems design, but it doesn't change what covered institutions must do unless a final rule is adopted and becomes effective. The agencies' withdrawal confirms that this proposal will not be finalized as written.
Why the proposed threshold mattered
Lowering the threshold from $3,000 to $250 would have pulled many more transfers into scope. For a bank, money services business, or other covered institution, that can mean collecting and retaining information for more transactions, adjusting monitoring processes, and making sure systems can exchange required information reliably.
The operational impact wouldn't land only on large banks. Smaller institutions and firms with fewer compliance staff could face heavier strain, particularly if they handle lots of low-value international payments. Remittance providers and crypto businesses would also have needed to check whether existing systems could support the proposed requirements.
Separately, the crypto-specific language raised implementation questions. Even if a rule says a transfer is in scope, institutions still have to identify the relevant parties and transmit information across the payment chain in a way that works. That practical issue came up repeatedly in comments.
Why FinCEN and the Fed withdrew the proposal
The agencies received nearly 3,000 comments. Many submissions were substantially similar form letters, but the responses still reflected disagreements about costs, benefits, and technical feasibility.
Critics of the lower threshold argued it would increase compliance burdens for smaller institutions and could steer consumers toward less regulated ways of sending money. That concern isn't unique to crypto. If the cost or friction of using regulated channels changes, regulators have to consider whether people simply move the activity elsewhere.
Some commenters also questioned the need to lower the threshold when institutions already report suspicious activity to FinCEN. Others argued inflation had eroded the real value of the $3,000 threshold and that it should be raised, not lowered. Those positions point in different directions - expanding information collection, focusing on suspicious activity, or updating a threshold that has been in place for decades.
The crypto provisions were also a mixed bag. Crypto service providers and industry groups objected, citing technical limitations and the lack of an international messaging standard for crypto transfers. Some banks and money services businesses supported clearer coverage. The dispute wasn't only whether crypto should be covered. It was also about how the requirement could work across different firms and transfer systems.
The agencies' two reasons for stepping back
First, more than five years had passed since the proposal was issued. The agencies said additional public feedback would help them evaluate any similar future action. Withdrawing the proposal is also a way of giving the public certainty: they won't finalize this proposal without another opportunity to comment.
Second, the crypto market and its legal environment have changed. In the withdrawal notice, the agencies pointed to continued market maturity and newer legal frameworks, including the GENIUS Act, enacted on July 18, 2025. They said any future crypto-related changes should reflect those developments so the requirements are fit for purpose.
That language keeps the door open, but it doesn't commit to a new rule right away. The agencies didn't announce a replacement threshold, a new definition of money, or a timeline. The practical takeaway is narrower: they considered the 2020 proposal outdated enough to withdraw and didn't want to finalize it without further public input.
What changes now for institutions and crypto users
For now, the answer is simple: the existing $3,000 threshold remains. The withdrawal notice does not repeal, amend, or replace the current recordkeeping and Travel Rule requirements. It removes the 2020 proposal as a way to lower the threshold to $250 and add the proposed crypto language.
That matters for compliance teams. A withdrawn proposal isn't a new exemption from rules that already exist. Institutions still have to follow the requirements currently in effect, including obligations to collect, retain, or transmit information when a covered transfer meets the relevant criteria. The notice doesn't tell firms to stop compliance work or ignore current law.
For bitcoin users and other crypto users, there's no immediate change tied to this specific proposal. The $250 threshold never took effect, and the withdrawal doesn't introduce a new threshold. It also doesn't mean every crypto transfer below $3,000 is automatically unmonitored or exempt from all other legal and compliance obligations. What it does mean is that this proposed Travel Rule change is no longer moving forward.
Crypto businesses shouldn't treat the withdrawal as proof that the issue is over. A future proposal could bring a different threshold, revised definitions, or a new implementation plan. The agencies have said they would want public comment before adopting a similar change. So the process is something to watch, not a guarantee that the policy will never change.
A practical compliance reading
If you're making decisions now, separate three buckets:
- Current requirements: Keep applying the rules and thresholds already in force for your institution and activity.
- Withdrawn proposal: Don't treat the 2020 plan's $250 threshold or proposed crypto wording as final.
- Potential future action: Watch for new agency proposals and evaluate scope, definitions, and effective dates before changing systems or customer processes.
This avoids two common mistakes. First, building as if a proposal is already law, which can waste time and money. Second, assuming withdrawal wipes out existing duties or prevents future rulemaking.
For product and engineering teams, the broader lesson is to avoid hard-coding policy assumptions into payment flows when a rule is still only a proposal. Where you can, make thresholds and jurisdictional logic configurable, document which legal requirement each control supports, and keep a clean line between production obligations and contingency planning. That's not a prediction about what regulators will do - it's a way to reduce the cost of adapting later.
What the withdrawal signals about crypto regulation
This decision fits a broader pattern of regulatory activity, but it's still best read narrowly. The notice is about withdrawing a specific proposal, not about stepping back from crypto oversight altogether. FinCEN has also used other legal tools, including action against the MEXC exchange over alleged sanctions evasion. An action aimed at a named platform is different from a rule that could apply broadly to many institutions.
That distinction matters when you're sorting headlines. A proposal can be withdrawn because the agencies want to revisit assumptions, implementation details, or timing. An enforcement action can move ahead under separate authority. One doesn't automatically cancel the other.
Stablecoins also have their own regulatory track. The notice points out that, under the GENIUS Act, the Federal Reserve proposed customer identification requirements for stablecoin issuers, while FinCEN and the Treasury's sanctions office proposed anti-money-laundering programs for those firms. Those steps don't revive the withdrawn Travel Rule proposal. They do show that regulatory treatment can vary by asset type, issuer role, and the legal authority being used.
For the crypto industry, one of the most important details is the agencies' stated desire to account for market changes and emerging legal frameworks before designing a new rule. That pushes implementation and scope to the front of the conversation, not the end. A rule that names digital assets but doesn't spell out workable information-sharing expectations could create uneven results across providers.
What firms should watch next
If FinCEN and the Fed revisit the issue, the next proposal will matter more than guesswork about what the 2020 plan would have done. Compliance and product teams should focus on questions like:
- The covered activity: Does the proposal apply to transfers that begin or end outside the United States, domestic transfers, or both?
- The threshold: Is it lower, higher, or structured differently than the current $3,000 line?
- The asset definitions: How does the text treat convertible virtual currency, stablecoins, and other digital assets?
- The information flow: What information must be collected, retained, and passed between institutions, and when?
- The implementation period: How much time would firms get to update controls, contracts, and technical systems?
- The public record: What do the agencies ask about costs, technical constraints, and effects on consumers and smaller providers?
These questions help you evaluate a real proposal when it appears. The agencies haven't said whether they will propose a new threshold or crypto definition. Until a new proposal is published, businesses should plan around current requirements and treat any future change as an open question.
Key takeaways
- FinCEN and the Federal Reserve withdrew their 2020 proposal to lower the cross-border Travel Rule and recordkeeping threshold from $3,000 to $250.
- The proposed crypto language was withdrawn as well; it was not adopted as a final rule.
- The existing $3,000 threshold and current requirements remain in place. The withdrawal does not amend them.
- Regulators cited the age of the proposal, the comments they received, and changes in crypto markets and legal frameworks as reasons to step back.
- No replacement proposal or timeline has been announced. A future change would require another opportunity for public comment, according to the agencies.
Conclusion
This withdrawal ends one specific proposal, not the bigger debate about how financial institutions should handle cross-border crypto transfers. For now, the $3,000 threshold and existing requirements stay in place, and the proposed $250 threshold (including the crypto wording) does not.
For institutions, the sensible move is to keep existing compliance controls in place rather than building the withdrawn proposal into production as if it were law. For crypto firms, the next meaningful signal will be a published proposal with clear scope, technical requirements, and an implementation timeline. Until then, the policy has changed less than the headline suggests.