Skip to main content

What is the Travel Rule?

The Travel Rule refers to a set of global anti-money-laundering and counter-terrorist-financing regulations, including the U.S. Bank Secrecy Act and the EU Transfer of Funds Regulation, that Bridge is legally obligated to comply with as a regulated financial institution. These regulations require Bridge to identify the parties to covered transfers and transmit specified information to the next regulated institution in the payment chain. A virtual asset service provider is commonly known as a VASP. In the European Economic Area (EEA), the equivalent term is crypto-asset service provider, or CASP. Every Travel Rule record has two parties:
  • Originator: The person or business that actually sends the funds.
  • Beneficiary: The person or business that ultimately receives the funds.
Travel Rule data must identify the actual sender and recipient of the funds. Bridge processes the transaction, but Bridge is not the originator or beneficiary: that role belongs to the developer’s end customer or the third party on the other end of the transfer, even when the funds move through a Bridge-custodied wallet. For each movement, your implementation must:
  1. Decide whether the movement is covered.
  2. Identify the actual originator and beneficiary.
  3. Collect and verify the required information.
  4. Submit the information to Bridge.

Regulatory background

United States

The US Funds Travel Rule is codified in 31 CFR 1010.410(f). It requires a US transmittor’s financial institution or intermediary financial institution to include specified information in a transmittal order of 3,000 USD or more, or its foreign-currency equivalent. The information includes the transmittor’s name, account number when applicable, address, transaction amount, execution date, recipient financial institution, available recipient information, and identifying information for the transmittor’s financial institution. In common crypto terminology, the transmittor is the originator and the recipient is the beneficiary. FinCEN applies these requirements to qualifying convertible virtual currency transfers. See FinCEN guidance FIN-2019-G001.

European Union

Regulation (EU) 2023/1113 applies to covered crypto-asset transfers involving a CASP from December 30, 2024. It requires originator and beneficiary information to accompany covered transfers and has no general minimum transaction threshold. Required information includes names, relevant distributed-ledger addresses or crypto-asset account numbers, prescribed originator identification information, and an LEI or equivalent official identifier when applicable and available in the message format. For a transfer exceeding 1,000 EUR to or from a self-hosted address, the CASP must take adequate measures to assess whether its customer owns or controls the address. This is an ownership-or-control check, not a general exemption for transfers of 1,000 EUR or less. The European Banking Authority Travel Rule Guidelines explain how providers should detect missing or incomplete information, request missing information, assess risk, reject or return transfers, and address repeated failures by another provider.

Scope and applicability

Key terms

Determine applicability

The Travel Rule applies to transactions where funds are sent on-chain to or from a wallet outside of Bridge’s ecosystem. It does not apply to funds flows that stay within Bridge custody or fiat flows with no on-chain leg outside of Bridge. As a general rule, if the transaction involves moving crypto on-chain outside of Bridge’s custody, the Travel Rule applies. Crypto Travel Rule requirements depend on jurisdiction. Note that even if you are not yourself a regulated entity, Bridge is a regulated EU entity and US MSB and is required to collect originator and beneficiary information for qualifying transactions. This means you will need to pass this data to Bridge as a condition of processing these flows.

US applicability

Transfers of 3,000 USD or more fall under US jurisdiction when meeting any of the following criteria:
  • Your institution operates as a US-regulated VASP or MSB, governing all qualifying movements regardless of user jurisdiction or asset type.
  • The transfer involves USD or USDC, irrespective of where the customer resides.
  • The end customer resides within the US, regardless of the asset used.

EEA applicability

Transfers fall within European Economic Area scope and trigger Travel Rule compliance obligations without any minimum monetary threshold if they satisfy any of these conditions:
  • Bridge or your organization functions as an EEA-licensed CASP, governing all transfers independent of customer residency or token type.
  • The payment structure incorporates EUR or EURC components (such as virtual IBAN funding, fiat disbursements, or asset swaps), regardless of user location.
  • The end customer is EEA-based, irrespective of the underlying currency.
For corporate entities, jurisdiction within the EEA relies upon the company’s official registered location rather than the personal residences of key ultimate beneficial owners or affiliated individuals. Hence for Travel Rule purposes, developers must provide the legal registered address. The 1,000 EUR threshold strictly governs self-hosted address verification when EUR or EURC assets are transferred. All EEA-scoped transfers obligate full Travel Rule data collection without a minimum limit.

When the Travel Rule does not apply

If funds never leave Bridge’s custody and no on-chain transfer is made to an external VASP or self-hosted wallet, there is no Travel Rule obligation. For example:
  • Fiat into a Bridge custodial wallet (onramp only, no outbound disbursement): No Travel Rule data required
  • Bridge wallet to Bridge wallet (internal transfer): No Travel Rule data required
  • Bridge wallet to fiat bank account (no on-chain leg): No Travel Rule data required

Determine what you need to supply

  • Inbound crypto from a self-custodied wallet, or another source not transmitting information to Bridge - Developer should collect the applicable originator information.
  • Outbound crypto/onramp to a destination wallet - Developer should collect the beneficiary information Bridge needs before payout.
  • For crypto sent by another CASP, the sending provider is expected to transmit originator information to Bridge, so you generally do not need to submit that sender information yourself. Submit the beneficiary information as well to ensure Bridge has what it needs. Treat sender and beneficiary information as separate responsibilities, not a blanket exemption.
You may attach travel_rule_data even when it is not strictly required for a particular movement. Always represent the actual parties accurately.

Identify the originator and beneficiary

For each movement, identify the actual originator and ultimate beneficiary, the Bridge Customer resource associated with the route, and any sending/receiving institution. The developer making an API request is not automatically the originator.

Originator

The originator is whoever is actually sending the funds. This may be your customer or a third party. The key distinction is whether the transfer is self-to-self or involves an identifiable third party:
  • Self-to-self transfer (your customer sends to themselves): Set originator.is_self: true. Bridge will automatically pull the originator’s information from the customer’s profile.
  • Identifiable third-party originator (a third party sends funds and their identity is known or obtainable): The third party is the originator. Where you are able to identify them (for example, on outbound transactions you initiate or inbound transfers where your customer knows the sender), you are expected to collect and submit their name and address. Bridge will work through its own resolution process internally and will reach out to you directly if additional information is needed.
  • Unidentifiable originator (funds arrive from an unknown source, e.g., open liquidation addresses): This is a distinct scenario with its own obligations and resolution framework. See Unknown originators.
A documented, good-faith effort to collect originator data wherever possible is required. Where an originator cannot be identified, the obligation does not disappear. is_self: true means the person sending the funds is your customer sending to themselves. It is not a substitute for collecting third-party originator data when that data is obtainable.

Beneficiary

The beneficiary represents the final account owner rather than Bridge. When this account holder matches your end customer, designate is_self: true. Otherwise, supply the full identity information of the external recipient. Apply is_self separately to each party. Set originator.is_self: true when the originator is the person or business represented by the associated Bridge Customer resource. Set beneficiary.is_self: true when the beneficiary matches that resource. One flag can be true while the other is false. Both flags are true only when both parties match that Customer resource.

Identify the parties in your flow

The following examples illustrate common flows:
  • Crypto payout to a third party Originator: Your customer (who initiated the transfer). Set is_self: true on the originator and Bridge will pull their info from the customer profile. Beneficiary: The third-party recipient (name, address, and legal_entity_identifier if a business). Wallet ownership attestation is not required from that third-party recipient.
  • Third-party Virtual Account onramp Originator: the third-party sender, such as a friend, whose information is collected from the end customer. Beneficiary: the receiving end customer; use is_self: true.
  • Third-party funding of a Virtual Account or Liquidation Address The third party is the originator. If their identity is known or obtainable, collect and submit it. Wallet ownership attestation is not required for that noncustomer third party.
  • Offramp to an external bank account The beneficiary is the ultimate bank-account holder, not Bridge. If the bank account holder is the same person as your customer, use is_self: true; If it is a different person, provide the bank account holder’s details as the beneficiary.
For treasury flows, confirm the actual legal parties and associated Customer resource with Bridge before choosing self flags. Treasury activity can use reusable party information when the same parties apply to future movements; the label “treasury” alone does not determine either party’s identity.

Additional money movement flows

Unknown originators

Where the ultimate originator is genuinely unknown, make and document reasonable good-faith collection efforts, submit what can be obtained through the supported process and tell Bridge if the product structurally accepts unknown third parties.
  • Submit what you have. Make a documented good-faith effort to obtain the actual sender’s information. Provide available partial information and do not invent information that you do not have.
  • Document the product model. Tell Bridge if the product intentionally accepts inbound transfers from unknown third parties, so the model and partner/downstream AML responsibilities are understood.
  • Follow risk-based handling. Bridge handles unresolvable originators above EUR 1,000, and other missing required Travel Rule information, on a risk basis. Bridge will contact you if further action is needed.
  • Do not fill unknown fields with another person’s details or use is_self to conceal an unknown sender. If API validation prevents a genuine partial submission, seek Bridge guidance instead of fabricating missing values.

Wallet custody, ownership and attestation

Classify wallet custody

Once you have identified the originator and beneficiary information, classify the custody arrangement of the wallet. For inbound flows, classify the depositing (originator) wallet; for outbound flows, classify the receiving (beneficiary) wallet where applicable. For a fiat source or destination, omit wallet_type and wallet_attested_ownership_at. For a fiat offramp with beneficiary is_self: true, no other beneficiary fields are required. For a third-party beneficiary, provide name and address.

Determine whether ownership attestation is required

Attestation is required when:
  • The sending wallet is self-hosted (self_custodied or hosted) AND
  • The transaction is through Bridge’s EU entity (EUR transaction) AND
  • The transaction exceeds €1,000 in a single transaction or in several transactions which appear to be linked.
For US flows, wallet attestation is not required when sending to or receiving from a self-hosted wallet. Similarly, attestation is not required for:
  • Bridge-custodied wallets
  • Third-party originators or beneficiaries (non-customers); collect their name and address, but no wallet attestation
  • Fiat-only flows

Ownership attestation methods

Use an appropriate ownership-verification method, such as a signature challenge, micro-deposit/satoshi test or third-party verification tool. A signature challenge is not the only method. Attestations are subject to sample-based quality checks; never add a timestamp for a check that has not occurred.

Share Travel Rule data

What originator fields are required depends on whether the originator is your customer (self-to-self) or a third party.

Reusable resources versus one-off records

Bridge supports two ways of sharing Travel Rule data. Reusable product/resource submissions and one-off transactions use the same travel_rule_data payload. Use this endpoint to submit originator and beneficiary information for Travel Rule compliance. In the request URL below, resource_id refers to either the product resource ID or the one-off resource ID. The following sections demonstrate reusable Virtual Account and one-time Transfer examples.
Before submitting travel_rule_data, the developer should identify whether each originator or beneficiary is a Bridge customer. Bridge uses the verified customer record if is_self = true, if is_self = false, the developer supplies the counterparty’s required identifying information. The API also requires a wallet classification to be provided for the relevant party:
  • self_custodied: Customer-owned wallet
  • hosted: Developer-owned or hosted wallet
  • external: Exchange-owned wallet or smart contract
API reference: Submit Travel Rule data

Example: Reusable Virtual Account

The end customer regularly funds their dedicated Virtual Account from their own bank account. Each USD payment is converted to USDC and sent to the end customer’s receiving address on Base. The end customer is both the originator and beneficiary. Create a Virtual Account with reusable Travel Rule information for this fixed self-to-self relationship.
API reference: Create a Virtual Account

Example: One-time Transfer

In this example, the end customer makes a one-time payment to a third-party recipient whose receiving account is held at another exchange/CASP. POST /v0/transfers creates the individual movement.
API reference: Create a Transfer

What data you need to share

The information you submit depends on whether each party matches the person or business identified by the Customer ID used for that transaction. Provide wallet information separately from the originator’s and beneficiary’s identity information.

Travel Rule compliance expectations and enforcement

Bridge enforcement

Missing Travel Rule information alone does not cause an immediate hold or freeze at transaction time. Bridge will reach out to address noncompliance. If Travel Rule data remains missing after outreach, Bridge may apply enhanced controls at the customer level and may reject future transfers. Do not treat this process as a guarantee that every transfer executes, that unrelated controls never apply or that all compliance obligations are satisfied. Follow Bridge’s case-specific instructions and deadlines; do not assume a fixed remediation grace period.