본문으로 건너뛰기

What is the crypto Travel Rule?

The crypto Travel Rule is a regulatory requirement for crypto-asset service providers to collect, verify where required, transmit and retain information about the originator and beneficiary of a crypto transfer. In the European Union, Regulation (EU) 2023/1113 applies to covered crypto transfers from 30 December 2024. It can require Quppy’s applicable provider to ask who is sending or receiving crypto, which provider or self-hosted address is involved, and in some cases for evidence of wallet ownership or control.

최종 확인: 2026-08-21

Article facts

FieldVisible value
PurposeTraceability of covered crypto transfers and prevention of financial crime
EU legal frameworkRegulation (EU) 2023/1113 and applicable EBA guidance
EU application date30 December 2024
Information concernsOriginator, beneficiary, transfer, provider and sometimes self-hosted address
Self-hosted address checksCan include ownership/control verification; specific EU rule applies over €1,000 in relevant cases
Does it make a transfer risk-free?No
Last reviewed2026-08-21

Why is it called the Travel Rule?

The name reflects the principle that identifying information should “travel” with a covered transfer between regulated service providers. The goal is to help providers and authorities trace transfers and identify missing, false or suspicious information.

The requirement is not unique to Quppy. It is based on international AML/CFT standards and implemented through regional and national rules.

Which transfers can be affected?

The Travel Rule can affect crypto transfers:

  • from Quppy to another crypto exchange or custodial wallet;
  • from another provider to Quppy;
  • between a regulated provider and a self-hosted wallet;
  • involving a person other than the Quppy user;
  • involving providers in different countries.

The exact obligations depend on the jurisdictions, provider roles and transfer structure. A transfer to or from a self-hosted address is not automatically exempt.

What information can be requested?

Information can include:

About the originator

  • full name;
  • account or wallet-related identifier;
  • address, identity-document number, customer-identification number, or date and place of birth where required;
  • legal-entity identifier where applicable.

About the beneficiary

  • full name;
  • account or wallet-related identifier;
  • provider or wallet type;
  • legal-entity information where applicable.

About the transfer

  • crypto-asset;
  • amount;
  • blockchain network;
  • wallet addresses;
  • transaction hash;
  • sending and receiving providers;
  • purpose or relationship where required.

The exact fields shown in Quppy can differ by country and provider.

What is a self-hosted address?

A self-hosted address is a crypto address not administered by a crypto-asset service provider on behalf of the user. It is sometimes called a personal, unhosted or non-custodial wallet address.

Quppy Crypto itself uses a custodial model. However, users can send to or receive from compatible external wallets, including self-hosted wallets where supported.

Why can I be asked to prove ownership or control of a wallet?

For covered transfers handled under the applicable EEA service configuration and involving a self-hosted address, the provider can need to identify the relevant person and assess whether the address is owned or controlled by the stated originator or beneficiary.

Under Regulation (EU) 2023/1113, specific verification obligations apply in relevant cases for transfers exceeding EUR 1,000 to or from a self-hosted address.

An approved verification method might involve:

  • a signed message where technically supported;
  • a small verification transfer;
  • evidence from the wallet interface;
  • a provider-approved ownership declaration;
  • transaction history or other risk-based evidence.

The actual method must be the one shown by Quppy or the provider. Never disclose a private key or seed phrase.

What happens if information is missing?

The provider can:

  • request missing or corrected data;
  • pause the transfer;
  • reject or return the transfer where possible;
  • restrict transfers to or from a provider that repeatedly omits required information;
  • conduct enhanced review;
  • report suspicious activity where legally required.

A blockchain transaction can be technically irreversible even when the provider cannot credit it. This is why required information should be completed before sending whenever the flow requests it.

Who receives Travel Rule information?

Depending on the transfer, information can be shared with:

  • the sending or receiving crypto-asset service provider;
  • technology vendors used to transmit Travel Rule data;
  • compliance and screening providers;
  • regulators, financial intelligence units, courts or law-enforcement authorities where legally required;
  • other recipients described in the applicable Privacy Notice.

Travel Rule data should not be entered into public blockchain fields unless the approved process specifically requires a non-sensitive reference.

How long can the information be retained?

Retention depends on the applicable law and provider. Payhound’s current Privacy Notice states that Travel Rule data is generally retained for five years, with longer retention possible where authorised or required by an authority, legislation, legal proceedings or justified legitimate interests.

The retention period that applies to a particular Quppy user depends on the provider and Privacy Notice assigned to that service.

How should I complete a Travel Rule request?

  1. Select whether the destination is an exchange/custodial provider or a self-hosted wallet.
  2. Enter the beneficiary’s accurate legal name.
  3. Identify the external provider when requested.
  4. State whether the wallet belongs to you or another person.
  5. Provide the requested relationship or purpose information.
  6. Complete any approved wallet-ownership check.
  7. Verify the asset, network and address before confirming.

Do not choose “my wallet” merely to avoid providing beneficiary information. False information can cause rejection, restriction or further review.

Does the Travel Rule guarantee that a transfer is safe?

No. Travel Rule data supports traceability and compliance. It does not guarantee that:

  • the recipient is trustworthy;
  • the address is free of risk;
  • the transfer can be reversed;
  • the crypto-asset will retain value;
  • the external provider will credit the transfer.

Always verify the recipient and transaction details independently.

FAQ

Does the Travel Rule apply only to large transfers?

No. Information requirements can apply to covered transfers regardless of amount. Additional self-hosted-address verification requirements can apply in relevant EU/EEA service cases over EUR 1,000.

Does it apply to self-hosted wallets?

Yes, covered transfers to or from self-hosted addresses can require information and risk-based ownership or control checks.

Do I need to share my seed phrase?

No. Never share a seed phrase or private key.

Why do I need the recipient’s name?

The applicable provider can be required to associate the transfer with originator and beneficiary information.

Can my transfer be rejected if the other provider does not supply information?

Yes. Missing or invalid required information can lead to delay, rejection, return or enhanced review.

Is Travel Rule information stored on the blockchain?

The regulated data exchange normally occurs between providers or through approved systems, not as public personal data on the blockchain.

Does the Travel Rule apply outside the EEA?

Many jurisdictions implement FATF-based Travel Rule requirements, but the details differ.

When did the EU rule apply?

Regulation (EU) 2023/1113 applies from 30 December 2024.

Explanatory note

This article explains the current Quppy product and compliance configuration. The applicable Quppy and service-provider terms, country eligibility rules, privacy notices and information shown in the app prevail if they differ from this article.

Verification and compliance

Why do I need to provide information about an external wallet?

Quppy or the applicable crypto-service provider may ask for information about an external wallet to identify the sender or beneficiary, determine whether the address is self-hosted or managed by another provider, comply with the Travel Rule, assess sanctions and AML/CFT risk, and confirm that the asset and network are supported. The request can apply to deposits and withdrawals and never requires you to disclose a private key or seed phrase.

Crypto wallet and transfers

How do I send crypto to an external wallet?

Eligible users can send supported crypto-assets from Quppy to compatible external wallet addresses. Select the asset and network available to your account, enter or scan the destination address, review the amount and transaction details, and complete the required confirmation steps. Blockchain transactions normally cannot be reversed.

Crypto wallet and transfers

How do I receive crypto from an external wallet?

Eligible users can receive supported crypto-assets from compatible external wallets and crypto platforms. Before sending, select the asset and currently supported network in Quppy, copy the deposit details and use the same asset and network on the external platform. Do not use an old address or unsupported network.

Verification and compliance

Why can a Quppy transaction be delayed or rejected?

A Quppy transaction can be delayed, placed under review, returned or rejected because of payment-route rules, blockchain confirmations, incorrect details, security controls, transaction limits, provider availability, sanctions or AML/CFT checks, Travel Rule information, source-of-funds questions, or a technical incident. A pending or rejected status does not identify one specific cause, and Quppy may be legally unable to disclose every internal risk indicator.