The Travel Rule is an anti-money laundering requirement that requires originator and beneficiary information to accompany a qualifying transfer. It applies to Bitcoin payments whenever a regulated intermediary sits on either side.

In the US, the FinCEN Travel Rule for crypto sits under the Bank Secrecy Act; in the EU, Regulation (EU) 2023/1113 governs transfers between crypto-asset service providers.

Travel Rule Explained and Its Application

The Travel Rule follows the intermediary, not the asset. When a regulated business sends or receives value for a customer, it must collect defined information about the originator and the beneficiary, pass that information to the next institution in the chain, and retain it. A blockchain record shows addresses and amounts, not names or account references, so the on-chain transaction alone never satisfies the obligation.

That is why Bitcoin payments fall within the scope. The question is not whether the rail is public, but whether a licensed entity is acting as a financial intermediary at either end. Three regimes matter for platforms accepting Bitcoin: FATF Recommendation 16, the funds-transfer and transmittal-of-funds rules under the US Bank Secrecy Act enforced by FinCEN, and Regulation (EU) 2023/1113. Obligations beyond the Travel Rule are set out in this overview of the global regulatory environment for Bitcoin payments.

The FinCEN Travel Rule for Crypto Payments in the US

The FinCEN Travel Rule for crypto is not a separate crypto statute. It is the existing Bank Secrecy Act transmittal-of-funds rule that applies to businesses that qualify as money transmitters, including those dealing in convertible virtual currency, as set out in FinCEN's 2019 guidance on convertible virtual currency business models.

The threshold is transmissions of $3,000 or more. A proposal to lower the threshold for certain cross-border transmittals has been under discussion by FinCEN and the Federal Reserve since 2020, but it has not been finalized and is not law. Plan against the $3,000 figure and monitor the rulemaking.

The originator information that must accompany a qualifying transmittal includes the originator's name, address, and account number; the amount; the execution date; and the recipient financial institution. Beneficiary details travel, too, to the transmittor's financial institution, where they are received. Records are retained for 5 years and produced on request, and FinCEN enforces compliance through examinations, supervisory referrals, and civil money penalties.

Info: The data must be transmitted onward to the next financial institution in the chain, not simply stored internally. Retention alone is a posture of partial compliance and a common examination finding.

The FATF Travel Rule for Crypto: Recommendation 16 Explained

The international baseline is set by the Financial Action Task Force, which extended Recommendation 16 to virtual assets in June 2019. FATF standards are not directly binding: member jurisdictions implement them through domestic law, which is why the details differ between Washington and Brussels.

Recommendation 16 applies to virtual asset service providers, a category covering exchanges between virtual assets and fiat, exchanges between virtual assets, transfers of virtual assets, custody or administration of virtual assets, and participation in the offer or sale of a virtual asset. FATF recommends a threshold of $1,000 or €1,000, above which the full originator and beneficiary data set must accompany the transfer.

Implementation remains uneven. FATF's periodic targeted updates continue to report jurisdictions that have not legislated at all, which produces the sunrise issue: a compliant provider routinely faces a counterparty with no live obligation to send or receive the data. That mismatch is an operational problem, not a legal excuse, and supervisors expect a documented policy for handling it.

Travel Rule Requirements in the EU: The Transfer of Funds Regulation

Regulation (EU) 2023/1113, the recast Transfer of Funds Regulation, has applied to crypto-asset service providers since December 30, 2024. There is no minimum threshold, so information accompanies every transfer of crypto-assets between CASPs, including small-value payments.

The originating CASP collects and transmits the originator's name, distributed ledger address or account number, address details, official personal document or customer identification number, and, where required, the date and place of birth, alongside the beneficiary's name and address or account reference. The originating CASP verifies originator information, while the receiving CASP verifies beneficiary information and performs procedures for transfers that arrive with missing data.

Self-hosted wallets are handled separately. A CASP collects and retains the required information for transfers to or from a self-hosted address, and, for transfers above €1,000, it must verify that the customer controls that address. MiCA, the wider EU conduct regime for crypto-asset services, sits alongside these transfer obligations and is covered in the ElenPAY Lightning Knowledge Hub.

US vs EU Travel Rule Comparison

  • Governing rule: US, Bank Secrecy Act transmittal-of-funds rules enforced by FinCEN. EU, Regulation (EU) 2023/1113.
  • Threshold: US, $3,000 or more. EU, no minimum threshold.
  • Entities in scope: US, money transmitters, including convertible virtual currency businesses. EU, crypto-asset service providers.
  • Applies from: US, existing Bank Secrecy Act rule applied to convertible virtual currency activity. EU, December 30, 2024.
  • Self-hosted wallets: US, treatment depends on the intermediary's role and FinCEN guidance. EU, information collected, with ownership verification above €1,000.

How the Travel Rule Applies to Bitcoin Payments over Lightning

The obligation is identical over Lightning because it attaches to the regulated intermediary, not to the settlement layer. A Layer 2 payment between two licensed providers carries the same data duties as an on-chain transfer of the same value in the same corridor.

What differs is the mechanics. Travel Rule information does not ride inside the Lightning payment: it moves institution to institution over separate compliance messaging channels, so the payment settles on one path while the counterparty data is exchanged on another. In practice, originator details are captured when the customer is identified, and the licensed entity responsible for the transfer attaches them to its own counterparty record.

Speed and cost do not change the analysis. Instant settlement, routing fees of a fraction of a cent, and no chargebacks are commercial advantages, not relief from recordkeeping, screening, or transmission duties.

Quick tip: Log the counterparty provider, not only the payment reference. Because the data exchange occurs provider-to-provider, reconciliation and supervisory queries depend on knowing which institution is on the other side.

Platform vs Payment Provider: Where Travel Rule Responsibilities Sit

Travel Rule obligations sit with the regulated entity that holds the customer relationship and the license or registration covering the transfer. A payment provider that operates the Lightning rail does not take on those obligations by processing the payment, and a platform cannot outsource them by contract. What a contract can do is set out clearly what each party records, what data the platform can access, and how the two sides reconcile. The pattern below is a common starting point, to be confirmed with compliance counsel for each corridor.

  • Customer identification and KYC onboarding: owned by the licensed platform as part of its own customer due diligence program.
  • Originator data capture at checkout: the platform owns the data and the customer's consent, and its checkout flow needs to be able to collect the required fields.
  • Transmission to the counterparty institution: the responsibility of the licensed entity on each side of the transfer, typically through a dedicated Travel Rule messaging solution rather than the payment rail itself.
  • Record retention: the platform retains its own customer and transfer records for the statutory period. A payment provider's transaction records can support reconciliation, but they do not replace the platform's own records.
  • Sanctions and counterparty screening: performed by the licensed entity under its own AML program.
  • Reporting to the supervisor: each regulated party files under its own license or registration.

ElenPAY works with licensed, regulated businesses and manages nodes, liquidity, and custody behind the Bitcoin Lightning payment gateway, with integration via REST API, payment links, a checkout widget, or white-label. ElenPAY does not provide Travel Rule or AML compliance services: those obligations remain with each platform's own compliance function and advisers. ElenPAY's own regulatory position is published in its MiCA compliance disclosures.

Travel Rule Readiness Checklist for Platforms

  • Map the flows. Identify every payment path that crosses a regulated intermediary and record which jurisdiction governs each.
  • Fix the threshold per corridor. $3,000 in the US under the Bank Secrecy Act, no minimum in the EU under Regulation (EU) 2023/1113.
  • Document the data set. List the originator and beneficiary fields captured at checkout, where they are stored, and for how long.
  • Allocate duties in writing. Agree on which party transmits, screens, and retains, and reflect it in the provider contract and the AML policy.
  • Test the sunrise scenario. Decide in advance what happens when a counterparty provider sits in a jurisdiction with no live Travel Rule obligation.

ElenPAY's Commitment to Regulatory Requirements

ElenPAY is a Bitcoin Lightning payment service provider, and meeting regulatory requirements is part of how the business operates rather than an add-on. The ElenPAY team works only with licensed, regulated businesses, publishes its regulatory position under MiCA, and follows Travel Rule, MiCA, and FinCEN developments closely as they apply to Lightning payments. ElenPAY also contributes to the wider industry by publishing clear, sourced explanations of how these rules apply to Lightning, including through the Lightning Knowledge Hub, so that platforms, providers, and their advisers can work from the same understanding of the obligations.

Talk to the ElenPAY Team About Lightning Payments

Travel Rule obligations do not change based on which rail moves the payment, but the split of duties between a platform and its payment provider needs to be documented, not assumed. Platforms should work through that split with their compliance team and legal advisers before finalizing policy, and should confirm with any payment provider what data and records it can make available.

To discuss how a Bitcoin Lightning payment gateway fits alongside an existing compliance program, contact the ElenPAY team. The team can walk through how payments are processed through the gateway and what transaction data is available to the platform. Compliance decisions remain with the platform and its advisers.

Travel Rule and Bitcoin Payments: FAQs

Which agency enforces the Travel Rule for crypto in the US?

FinCEN, a bureau of the US Department of the Treasury, administers and enforces the Bank Secrecy Act rules that create the Travel Rule. Enforcement includes examination, supervisory referral, and civil money penalties, and functional regulators may conduct examinations on FinCEN's behalf. Criminal matters are referred to the Department of Justice.

What is the threshold for the crypto Travel Rule in the US and the EU?

The US threshold is $3,000 or more for a transmittal of funds. The EU has no minimum threshold under Regulation (EU) 2023/1113, so information accompanies every transfer between crypto-asset service providers. FATF recommends $1,000 or €1,000 as the international baseline, which is why national figures diverge.

What is the sunrise issue in Travel Rule compliance?

The sunrise issue describes the gap created when jurisdictions bring Travel Rule obligations into force on different dates and under different standards. A provider with live duties may face a counterparty that cannot legally send or receive the required data. Supervisors expect the compliant side to document its approach, including a risk assessment of the counterparty and the transfer.

Does the Travel Rule apply to self-hosted wallets?

Treatment varies by jurisdiction. Under Regulation (EU) 2023/1113, a CASP must collect and retain the required information for transfers involving a self-hosted address, and verify customer control of that address for transfers above €1,000. In the US, obligations depend on the intermediary's role in the transmittal rather than on the wallet type alone.

Do Travel Rule obligations replace KYC and AML checks?

No. Travel Rule requirements sit atop customer due diligence, sanctions screening, transaction monitoring, and suspicious activity reporting. The rule governs what information accompanies a transfer between institutions, and it does not discharge the duty to identify and risk-assess the customer.

Does ElenPAY provide Travel Rule compliance services?

No. ElenPAY provides Bitcoin Lightning payment infrastructure for licensed, regulated businesses and meets its own regulatory obligations, including the disclosures published under MiCA. Travel Rule, KYC, and AML compliance remain the responsibility of each platform under its own license or registration, with support from its compliance team and legal advisers.