---
title: "What is the travel rule for stablecoin off-ramps? Thresholds, data, and failed checks"
seoTitle: "The travel rule for stablecoin off-ramps, explained"
description: "The travel rule makes off-ramps pass sender and receiver data with transfers. Thresholds by country, required data, and what happens when checks fail."
date: "2026-09-24"
updated: "2026-09-24"
category: "compliance"
author: "BlindPay Team"
faq:
  - q: "What is the travel rule in crypto?"
    a: "It's the requirement that virtual asset service providers obtain, keep, and pass along information about the sender and the receiver of a transfer, the same way banks do for wires. FATF extended its Recommendation 16 to virtual assets in 2019, and countries implement it through their own AML rules."
  - q: "At what amount does the travel rule apply to stablecoin transfers?"
    a: "It depends on the country. FATF recommends a threshold of USD or EUR 1,000. The EU applies the rule with no minimum since December 30, 2024. The US applies it at USD 3,000 under the Bank Secrecy Act. Singapore uses SGD 1,500, and the UK applies it to all transfers with a reduced data set below EUR 1,000."
  - q: "Does the travel rule apply when I off-ramp from my own wallet?"
    a: "Differently. A self-hosted wallet has no provider on the other side to exchange data with, so the off-ramp collects and keeps the information about its own customer instead. In the EU, for transfers above EUR 1,000 involving a self-hosted wallet, the provider must also verify that the wallet is owned or controlled by its customer."
  - q: "Is off-ramping crypto legal?"
    a: "Yes, in most countries, when it runs through a licensed or registered provider. In the US that means a money services business with state money transmitter licenses, in the EU a crypto-asset service provider under MiCA, and in Brazil an authorized virtual asset provider under the Central Bank's PSAV rules. The travel rule is one of the obligations that comes with those licenses."
  - q: "What happens if my off-ramp transaction fails compliance checks?"
    a: "It stops before or during the payout, depending on the check. A customer or bank account in a prohibited country is blocked outright. A possible sanctions match, or missing or unclear information, usually leads to a hold and a request for information. On BlindPay a hold can last up to 30 days; approval resumes the payout, and a timeout or rejection fails it. A refunded payout returns the stablecoins to the wallet that funded it, while a failed payout doesn't refund automatically and needs support."
---

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.

## What does the travel rule require?

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](/resources/more/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.

## What are the travel rule thresholds by country?

| 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](/resources/more/stablecoin-regulation-tracker-2026) for the wider rules in each market, including [MiCA](/resources/more/mica-stablecoin-rules-explained) in the EU and the [PSAV regime](/resources/more/psav-brazil-explained) in Brazil.

## Where does the travel rule show up in an off-ramp?

An off-ramp sits between two regimes: crypto on one side, banking on the other. The rule touches each leg differently.

1. **Stablecoin arrives from an exchange or another provider.** That provider is a VASP, so it sends travel rule data about the sender. The off-ramp receives it, checks it against its own records, and keeps it.
2. **Stablecoin arrives from a self-hosted wallet.** There's no provider on the other side, so no travel rule message. The off-ramp relies on its own customer's KYC and records who controls the wallet. In the EU, above EUR 1,000, it has to verify that its customer owns or controls that wallet.
3. **Fiat goes out to a bank account.** The bank transfer carries its own payment data under the banking rules for that rail. On a wire, the originator and beneficiary details travel in the payment message, which is where the original travel rule came from.

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.

## How is the travel rule different from KYC, KYB, and sanctions screening?

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](/resources/more/real-time-transaction-monitoring-stablecoin-payments) and [compliance agents for cross-border payments](/resources/more/compliance-agents-cross-border-stablecoin-payments) cover the ongoing side.

## What happens when a compliance check fails?

It depends on which check and how badly. On BlindPay:

- **Prohibited country.** Customer or bank account creation fails outright. There's no override and no manual exception.
- **Missing or unclear information.** Compliance opens a request for information on the customer. The customer moves to `compliance_request`, and only one request is open at a time.
- **Held payout.** A payout that needs a closer look, including a possible sanctions or watchlist match, moves to `on_hold`. A hold can last up to 30 days. Approval resumes the normal flow, and a timeout without a decision fails the payout.
- **Refunded.** The stablecoins go back to the wallet that funded the payout, instead of being converted to fiat. Stablecoin refunds process right away.
- **Failed.** The payout didn't complete. A failed payout doesn't refund automatically; contact support.

Each outcome has its own status, covered in [stablecoin payout statuses explained](/resources/more/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](/resources/more/stablecoin-off-ramp-limits), which bound what a customer can move before a hold is even in question.

## Does a small business need a license to accept stablecoin payments?

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](/resources/more/do-merchants-need-a-license-to-accept-stablecoins) goes through where that line sits.

## How does BlindPay handle the travel rule?

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](/docs/kb/kyc) and the hold process in [on-hold transactions](/docs/kb/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.*