Travel Rule compliance for stablecoin businesses 2026

The Travel Rule applies to your USDC business payments in every major jurisdiction, at different thresholds and with different data fields. A US outbound stablecoin transfer of 3,000 dollars or more triggers the FinCEN funds Travel Rule under 31 CFR 1010.410(f). The EU sets no de minimis under Regulation (EU) 2023/1113 for crypto-asset transfers between CASPs. The UK uses a 1,000 euro tier. Singapore uses a 1,500 SGD tier. Sending USDC without the right originator and beneficiary data attached is what gets the payment held or returned.

What is the Travel Rule and does it apply to my business?

The Travel Rule is a Financial Action Task Force standard, Recommendation 16, that requires financial institutions and virtual asset service providers to obtain, hold, and transmit originator and beneficiary information when they move value on behalf of a customer, per fatf-gafi.org/en/topics/virtual-assets.html. Regulators call it a "VASP-to-VASP" or "CASP-to-CASP" message: the sending institution passes structured KYC data alongside the on-chain transfer so the receiving institution can screen it.

In the United States, the rule sits inside the Bank Secrecy Act at 31 CFR 1010.410(f), the funds "Travel" regulation issued by FinCEN. FinCEN's own guidance at fincen.gov/resources/statutes-regulations/guidance/funds-travel-regulations-questions-answers says the rule applies to "transmittals of funds equal to or greater than $3,000 (or its foreign equivalent)." FinCEN has confirmed the rule reaches convertible virtual currency transmittals, and 2026 rulemaking extends Bank Secrecy Act obligations to permitted payment stablecoin issuers under the GENIUS Act, per fincen.gov/news/news-releases/agencies-invite-comment-proposed-rule-under-bank-secrecy-act.

In the European Union, Regulation (EU) 2023/1113 recasts the transfer of funds regulation and extends it to crypto-asset service providers, aligning the EU regime with FATF Recommendation 16, per the European Banking Authority at eba.europa.eu/publications-and-media/press-releases/eba-issues-travel-rule-guidance-tackle-money-laundering-and-terrorist-financing-transfers-funds-and. The EBA Travel Rule Guidelines apply from 30 December 2024. There is no de minimis for crypto-asset transfers under the EU regime, unlike traditional funds transfers.

In the United Kingdom, the Money Laundering and Terrorist Financing (Amendment) (No. 2) Regulations 2022 added a Part 7A to the 2017 MLRs and brought cryptoasset businesses inside the Travel Rule as of 1 September 2023, per fca.org.uk/news/statements/fca-sets-out-expectations-uk-cryptoasset-businesses-complying-travel-rule.

In Singapore, the Monetary Authority of Singapore imposes the rule on digital payment token service providers under MAS Notice PSN02, per mas.gov.sg/regulation/notices/psn02-aml-cft-notice---digital-payment-token-service. PSN02 sets a two-tier structure at 1,500 SGD.

If you are a business sending USDC to suppliers, contractors, or affiliates through a licensed VASP or CASP, the Travel Rule applies to your outbound payments the moment they cross the local threshold. If you self-custody a wallet and send peer-to-peer without a VASP in the middle, most regimes treat that as an "unhosted wallet" transfer with different, often heightened, due diligence requirements. This is general information, not legal advice.

Why do non-compliant outbound stablecoin payments get frozen?

Picture a US-formed exporter paying a 25,000 dollar USDC invoice to a supplier in Vietnam. The exporter's VASP is US-registered. The supplier receives at a Singapore-licensed DPT provider. The exporter clicks send with no structured message attached.

Two things happen. The originating VASP is required under 31 CFR 1010.410(f) to include the transmittor name, address, account number, transmittal amount, execution date, and the identity of the receiving institution in the transmittal order, per fincen.gov/resources/statutes-regulations/guidance/funds-travel-regulations-questions-answers. Without those fields, the VASP either blocks the outbound leg or files it and generates a compliance exception. Second, the receiving DPT provider in Singapore is required under PSN02 section 13 to obtain and hold originator and beneficiary information regardless of amount, and additional originator identifiers when the value exceeds 1,500 SGD, per mas.gov.sg/regulation/notices/psn02-aml-cft-notice---digital-payment-token-service. When the receiving institution finds the data missing or incomplete, PSN02 and the EBA Guidelines both require a risk-based decision to reject the transfer, return the funds, request the missing information, or suspend the beneficiary account.

The visible outcome is a stuck payment. The USDC lands on-chain, the beneficiary VASP quarantines the credit, the supplier calls you, and the invoice ages past due while both compliance teams reconcile a wire that already settled. In the worst case the beneficiary VASP freezes the account pending suspicious transaction reporting.

The other pattern is the return. The originating VASP refuses to send because your business account is missing the corporate KYC record that maps to the required Travel Rule fields. The stablecoin never leaves. You wire fiat instead and lose the settlement speed you built your treasury workflow around.

What does Plaitr do differently for Travel Rule outbound payments?

Plaitr runs a non-custodial account structure. Business funds sit at licensed US partner banks, mapped 1:1 to the legal entity that owns them, and stablecoin balances route through licensed VASP counterparties for the on- and off-ramp legs. That legal-entity mapping is what makes Travel Rule automation possible without asking your finance team to fill in KYC fields on every payment.

Plaitr does four things on outbound USDC:

• Attach the required Travel Rule fields to each outbound stablecoin transfer automatically. Transmittor name, transmittor address, transmittor account, transmittal amount, execution date, and receiving institution identifiers are pulled from the entity record on file and packaged into the VASP-to-VASP message before the on-chain send.
• Route through Travel Rule-compliant messaging rails, so the beneficiary VASP receives the structured payload before or with the transfer, matching the FATF Recommendation 16 "immediately and securely" standard at fatf-gafi.org/en/topics/virtual-assets.html.
• Block outbound sends over the local threshold when the counterparty VASP is unreachable on the messaging network, and surface a fallback path so the payment does not settle without a compliant handshake.
• Retain the Travel Rule records against the invoice and the on-chain hash, so year-end audit and any suspicious transaction reporting request maps to a single ledger entry rather than three disconnected systems.

Plaitr is not a bank. Plaitr operates under Wyoming governing law, with US banking delivered through licensed partner institutions and stablecoin rails on top. Cards are coming soon. Your business is responsible for the underlying customer relationships and any suspicious activity reporting obligations that attach to your own regulated status, if any.

What does a compliant USDC send look like in practice?

1. Onboard the business entity once. Provide the legal name, registered address, jurisdiction of formation, ownership, and government identifiers. Plaitr binds those records to the entity that owns the stablecoin balance.
2. Add the beneficiary. The counterparty is either a hosted VASP account, in which case you provide the beneficiary name, account or wallet reference, and the receiving VASP identifier, or a self-hosted wallet, in which case additional due diligence attaches under the EU and UK regimes.
3. Enter the invoice. Amount, currency, and reference. Plaitr computes whether the send crosses the applicable Travel Rule threshold in the paying jurisdiction and any receiving jurisdiction.
4. Confirm the send. Plaitr assembles the Travel Rule message with transmittor and beneficiary fields drawn from the entity records and dispatches it to the receiving VASP through the Travel Rule messaging network before broadcasting the on-chain transfer.
5. Receive the acknowledgment. The beneficiary VASP either accepts the payload and confirms it is ready to receive, or returns a rejection with the missing fields called out. Plaitr surfaces the rejection to the sender before any USDC leaves the account.
6. Settle on-chain. Plaitr broadcasts the USDC transfer once the Travel Rule handshake completes. The on-chain hash, the Travel Rule payload, and the invoice all link to the same ledger entry.
7. Reconcile automatically. The transaction posts to the general ledger with the Travel Rule metadata attached, ready for audit, tax, and any regulator request.

Here is how the four jurisdictions compare:

| Jurisdiction | Rule and citation | Threshold for stablecoin transfers | Required originator fields | Required beneficiary fields | | --- | --- | --- | --- | --- | | United States | 31 CFR 1010.410(f), funds "Travel" rule, per fincen.gov | 3,000 USD or foreign equivalent | Name, address, account number, transmittal amount, execution date, identity of transmittor's financial institution | Name, address, account number, identity of receiving financial institution, other specific identifiers if received | | European Union | Regulation (EU) 2023/1113 and EBA Travel Rule Guidelines from 30 December 2024, per eba.europa.eu | No de minimis for crypto-asset transfers between CASPs | Name, distributed ledger address or account number, address, official personal document number, customer identification number, or date and place of birth | Name, distributed ledger address or account number, and account number where used | | United Kingdom | Money Laundering, Terrorist Financing and Transfer of Funds Regulations 2017, Part 7A, in force 1 September 2023, per fca.org.uk | 1,000 EUR equivalent for full data set; reduced data set below | Full: name, account number or wallet reference, and one of address, ID number, or date and place of birth. Reduced below 1,000 EUR: name and account or wallet reference | Name and account number or wallet reference | | Singapore | MAS Notice PSN02, sections 13.4 and 13.6, per mas.gov.sg | Baseline data required for any amount; expanded data required above 1,500 SGD | Baseline: name and account or transaction reference. Above 1,500 SGD: additional identifier, either address, national ID number, or date and place of birth | Name and account or transaction reference |

Every entry above comes from the primary regulatory source cited in the sources block. Do not treat this as a substitute for a jurisdiction-specific compliance review by counsel.

FAQ

Does the Travel Rule apply to on-chain transfers under 3,000 dollars from a US business?

The FinCEN funds Travel Rule under 31 CFR 1010.410(f) applies to transmittals equal to or greater than 3,000 dollars, per fincen.gov. Transfers under 3,000 dollars are outside the Travel Rule recordkeeping and transmittal requirement in the US, but they remain inside Bank Secrecy Act obligations for VASPs, including customer identification, transaction monitoring, and suspicious activity reporting. Your VASP may still collect Travel Rule fields on smaller sends as a matter of policy.

Is there any threshold under the EU crypto Travel Rule?

The EU Regulation (EU) 2023/1113, as reflected in the EBA Travel Rule Guidelines applying from 30 December 2024, requires originator and beneficiary information to accompany crypto-asset transfers between CASPs regardless of value, per eba.europa.eu. The de minimis that historically applied to fiat funds transfers does not apply to crypto-asset transfers. Every CASP-to-CASP send must carry the required data.

What about self-hosted wallet transfers?

The FATF standard at fatf-gafi.org/en/topics/virtual-assets.html asks jurisdictions to apply risk-based measures to transfers involving unhosted wallets. The EU rules under Regulation 2023/1113 require CASPs to collect originator or beneficiary information for transfers involving self-hosted wallets above a set threshold and to verify the counterparty in some cases. The UK and Singapore apply similar risk-based expectations. Requirements differ by jurisdiction and by whether the send is inbound or outbound; check with your VASP before moving stablecoins to or from a self-hosted address.

Is Plaitr a VASP?

Plaitr is a non-custodial fintech. Business funds sit at licensed partner banks, and stablecoin custody and settlement route through licensed VASP counterparties. Plaitr provides the account structure, the Travel Rule field assembly, and the reconciliation layer. The VASP-to-VASP messaging obligation is discharged by the licensed counterparty that executes the on-chain leg. Plaitr is not a bank and cards are coming soon.

Does non-custodial mean the Travel Rule does not apply?

No. The Travel Rule attaches to the VASP or CASP that executes the transfer, not to the software vendor. When your business sends USDC through a Plaitr-facilitated flow, the licensed VASP counterparty is the regulated actor for Travel Rule purposes, and the required fields still travel with the payment. A truly peer-to-peer transfer with no VASP in the loop is a different case handled under the self-hosted wallet framework in each jurisdiction.

Do stablecoin issuers themselves have Travel Rule duties?

In the United States, the 2026 joint FinCEN and OFAC proposed rulemaking treats permitted payment stablecoin issuers as financial institutions under the Bank Secrecy Act pursuant to the GENIUS Act, extending anti-money laundering program requirements to issuers, per fincen.gov/news/news-releases/agencies-invite-comment-proposed-rule-under-bank-secrecy-act. This is a proposed rule at the time of writing. In the EU, issuers of asset-referenced tokens and e-money tokens sit inside the MiCA framework, per eba.europa.eu. Confirm current status with counsel before relying on either regime.

What happens when the receiving VASP is in a jurisdiction that has not implemented the Travel Rule?

The FATF 2025 targeted update at fatf-gafi.org/en/topics/virtual-assets.html notes that 73 percent of surveyed jurisdictions have passed Travel Rule legislation. Sending VASPs are expected to apply a risk-based approach when the receiving jurisdiction lacks a compliant regime, which can include enhanced due diligence, additional counterparty verification, or refusing the transfer. Your VASP will typically surface this as a hold or a request for more information before the send.

Can Plaitr freeze a payment?

Plaitr will surface a rejection from the counterparty VASP before broadcasting the on-chain transfer. If the Travel Rule handshake fails because required fields are missing or the counterparty is not reachable on the messaging network, the USDC does not leave the account. The funds sit at the partner bank or in the entity-mapped stablecoin balance until the exception is cleared.

Map your outbound stablecoin flows against the four thresholds in the table above. Where the send crosses the local threshold, confirm your VASP collects and transmits the required fields automatically rather than asking finance to fill them in per payment. Where the beneficiary sits in a self-hosted wallet, confirm the enhanced due diligence path in the relevant jurisdiction before sending. See how Plaitr assembles Travel Rule fields, routes VASP-to-VASP messaging, and reconciles the on-chain hash to the invoice at demo.plaitr.com.

This is general information, not legal advice.