The travel rule makes off-ramps pass sender and receiver data with transfers. Thresholds by country, required data, and what happens when checks fail.
The travel rule requires a provider that moves virtual assets to collect information about the sender and the receiver and pass it along with the transfer, the same way banks do for wires. For a stablecoin off-ramp, it means the provider knows who sent the stablecoin, who gets the fiat, and can prove both to a regulator. The threshold depends on the country: USD or EUR 1,000 under FATF guidance, USD 3,000 in the US, and no minimum at all in the EU.
It's the least visible compliance check in an off-ramp. It's also the one people ask about least until a payout stalls.
FATF's Recommendation 16 has applied to wires for decades. In 2019 FATF extended it to virtual asset service providers, the category covered in what is a VASP. The provider sending a transfer must obtain and pass on:
| Data | Below threshold | At or above threshold |
|---|---|---|
| Originator name | Yes | Yes |
| Originator account or wallet address | Yes | Yes |
| Originator address, national ID number, customer ID, or date and place of birth | No | Yes |
| Beneficiary name | Yes | Yes |
| Beneficiary account or wallet address | Yes | Yes |
The receiving provider must collect the same data, check it, and keep it. Below the threshold the data doesn't have to be verified unless something looks suspicious. At or above it, it does.
Providers exchange this data through messaging networks built for it, mostly on a common data model called IVMS 101. The details of which network matter less than the fact that one exists: travel rule data moves beside the transfer, not inside it. The blockchain transaction itself carries none of it.
| Jurisdiction | Threshold | Notes |
|---|---|---|
| FATF recommendation | USD or EUR 1,000 | Countries set their own threshold |
| European Union | None | Transfer of Funds Regulation, since December 30, 2024 |
| United States | USD 3,000 | Bank Secrecy Act recordkeeping and travel rule |
| Singapore | SGD 1,500 | |
| United Kingdom | All transfers | Reduced data set below EUR 1,000 |
Thresholds move. Treat this table as a snapshot and check the stablecoin regulation tracker for the wider rules in each market, including MiCA in the EU and the PSAV regime in Brazil.
An off-ramp sits between two regimes: crypto on one side, banking on the other. The rule touches each leg differently.
The practical upshot: the off-ramp has to know the sender and the receiver well before the payout executes. That's why onboarding comes first.
They answer different questions and run at different moments.
| Check | What it answers | When it runs |
|---|---|---|
| KYC | Is this person who they say they are? | Onboarding, then refreshed |
| KYB | Is this business real, and who owns and controls it? | Onboarding, then refreshed |
| Sanctions screening | Is anyone involved on a sanctions list, or in a prohibited country? | Onboarding and on every transaction |
| Transaction monitoring | Does this payment fit the customer's normal pattern? | Continuously |
| Travel rule | Does the originator and beneficiary data move with the transfer? | On every transfer that crosses the threshold |
KYC and KYB establish identity once. Screening and monitoring watch every payment. The travel rule makes sure identity data follows the money between providers. Real-time transaction monitoring and compliance agents for cross-border payments cover the ongoing side.
It depends on which check and how badly. On BlindPay:
compliance_request, and only one request is open at a time.on_hold. A hold can last up to 30 days. Approval resumes the normal flow, and a timeout without a decision fails the payout.Each outcome has its own status, covered in stablecoin payout statuses explained. Most holds clear with a document, so fast responses matter more than anything else. Large payouts are also shaped by off-ramp limits, which bound what a customer can move before a hold is even in question.
Usually not, if it's selling its own goods or services and uses a licensed provider to convert. Exchanging stablecoins for fiat on behalf of other people is the regulated activity, and that's what the off-ramp does. Do merchants need a license to accept stablecoins goes through where that line sits.
BlindPay runs KYC, KYB, sanctions screening, and travel rule compliance inside the API flow. Every customer is verified before their first transaction: KYC Standard in about 60 seconds for eligible individuals, and manual review for KYC Enhanced and KYB. Checks run before money moves, so a problem shows up as a blocked request or a held payout with a status and a webhook, not a transfer that disappears for a week. The customer requirements are in the KYC reference and the hold process in on-hold transactions.
Before you integrate, map which of your flows cross which threshold, and collect full sender and receiver details from day one. Data you collect at onboarding is data nobody has to chase during a hold.
This article is for general information only and is not legal advice.
Stablecoin transfers settle final in minutes and cannot be reversed. That finality proves custody at every step, but it also opens a fraud gap on the fiat side of the payment.
A side-by-side comparison of automated and manual KYC/KYB for fintechs: onboarding time, false-positive rates, cost per verification, scaling across jurisdictions, and audit-trail quality, plus the cases where a human reviewer is still required.
How compliance agents apply FinCEN, MiCA, FCA, MAS, and Banco Central do Brasil rules to cross-border stablecoin payments: jurisdiction table, the FATF Travel Rule, multi-list sanctions screening, the four components of a compliant program, and questions to ask a compliance provider.