Travel Rule requirements

Explore Travel Rule requirements by jurisdiction.

On this page, you can find the information on Travel Rule requirements applied in different jurisdictions.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

The resolution establishes that the obligated subjects must comply with the identification of the originator and the beneficiary of the transactions covered by the Travel Rule, in the terms established by the International Standards of the FATF and in the modality that the FIU establishes for the exchange and validation of said information. Information will be updated when FIU publishes clarifications.

Data to be shared

Subject

Details

Threshold-based data

The resolution establishes that the obligated subjects must comply with the identification of the originator and the beneficiary of the transactions covered by the Travel Rule, in the terms established by the International Standards of the FATF and in the modality that the FIU establishes for the exchange and validation of said information. Information will be updated when FIU publishes clarifications.

Domestic vs cross-border transfers

Batch file transfer

Unhosted wallet verification

VASP Due Diligence

Time and way to share the Information

Record retention

10 years.

The resolution establishes that the obligated subjects must comply with the identification of the originator and the beneficiary of the transactions covered by the Travel Rule, in the terms established by the International Standards of the FATF and in the modality that the FIU establishes for the exchange and validation of said information. Information will be updated when FIU publishes clarifications.

Subject

Details

Status

Not in force. Shall come into force on March 31, 2026.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Individual Person


Originator:

  • a) Full official name;
  • b) Tracing information in relation to the transfer of value which means information that satisfies the following:
    • (i) for a transfer from an account held by the originator with the originating VASP - enables the originating VASP to identify the account; or
    • (ii) for a transfer of a virtual asset from a custodial wallet - enables the originating VASP to identify the originator's virtual asset holdings in the wallet (such as by providing the wallet address, including the destination tag or memo details, if applicable); or
    • (iii) for a transfer of a virtual asset from a self-hosted virtual asset wallet - provides the address of the wallet; or
    • (iv) in any other case - provides a unique transaction reference number for the transfer of value;
  • c) Information that is one or more of the following:
    • (i) a unique customer identification number given to the originator by the originating VASP;
    • (ii) a unique identification number given to the originator by an Australian government body, other than the originator's tax file number (within the meaning of section 202A of the Income Tax Assessment Act 1936);
    • (iii) a unique identification number given to the originator by the government of a foreign country;
    • (iv) a unique identification number given to the originator by an organisation accredited by the Global Legal Entity Identification Foundation;
    • (v) if the originator is an individual-the originator's date and place of birth;
    • (vi) the originator's full business or residential address (not being a post box).

Beneficiary:

  • d) Full official name;
  • e) Tracing information in relation to the transfer of value which means information that satisfies the following:
    • (i) for a transfer from an account held by the originator with the originating VASP - enables the originating VASP to identify the account; or
    • (ii) for a transfer of a virtual asset from a custodial wallet - enables the originating VASP to identify the originator's virtual asset holdings in the wallet (such as by providing the wallet address, including the destination tag or memo details, if applicable); or
    • (iii) for a transfer of a virtual asset from a self-hosted virtual asset wallet - provides the address of the wallet; or
    • (iv) in any other case - provides a unique transaction reference number for the transfer of value.

Legal Entity


Originator:

  • f) Registered name;
  • g) Tracing information in relation to the transfer of value which means information that satisfies the following:
    • (i) for a transfer in circumstances where the value is to be made available to the beneficiary by depositing it into an account held by the beneficiary - enables the beneficiary VASP to identify the account; or
    • (ii) for a transfer of a virtual asset in circumstances where the asset is to be made available to the beneficiary by transferring it to a custodial wallet - enables the beneficiary VASP to identify the originator's virtual asset holdings in the wallet (such as by providing the wallet address, including the destination tag or memo details, if applicable); or
    • (iii) for a transfer of a virtual asset in circumstances where the value is to be made available to the beneficiary by transferring it to a self-hostedvirtual asset wallet - provides the address of the wallet; or
    • (iv) in any other case - provides a unique transaction reference number for the transfer of value;h) Information that is one or more of the following:
    • (i) a unique customer identification number given to the originator by the originating VASP;
    • (ii) a unique identification number given to the originator by an Australian government body, other than the originator's tax file number (within themeaning of section 202A of the Income Tax Assessment Act 1936);
    • (iii) a unique identification number given to the originator by the government of a foreign country;
    • (iv) a unique identification number given to the originator by an organisation accredited by the Global Legal Entity Identification Foundation;
    • (v) the originator's full business or residential address (not being a post box).

Beneficiary:

  • i) Registered name;
  • j) Tracing information in relation to the transfer of value which means information that satisfies the following:
    • (i) for a transfer in circumstances where the value is to be made available to the beneficiary by depositing it into an account held by the beneficiary - enables the beneficiary VASP to identify the account; or
    • (ii) for a transfer of a virtual asset in circumstances where the asset is to be made available to the beneficiary by transferring it to a custodial wallet - enables the beneficiary VASP to identify the originator's virtual asset holdings in the wallet (such as by providing the wallet address, including the destination tag or memo details, if applicable); or
    • (iii) for a transfer of a virtual asset in circumstances where the value is to be made available to the beneficiary by transferring it to a self-hosted virtual asset wallet - provides the address of the wallet; or
    • (iv) in any other case - provides a unique transaction reference number for the transfer of value.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

To be added later.

Batch file transfer

No special provisions.

Unhosted wallet verification

Required.

VASP Due Diligence

Required.

Time and way to share the Information

The regulation does not establish specific provisions. In accordance with the FATF's recommendations, the required information must be transmitted immediately and securely.

Record retention

To be determined later.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from 23 February 2022.

Regulation

Regulatory body

Threshold

None. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 14, 2020.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or a unique transaction identifier); and
  • c) Address or date and place of birth or the payer's national identity number or customer identification number.

Beneficiary:

  • d) Full name;
  • e) Account number (or a unique transaction identifier).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

There is a difference.


Domestic. The following data needs to be transferred: b), but other data should be provided within three business days after request.


Cross-border. The following data should be transferred:

  • < BSD 1,000: a), b), d), e);
  • > BSD 1,000: a), b), c), d), e).

Batch file transfer

Where a batch file transfer comprises individual wire transfers (VA transfers) of one thousand dollars or more from a single payer (originator) to payees (beneficiary) outside The Bahamas, the originating financial institution shall be exempted from the requirements of paragraph 3 of the Section "The main actions required" in respect of the inclusion of the payer's information with each individual transfer, provided that

  • (a) the batch file contains the information required under paragraph 3 specified in Section "The main actions required" on
    • (i) the payer;
    • (ii) the payees; and
  • (b) the individual wire transfers include the payer's account number or, if no account is used , a unique transaction identifier.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation does not establish specific provisions. In accordance with the FATF's recommendations, the required information must be transmitted immediately and securely.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force.

  • From January 1, 2020 — for crypto-asset licensees.
  • From January 1, 2024 — for investment firm licensees.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (e.g. IBAN or crypto-asset wallet) where such an account is used to process the transaction;
  • c) Address, or national identity number, or customer identification number, or date and place of birth.

Beneficiary:

  • d) Full name; and
  • e) Account number (e.g. IBAN or crypto-asset wallet) where such an account is used to process the transaction.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference. VASPs must consider all transfers of crypto-assets as cross-border wire transfers rather than domestic transfers.

Batch file transfer

There are no special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from January 1, 2018.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:


Natural Person:

  • a) Full name;
  • b) Address (or date and place of birth, customer identification number or national identity number);
  • c) Account number (or unique identifier).

Legal Entity:

  • a) Full name;
  • b) Address;
  • c) Account number (or unique identifier).

Beneficiary:

  • d) Full name;
  • e) Account number (or unique identifier).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

There is a difference.


Domestic.


The following data needs to be transferred irrespective of the threshold: c), but other data should be provided within three business days after request.


Cross-border.


> USD 1,000: a), b), c), d), e).

Batch file transfer

Where there is a batch file transfer from a single payer and the payee PSP is situated outside Bermuda, complete information will be considered to have been transferred, provided that:

  • a) The batch file transfer contains complete information on the payer and on each of the payees for each individual transfer;
  • b) The individual transfers of funds carry the account number of the payer or a unique identifier where an account number is not available; and
  • c) The complete information provided on all payees is fully traceable within the beneficiary country.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

When establishing a correspondent relationship with a VASP registered outside Bermuda.

Time and way to share the Information

The essential information of each transfer should be accurate, complete and immediately available.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 1, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name (registered or trading names where the originator is a legal structure);
  • b) Address;
  • c) Account number where the account is used to process a transaction (or other unique transaction identifiers)
  • d) One of the following: date and place of birth; or the customer identification number or national identity number.

Beneficiary:

  • e) Full name (registered or trading names where the beneficiary is a legal structure);
  • f) Account number where the account is used to process a transaction (or other unique transaction identifiers).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In cases of batch file transfers of virtual assets from a single originator, the obligation of the originator’s VASP to ensure that information on the originator accompanies each transfer shall not apply to the individual transfers bundled within the batch file, provided that the batch file contains comprehensive information on both the originator and beneficiary. This information must be fully traceable within the beneficiary’s jurisdiction, and each individual transfer within the batch file must include the originator's account number or a unique identifier.

Unhosted wallet verification

Requirement applicable in cases of heightened risk.

VASP Due Diligence

When establishing a correspondent relationship with a VASP registered outside the BVI.

Time and way to share the Information

The required information shall be transmitted simultaneously and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from April 1, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Address;
  • c) Account number or other reference number (if any) of the person or entity who requested the transfer (originator information).

Beneficiary:

  • d) Full name;
  • e) Address;
  • f) Account number or other reference number (if any) of the beneficiary.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation does not establish specific provisions. In accordance with the FATF's recommendations, the required information must be transmitted immediately and securely.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from July 1, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or unique transaction reference number that permits traceability of the transaction); or
  • c) One of the following: address, or number of a government-issued document evidencing the originator's identity; or customer identification number or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or unique transaction reference number that permits traceability of the transaction).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

For batch file transfers of virtual assets from a single originator, the obligation on the VASP of the originator to ensure that information on the originator accompanies transfers of virtual assets shall not apply to the individual transfers of virtual assets bundled together if—(a) the batch file contains — (i) the name of the originator; (ii) where an account is used to process the transfer of virtual assets by the originator, the account number of the originator; (iii) the address of the originator, the number of a Government-issued document evidencing the originator’s identity or the originator’s customer identification number or date and place of birth; and (b) the individual transfers of virtual assets carry the account number of the originator or a unique identifier. A batch file shall contain the name, account number or unique identifier of the beneficiary that is traceable in the beneficiary country.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be submitted simultaneously or concurrently with the transfer.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on July 1, 2025.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value of USD 1,000 or more.

Data to be shared

Natural Person


Originator:

  • a) Name;
  • b) Account number, where such account is used to process the transaction;
  • c) National identity card number, for Chileans and residents, or passport number or equivalent identification document for non-resident foreigners.
  • d) Address.

Beneficiary:

  • e) Name;
  • f) Account number, where such account is used to process the transaction.

Legal Entity


Originator:

  • g) Registered name;
  • h) Account number, where such account is used to process the transaction;
  • i) Tax ID number (RUT) or equivalent identification number if the entity is foreign;
  • j) Address.

Beneficiary:

  • k) Registered name;
  • l) Account number, where such account is used to process the transaction.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation do not explicitly specify the time frame for information sharing. In turn, according to the interpretive note to FATF Recommendation 15, originating VASPs should submit the information on the originator and beneficiary to the beneficiary VASP immediately and securely.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from January 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number;
  • c) Physical or geographical address of the originator, or the national identity number, or the customer identification number that uniquely identifies the originator of the ordering institution, or the date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number.

Subject

Details

Threshold-based data

USD 1,000

  • < USD 1,000: a), b), d), e).
  • > USD 1,000: a), b), c), d), e).

Domestic vs cross-border transfers

No difference.


Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from September 7, 2021.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value of USD 1,000 or more.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number;
  • c) Address (when available);
  • d) Identification of the financial institution;
  • e) Negotiated amount;
  • f) Execution date.

Beneficiary:

  • g) Full name;
  • h) Address (When available);
  • i) Identification of the financial institution;
  • j) Account number;
  • k) Any other identifying information of the recipient (When available).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation does not establish specific provisions. In accordance with the FATF's recommendations, the required information must be transmitted immediately and securely.

Record retention

15 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 15, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on December 31, 2027.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value exceeding EUR 1,000 or USD 1,000 or GEL 3,000.

Data to be shared

Originator:

  • a) Full name (in the case of an individual - first and last name);
  • b) Distributed ledger address, if the transfer of the virtual asset is recorded on a network that uses distributed ledger technology (DLT) or similar technology, and the originator's virtual asset account number, if such an account exists and is used for processing the transfer;
  • c) Virtual asset account number, if the transfer of the virtual asset is not recorded on a network that uses distributed ledger technology (DLT) or similar technology;
  • d) Address, including the name of the country, or the originator's identity document/passport number or personal identification number, or the originator's date and place of birth;
  • e) Official identification data of the legal entity (possibly including the LEI), if the relevant field is presented in the transfer message format and provided by the originator to the VASP.

Beneficiary:

  • a) Full name (in the case of an individual - first and last name);
  • b) Distributed ledger address, if the transfer of the virtual asset is recorded on a network that uses distributed ledger technology (DLT) or similar technology, and the beneficiary's virtual asset account number, if such an account exists and is used for processing the transfer;
  • c) Virtual asset account number, if the transfer of the virtual asset is not recorded on a network that uses distributed ledger technology (DLT) or similar technology;
  • d) Official identification data of the legal entity of the beneficiary (possibly including the LEI), if the relevant field is presented in the transfer message format and provided by the beneficiary to the VASP.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer, the originator's required information need not accompany each individual virtual asset transfer, provided that:

  • a) the batch is accompanied by the remaining required information;
  • b) the information is verified, and the individual transactions comprising the batch file meet one of the following conditions:
    • i) it contains the beneficiary's distributed ledger address, if the virtual asset transfer is registered on a network using DLT or similar technology, as well as the asset beneficiary's virtual asset account number, if such an account exists and is used to process the transfer;
    • ii) the virtual asset account number of the recipient, if the transfer of the virtual asset is not registered on a network that uses DLT or similar technology;
    • iii) if the transfer is not registered on a network using DLT or similar technology, and simultaneously the virtual asset transfer is neither made from nor to a virtual asset account, the VASP is required to ensure that the transfer is accompanied by a unique transaction code.

Unhosted wallet verification

Required if the value of the virtual asset transferred to a self-hosted address exceeds EUR 1,000 or USD 1,000 or GEL 3,000 or the equivalent in other foreign currencies.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information must be transmitted prior to or during the transfer of the virtual asset, in a secure manner and in compliance with the Law of Georgia on Personal Data Protection. Furthermore, the VASP is not required to accompany the virtual asset transfer transaction with the information by directly attaching it to, or embedding it within, the virtual asset transfer itself.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from October 1, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.


Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

Data to be shared

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

Batch file transfer

Unhosted wallet verification

VASP Due Diligence

Time and way to share the Information

Record retention

Subject

Details

Status

In force from September 22, 2022.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value of EUR 1,000 or more.

Data to be shared

Originator:

  • a) Full name;
  • b) Virtual asset account number (where there is no virtual asset account number, a unique transaction identifier);
  • c) One of the following: address; or national identity number; or customer identification number; or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Virtual asset account number (where there is no virtual asset account number, a unique transaction identifier).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from July 10, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full official name;
  • b) Where a transfer of virtual assets is registered on a network using DLT or similar technology, the originator’s distributed ledger address and the originator’s virtual asset account number, where such an account exists and is used to process the transaction;
  • c) Where a transfer of virtual assets is not registered on a network using DLT or similar technology, the originator’s account numbers;
  • d) Where a transfer of virtual assets is neither registered on a network using DLT or similar technology nor is made from or to a virtual asset account, the originating VASP shall ensure that the transfer of virtual assets is accompanied by a unique transaction identifier which permits traceability of the transaction;
  • e) One of either: (i) the originator’s address, including the name of the country, (ii) national identity number, (iii) customer identification number or (iv) date and place of birth;
  • f) Subject to the existence of the necessary field in the relevant message format, and where provided by the originator to the originator’s VASP, the current LEI of the originator or any other available equivalent official identifier.

Beneficiary:

  • g) Full official name;
  • h) Where a transfer of virtual assets is registered on a network using DLT or similar technology, the beneficiary’s distributed ledger address and the beneficiary’s virtual asset account number, where such an account exists and is used to process the transaction;
  • i) Where a transfer of virtual assets is not registered on a network using DLT or similar technology, the beneficiary’s account numbers;
  • j) Where an account is not used to process the transfer, the unique transaction identifier which permits the traceability of the transaction;
  • k) Subject to the existence of the necessary field in the relevant message format, and where provided by the originator to the originator’s VASP, the current LEI of the originator or any other available equivalent official identifier.

Subject

Details

Threshold-based data

Sumsub has submitted a request to the Guernsey Financial Services Commission for clarification on the application of the rules concerning the minimum threshold amount. This information will be updated upon receipt of the regulator's response.


GGP 1,000


Where a transfer is carried out which is under the GGP 1,000 threshold, VASPs must obtain and hold:

  • a) the names of the originator and the beneficiary; and
  • b) the virtual asset wallet address for each party or a unique transaction reference number.

It is not necessary to verify the originator's information unless the virtual assets to be transferred have been received anonymously, or the VASP has reasonable grounds to suspect ML, TF and/or PF.

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch transfer, an originating VASP shall:

  • a) ensure that the batch file contains required and accurate originator information and required beneficiary information;
  • b) ensure that the information is such as to permit the traceability within the beneficiary jurisdiction of each transaction comprised in the batch from the originator to the beneficiary (and “beneficiary jurisdiction” means the jurisdiction in which the beneficiary VASP received the transfer of the virtual assets); and
  • c) include the originator’s account number or unique transaction identifier and/or such other information, or information of such a class or description, as may be specified in the Handbook on Countering Financial Crime (AML/CFT/CPF).

The batch file information requirements which apply where several individual virtual asset transfers with a single originator are bundled together for transmission in a batch transfer include:

  • a) The name of the originator;
  • b) Where an account is used to process the transfer of virtual assets by the originator, the account number of the originator;
  • c) One of either (i) the originator’s address, including the name of the country, (ii) national identity number, (iii) customer identification number or (iv) date and place of birth;
  • d) The individual transfers of virtual assets carry the account number of the originator or a unique identifier; and
  • e) The name, account number or unique identifier of the beneficiary that is traceable in the beneficiary country.

Where a transfer is carried out which is under the GGP 1,000 threshold, VASPs must obtain and hold:

  • a) the names of the originator and the beneficiary; and
  • b) the virtual asset wallet address for each party or a unique transaction reference number.

It is not necessary to verify the originator's information unless the virtual assets to be transferred have been received anonymously, or the VASP has reasonable grounds to suspect ML, TF and/or PF.

Unhosted wallet verification

Required for transactions exceeding GGP 1,000.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information should be submitted in advance of, or simultaneously or concurrently with, the transfer of virtual assets and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or a unique reference number);
  • c) Address, customer identification number or identification document number or, date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or a unique reference number).

Subject

Details

Threshold-based data

HKD 8,000

  • < HKD 8,000: a), b), d), e);
  • ≥ HKD 8,000: a), b), c), d), e).

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

Required.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

8 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 10, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Permanent Account Number (PAN) or National Identity Number;
  • b) Full name;
  • c) Account number;
  • d) Physical (geographical) address, or date and place of birth.

Beneficiary:

  • e) Full name;
  • f) Account number.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence;
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from October 1, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Wallet address;
  • c) Residential address;
  • d) For Indonesians: Identity card number; for non-Indonesians: passport number, identity card number issued by the individual's country of origin, permanent residence permit card number or limited residence permit card number (if available).

Beneficiary:

  • e) Full name;
  • f) Wallet address;
  • g) Residential address.

Subject

Details

Threshold-based data

USD 1,000

  • < USD 1,000: a), b), e), f);
  • ≥ USD 1,000: a), b), c), d), e), f), g).

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special requirement.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

10 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from October 28, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person:


Originator:

  • a) Full official name;
  • b) Unique account Identifier (or a unique transaction identifier);
  • c) One of the following: address, a national identity number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Unique account Identifier (or a unique transaction identifier).

Legal Entity:


Originator:

  • f) Registered name (or a trading name);
  • g) Unique account Identifier (or a unique transaction identifier);
  • h) Registered office address, or if different, or if there is none, a principal place of business.

Beneficiary:

  • i) Registered name (or a trading name);
  • j) Unique account Identifier (or a unique transaction identifier).

Subject

Details

Threshold-based data

EUR 1,000


Natural Person:

  • < EUR 1,000: a), b), d), e);
  • > EUR 1,000: a), b), c), d), e).

Legal Entity: No difference.

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer, the information required specified does not have to accompany each individual virtual asset transfer provided that:

  • a) each individual virtual asset transfer within the batch is accompanied by the unique account identifier or, if there is no unique account identifier, the unique transaction identifier; and
  • b) the batch is accompanied by the remaining required information.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from November 14, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Identity number (or a unique identity number), or the date of birth or the date of incorporation;
  • c) Address;
  • d) Account number (or another unique identification number).

Beneficiary:

  • a) Full name;
  • b) Account number (or another unique identification number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the event a Service Provider performed a number of cross border electronic wire transfers from Israel, or transfers of virtual currency, for the same originator in one batch file, the said batch file will include the information contained in Section "Data to be shared" with respect to each of the transfers in the batch file.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Name;
  • b) Identifier related to the transfer, or an alphanumeric code sufficient to identify such identifier;
  • c) Residential address, or identity verification document, or a customer identification number.

Beneficiary:

  • d) Name;
  • e) Identifier related to the transfer, or an alphanumeric code sufficient to identify such identifier.

Legal Entity


Originator:

  • f) Registered name;
  • g) Identifier related to the transfer, or an alphanumeric code sufficient to identify such identifier;
  • h) Location of the head office or principal business office, or customer identification number.

Beneficiary:

  • i) Registered name;
  • j) Identifier related to the transfer, or an alphanumeric code sufficient to identify such identifier.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

If a virtual asset transfer is carried out to a VASP incorporated in a jurisdiction other than those specified in the list approved by the FSA, the Travel Rule does not apply; however, such transfers are not prohibited.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted at the time of the transfer.

Record retention

7 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from September 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person:


Originator:

  • a) Full name;
  • b) Account number (or other unique transaction identifiers);
  • c) One of the following: customer identification number; or address; or birth certificate, passport number, or national ID card number (or individual's date and place of birth).

Beneficiary:

  • d) Full name;
  • e) Account number (or other unique transaction identifiers).

Legal Entity:


Originator:

  • f) Registered or trading names;
  • g) Account number (or other unique transaction identifiers);
  • h) One of the following: customer identification number; or address of registered office (or principal place of business).

Beneficiary:

  • i) Registered or trading names;
  • j) Account number (or other unique transaction identifiers).

Subject

Details

Threshold-based data

EUR 1,000

Natural Person/Legal Entity

Domestic:

  • b) and e).

If additional information is requested, then:

  • < EUR 1,000: a), b), d), e);
  • > EUR 1,000: a), b), c), d), e).

Cross-border:

The following data should be transferred:

  • < EUR 1,000: a), b), d), e);
  • > EUR 1,000: a), b), c), d), e).

Domestic vs cross-border transfers

There is a difference.

Natural Person:

Domestic. The following data should be transferred: b) and e). However, within three working days of receiving a request for information from the beneficiary's CASP or ICASP, the following data should be made available:

  • < EUR 1,000: a), b), d), e);
  • > EUR 1,000: a), b), c), d), e).

Cross-border. The following data should be transferred:

  • < EUR 1,000: a), b), d), e);
  • > EUR 1,000: a), b), c), d), e).

Legal Entity:

Domestic. The following data should be transferred: g) and j). However, within three working days of receiving a request for information from the beneficiary's CASP or ICASP, the following data should be made available:

  • < EUR 1,000: f), g), i), j);
  • > EUR 1,000: f), g), h); i), j).

Cross-border. The following data should be transferred:

  • < EUR 1,000: f), g), i), j);
  • > EUR 1,000: f), g), h); i), j).

Sumsub has submitted a request to the Jersey Financial Services Commission for clarification on the application of the rules concerning the minimum threshold amount. This information will be updated upon receipt of the regulator's response.

Batch file transfer

In the case of a batch file transfer from a single originator where the CASPs of the beneficiaries are established outside the EU, the obligation on the CASP of the originator to ensure that information on the originator accompanies transfers of funds shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and the beneficiary, that the information has been properly verified, and that the individual transfers carry the account number of the originator or, where the exception is applied, the unique transaction identifier.

Unhosted wallet verification

Required in cases of higher risk.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation do not explicitly specify the time frame for information sharing. In turn, according to the interpretive note to FATF Recommendation 15, originating CASPs should submit the information on the originator and beneficiary to the beneficiary CASP immediately and securely.

Record retention

6 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from January 1, 2025.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Digital asset wallet address or account number or (in the absence of an account) unique transaction reference number;
  • c) Physical address, or national identity number, or customer identification, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Digital asset wallet address or account number or (in the absence of an account) unique transaction reference number.

Legal Entity


Originator:

  • f) Registered corporate name or trading name;
  • g) Digital asset wallet address or account number or (in the absence of an account) unique transaction reference number;
  • h) Either of the following: (i) the customer identification number; or (ii) the registered office address or primary place of business.

Beneficiary:

  • i) Registered corporate name or trading name;
  • j) Digital asset wallet address or account number or (in the absence of an account) unique transaction reference number.

Subject

Details

Threshold-based data

USD 1,000

Natural Person

  • < USD 1,000: a), b), d), e);
  • ≥ USD 1,000: a), b), c), d), e).

Legal Entity

  • < USD 1,000: f), g), i), j);
  • ≥ USD 1,000: f), g), h), i), j).

Domestic vs cross-border transfers

No difference.

Batch file transfer

If several transfers from a single originator are bundled in a batch file for transmission to beneficiaries, they may be exempted from the requirements in respect of originator information, provided that they include the originator’s account number or unique transaction reference number, and the batch file contains required and accurate originator information, and full beneficiary information, that is fully traceable within the beneficiary country.

Unhosted wallet verification

Required for transactions exceeding USD 1,000, as well as when there is a suspicion of money laundering or terrorist financing involving a transfer to a self-hosted digital wallet.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

As a general rule, the period is 5 years; for intermediary VASPs, it is 6 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 1, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

8 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 30, 2020.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from April 26, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) National registration identity card number or passport number;
  • c) Account number or digital wallet address or a unique transaction reference number;
  • d) Address or date and place of birth.

Beneficiary:

  • e) Full name;
  • f) Account number or digital wallet address or a unique transaction reference number.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The regulation does not establish specific provisions. In accordance with the FATF's recommendations, the required information must be transmitted immediately and securely.

Record retention

7 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from August 31, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or a unique reference number that permits the transaction to be traced if there is no account);
  • c) Address, national identity number, customer identification number, or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or a unique reference number that permits the transaction to be traced if there is no account).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

Where several individual transfers from a single originator are bundled in a batch file for transmission to beneficiaries, they are exempt from the originator information requirements provided that:

  • a) they include the originator's account number (or unique reference number); and
  • b) the batch file contains full and accurate originator information, and full beneficiary information, that is fully traceable within the beneficiary country.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and securely.

Record retention

6 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from February 7, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or a unique transaction reference number);
  • c) One of the following information: physical address; or national identity card number or passport number; or customer identification number; or place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or a unique transaction reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

7 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from September 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Virtual asset account number (or unique transaction reference number);
  • c) One of the following: address; or national identity card number or passport number; or customer identification number; or place of birth.

Beneficiary:

  • g) Full name;
  • h) Virtual asset account number (or unique transaction reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

For batch file transfers of virtual assets from a single originator, the individual transfers of virtual assets bundled must contain the following information:


Originator:

  • a) Full name;
  • b) Account number;
  • c) One of the following: address; or national identity card number or passport number; or customer identification number; or date and place of birth;
  • d) Individual transfers of virtual assets must carry the account number or unique identifier;
  • e) Any other information and documents as the The Bank of Namibia may require.

Beneficiary:

  • f) Full name;
  • g) Account number (or unique identifier that is traceable in the beneficiary’s country).

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 1, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number or other identifying information;

One of the following:

  • c) Address;
  • d) National identity number;
  • e) Customer identification number;
  • f) Place and date of birth.

Beneficiary:

  • g) Full name;
  • h) Account number (or a unique transaction reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

There is a difference.


Domestic. The following data needs to be transfered: b), but a), c), d), e), f), g) or other information should be provided within three working days after the request.


Cross-border: a), b), c), d), e), f), g), h).

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

Any information about the originator obtained by a reporting entity that is an intermediary institution must be provided by that reporting entity to the beneficiary institution as soon as practicable.


The information obtained by the reporting entity must accompany the wire transfer.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from January 9, 2025.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Name;
  • b) Distributed ledger address, in cases where the virtual asset transfer is recorded on a network using distributed ledger technology (DLT) or similar technology, and the originator's virtual asset account number, where such account exists and is used to process the transaction. In cases where the transfer is not recorded on a DLT network or similar technology, the virtual asset account number should be provided;
  • c) Address, official identity document number or customer identification number, or date and place of birth.

Beneficiary:

  • d) Name;
  • e) Distributed ledger address, in cases where the virtual asset transfer is recorded on a network using distributed ledger technology (DLT) or similar technology, and the originator's virtual asset account number, where such account exists and is used to process the transaction. In cases where the transfer is not recorded on a DLT network or similar technology, the virtual asset account number should be provided.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address, in cases where the virtual asset transfer is recorded on a network using distributed ledger technology (DLT) or similar technology, and the originator's virtual asset account number, where such account exists and is used to process the transaction. In cases where the transfer is not recorded on a DLT network or similar technology, the virtual asset account number should be provided;
  • h) Address, official identification document number or customer identification number.

Beneficiary:

  • i) Registered name;
  • j) Distributed ledger address, in cases where the virtual asset transfer is recorded on a network using distributed ledger technology (DLT) or similar technology, and the originator's virtual asset account number, where such account exists and is used to process the transaction. In cases where the transfer is not recorded on a DLT network or similar technology, the virtual asset account number should be provided.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

There is a difference.


Domestic transfer

  • Natural Person: a), b), c), d), e).
  • Legal Entity: f), g), h), i), j).

In the case of domestic virtual asset transfers, where the beneficiary VASP already holds the originator's and beneficiary's information, the originating VASP may include only the transaction identifier, provided it allows tracing of the virtual asset transfer to either the originator or the beneficiary. If the beneficiary VASP or competent authorities request the full information, the originating VASP shall provide it within three working days of the request.


Cross-border

  • Natural Person: a), b), c), d), e).
  • Legal Entity: f), g), h), i), j).

Batch file transfer

Where multiple individual virtual asset transfers from a single originator are bundled into a single batch file for transmission to beneficiaries, the file must contain the required information, which must be fully traceable in the beneficiary’s jurisdiction and include the originator’s distributed ledger address, the virtual asset account number, or a unique identifier or transaction reference number.

Unhosted wallet verification

Required for transactions exceeding USD 1,000.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be provided securely and either prior to or at the same time as the virtual asset transfer.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from May 12, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Wallet address;
  • c) Physical address or national identity number or, where the originator is not a natural person, the incorporation number or business registration number.

Beneficiary:

  • d) Full name;
  • e) Wallet address.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 6, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Wallet address, where such an account is used to process the virtual asset transfer or a unique transaction reference which permits traceability of the transaction;
  • c) Physical address, or national identification or customer identification number, or the date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Wallet address where such an account is used to process the transaction, an account number, or a unique transaction reference which permits traceability of the transaction.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

10 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on August 1, 2026.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) First and last names;
  • b) Account number, when it is used to process the transaction or the virtual asset wallet address, as applicable, or if there is no account, the operation reference code that allows it to be traced;
  • c) Identity document number;
  • d) Address or date and place of birth.

Beneficiary:

  • e) First and last names;
  • f) Account number, when it is used to process the transaction or the virtual asset wallet address, as applicable, or if there is no account, the operation reference code that allows it to be traced.

Legal Entity


Originator:

  • g) Registered name;
  • h) Account number, when it is used to process the transaction or the virtual asset wallet address, as applicable, or if there is no account, the operation reference code that allows it to be traced;
  • i) Unique taxpayer registry number (RUC) or equivalent registration number;
  • j) Operation identification number.

Beneficiary:

  • k) Registered name;
  • l) Account number, when it is used to process the transaction or the virtual asset wallet address, as applicable, or if there is no account, the operation reference code that allows it to be traced.

Subject

Details

Threshold-based data

USD 1,000

Natural Person

  • < USD 1,000: a), b), c), e), f);
  • ≥ USD 1,000: a), b), c), d), e), f).

Legal Entity

  • < USD 1,000: g), h), i), k), l;
  • ≥ USD 1,000: g), h), i), j), k), l.

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from February 5, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number;
  • c) Physical (geographical) address, or national identity number, or customer identification number, or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number.

Subject

Details

Threshold-based data

PHP 50,000

  • < PHP 50,000: a), b), d), e).
  • ≥ PHP 50,000: a), b), c), d), e).

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

Required.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from July 15, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

7 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 29, 2021.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Name;
  • b) Digital asset address, or the unique identifier of the digital asset transaction;
  • c) Residential or domicile address. If the data concerning the address was not obtained, one of the following identifiers shall be collected: i) national identification number (e.g., a unique master citizen number (JMBG)); or ii) personal identification document number, date and place of birth.

Beneficiary:

  • d) Name;
  • e) Digital asset address, or the unique identifier of the digital asset transaction;
  • f) Residential or domicile address. If the data concerning the address was not obtained, one of the following identifiers shall be collected: i) national identification number (e.g., a unique master citizen number (JMBG)); or ii) personal identification document number, date and place of birth.

Legal Entity


Originator:

  • g) Registered name;
  • h) Digital asset address, or the unique identifier of the digital asset transaction;
  • i) Identification number or, if such a number does not exist, another appropriate unique identification mark;
  • j) Registered office address. If the data concerning the address was not obtained, one of the following data shall be collected: i) national identification number (e.g., a legal entity registration number); or ii) unique identification number.

Beneficiary:

  • k) Registered name;
  • l) Digital asset address, or the unique identifier of the digital asset transaction;m) Registered office address. If the data concerning the address was not obtained, one of the following data shall be collected: i) national identification number (e.g., a legal entity registration number); or ii) unique identification number.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of digital assets from a single originator, the obligation on the DASP of the originator to ensure that transfers of digital assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the digital asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The data shall be provided to the other DASP simultaneously with the execution of the digital asset transaction and in a manner that ensures the integrity of such data and protection from unauthorised access to such data.

Record retention

10 years.

Obligations of the originating DASP

The originating DASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which DASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary DASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary DASP

The beneficiary DASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which DASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary DASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating DASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary DASP

The intermediary DASP must:

  • receive information about the originator and beneficiary from the previous DASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating DASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which DASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary DASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from September 1, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Wallet address (or unique transaction reference number);
  • c) Address (including the name of the country, government issued identification information inclusive of the national identification number (if applicable) or customer identification number or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Wallet address (or unique transaction reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

For batch file virtual asset transfers from a single originator, Section "The main actions required" shall not apply to the individual transfers where -

  • (a) the transfers are bundled together as a batch file and the batch file includes -
    • (i) the name of the originator; and
    • (ii) location data concerning the originator as specified under Section "Data to be shared";
  • (b) where a wallet is used, the wallet address(es);
  • (c) where a wallet is not used to process virtual asset transfers, the unique transaction reference number (commonly known as a transaction hash) utilised for the tracing of the transfer.

All information above should be transferred without delay to the beneficiary virtual asset service provider, together with transmission of the set of payment instructions to the beneficiary virtual asset service provider or to the beneficiary's financial institution.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

An originating virtual asset provider shall provide the information under Section "Data to be shared", without delay to the beneficiary virtual asset service provider, together with transmission of the set of payment instructions to the beneficiary virtual asset service provider or to the beneficiary's financial institution.


An originating virtual asset service provider may provide the information under Section "Data to be shared" to the beneficiary virtual asset service provider or reporting entity directly by attaching the information to the virtual asset transfer or providing the information directly.

Record retention

7 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

Data to be shared

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

Batch file transfer

Unhosted wallet verification

VASP Due Diligence

Time and way to share the Information

Record retention

Subject

Details

Status

In force from January 28, 2020.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full name;
  • b) Account number (or unique transaction reference number where no account number exists);
  • c) One of the following: (i) residential address; (ii) unique identification number (such as an identity card number, birth certificate number or passport number); or (iii) the date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or unique transaction reference number where no account number exists).

Legal Entity


Originator:

  • f) Registered name;
  • g) Account number (or unique transaction reference number where no account number exists);
  • h) One of the following: (i) registered or business address, and if different, principal place of business, as may be appropriate; (ii) unique identification number (such as an incorporation number or business registration number); or (iii) the date and place of incorporation or registration (as may be appropriate).

Beneficiary:

  • i) Registered name;
  • j) Account number (or unique transaction reference number where no account number exists).

Subject

Details

Threshold-based data

SGD 1,500


Natural Person

  • ≤ SGD 1,500: a), b), d), e);
  • > SGD 1,500: a), b) c), d), e).

Legal Entity

  • ≤ SGD 1,500: f), g), i), j);
  • > SGD 1,500: f), g) h), i), j).

Please also see the Domestic vs cross-border transfers section.

Domestic vs cross-border transfers

There is a difference.


Ordering VASP may, in the message or payment instruction that accompanies or relates to the value transfer to an intermediary VASP in Singapore, include only the unique transaction reference number and the beneficiary's name and account number (or unique transaction reference number where no account number exists), provided that:

  • a) the unique transaction reference number will permit the transaction to be traced back to the originator and beneficiary;
  • b) the ordering VASP shall provide the required originator information and beneficiary information within three business days of a request for such information by the intermediary VASP in Singapore, the Monetary Authority of Singapore or other relevant authorities in Singapore;
  • c) the ordering VASP shall provide the required originator information and beneficiary information immediately upon request for such information by law enforcement authorities in Singapore; and
  • d) the ordering VASP shall provide the required originator information and beneficiary information to the beneficiary VASP.

Batch file transfer

Where multiple individual transfers from a single originator are combined in a batch file for transmission to beneficiaries, a VASP shall ensure that the batch transfer file contains:

  • a) the required originator information, which has been verified; and
  • b) the required beneficiary information, which is fully traceable within the beneficiary country or jurisdiction.

Unhosted wallet verification

Required.


Where the transfer of digital payment token has been received from or sent to the VASP’s own customer’s personal wallet address, the customer should demonstrate control over the said wallet address, by effecting a transfer of digital payment token of an amount specified by the VASP.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from April 30, 2025.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Persons


Originator:

  • a) Full name;
  • b) Identity number, if the originator is a South African citizen or resident; or passport number or foreign national identity number, and date of birth, if the originator is not a South African citizen or resident;
  • c) Residential address, if such an address is readily available; or country of birth, if the residential address is not readily available;
  • d) Distributed ledger address associated with the transfer, if the transfer is registered on a network using distributed ledger or similar technology;
  • e) Crypto asset account number with the ordering CASP, if such an account is used to process the transaction, or a unique transaction reference number, if such an account number is not available.

Beneficiary:

  • f) Full name;
  • g) Distributed ledger address associated with the transfer, in cases, if the transfer is registered on a network using distributed ledger or similar technology;
  • h) Crypto asset account number with the recipient CASP, if such an account is used to process the transaction and this information is readily available to the ordering crypto asset service provider.

Legal Entities


Originator:

  • i) Registered name;
  • j) Registration number under which it is incorporated; and
  • k) Registered address;
  • l) Distributed ledger address associated with the transfer, if the transfer is registered on a network using distributed ledger or similar technology;
  • m) Crypto asset account number with the ordering CASP, if such an account is used to process the transaction, or a unique transaction reference number, if such an account number is not available.

Beneficiary:

  • n) Registered name;
  • o) Distributed ledger address associated with the transfer, in cases, if the transfer is registered on a network using distributed ledger or similar technology;
  • p) Crypto asset account number with the recipient CASP, if such an account is used to process the transaction and this information is readily available to the ordering crypto asset service provider.

Subject

Details

Threshold-based data

If < ZAR 5,000


Natural Persons:

  • Originator: a), d), e);
  • Beneficiary: f), g), h).

Legal Entities:

  • Originator: i), l), m);
  • Beneficiary: n), o), p).

An ordering crypto asset service provider need not verify the above-mentioned information in respect of a transfer that is a single transaction valued at less than ZAR 5,000 for accuracy, unless there is a suspicion of money laundering or terrorist financing, in which case, the ordering crypto asset service provider must verify the information pertaining to the originator.

In respect of an inward transfer that is a single transaction valued at less than ZAR 5,000 from an originator in a high-risk or other monitored jurisdiction, a recipient CASP must verify the accuracy of the beneficiary information.


If ≥ ZAR 5,000


Natural Persons:

  • Originator: a), b), c), d), e);
  • Beneficiary: f), g), h).

Legal Entities:

  • Originator: i), j), k), l), m);
  • Beneficiary: n), o), p).

Domestic vs cross-border transfers

Sumsub has submitted a request to the Financial Intelligence Centre for clarification regarding the differences between rules applicable to domestic and cross-border crypto-asset transfers. This guidance will be updated upon receipt of the regulator's response.


There is a difference.


CASPs and ICASPs must take reasonable measures to identify cross-border crypto-asset transfers that lack the required information. Additionally, they must develop, document, maintain and implement effective risk-based policies and procedures for determining:

  • (i) when to execute, suspend execution of, or return a cross-border crypto-asset transfer that lacks any of the required information; and
  • (ii) the appropriate follow-up action that they will take in each instance where they execute, suspend execution of, or return a cross-border crypto-asset transfer.

Batch file transfer

Sumsub has submitted a request to the Financial Intelligence Centre seeking clarification as to which information shall be contained within the batch file and which shall be contained within each individual transfer. This guidance shall be updated upon receipt of the regulator's response.


Ordering and intermediary CASPs may transmit the required information in batches; however, the Directive does not specify any particular requirements.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted simultaneously with the transfer itself and in a secure manner. Post facto transmission of the required information is not permitted.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence;
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 25, 2022.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value of KRW 1,000,000 or more.

Data to be shared

Originator:

  • a) Full name (or name of the corporation or organisation and the name of the representative);
  • b) Virtual asset addresses.

Beneficiary:

  • c) Full name (or name of the corporation or organisation and the name of the representative);
  • d) Virtual asset addresses.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

Information from the Section "Data to be shared" shall be provided together when transferring virtual assets.


In case of a request by the head of the Financial Intelligence Unit or the virtual asset business operator receiving the virtual asset, the resident registration number (in the case of a corporation, the corporate registration number) or passport number/alien registration number (only for foreigners) of the customer sending the virtual asset shall be provided within three business days from the date of request for information provision.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 30, 2024.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full official name;
  • b) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • c) Address and identification information: i) habitual residence, including country name; ii) official personal document number; iii) customer identification number, or date and place of birth.

Beneficiary:

  • d) Full official name;
  • e) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number.

Legal Entity


Originator:

  • f) Registered name;
  • g) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • h) Registered office address;
  • i) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Beneficiary:

  • j) Registered name;
  • k) Distributed ledger address and crypto-asset account number: If the transfer is registered on a DLT network, include the distributed ledger address and the crypto-asset account number if it exists and is used. If not registered on a DLT network, provide the crypto-asset account number;
  • l) Legal Entity Identifier (LEI) or equivalent identifier. The alternative identifier must: i) be a unique identification code for the legal entity; ii) be published in public registries; iii) be automatically issued upon entity formation by a public authority; iv) allow identification of name and address elements; v) be accompanied by a description of the identifier type in the messaging system.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of crypto-assets from a single originator, the obligation on the CASP of the originator to ensure that transfers of crypto-assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that the batch file contains the information on the originator and beneficiary, that that information has been verified, and that the individual transfers carry the distributed ledger address of the originator where this is applicable, the crypto-asset account number of the originator where this is applicable, or the unique transaction identifier where this is applicable.

Unhosted wallet verification

Required for transactions exceeding EUR 1,000.

VASP Due Diligence

When establishing a correspondent relationship with a CASP registered outside the EU.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner, and no later than the initiation of the blockchain transaction.

Record retention

5 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or self-hosted – is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from January 1, 2020.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all crypto-asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or transaction-related reference number);
  • c) Address (or date and place of birth, the client number or the national identity number of the client).

Beneficiary:

  • d) Full name;
  • e) Account number (or transaction-related reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

There is a difference.


Domestic. b), e), but other data should be provided within three days after request.


Cross-border. a), b), c), d), e).

Batch file transfer

No special provisions.

Unhosted wallet verification

Required.


The regulation does not provide for any exceptions for payments involving unregulated wallet providers.


As long as an CASP supervised by FINMA is not able to send and receive the information required in payment transactions, such transactions are only permitted from and to external wallets if these belong to one of the CASP's own customers. Their ownership of the external wallet must be proven using suitable technical means. Transactions between customers of the same CASP are permissible. A transfer from or to an external wallet belonging to a third party is only possible if, as for a client relationship, the supervised CASP has first verified the identity of the third party, established the identity of the beneficial owner and proven the third party's ownership of the external wallet using suitable technical means.


If the customer is conducting an exchange (fiat-to-virtual currency, virtual-to fiat currency, or virtual-to-virtual currency) and an external wallet is involved in the transaction, the customer's ownership of the external wallet must also be proven using suitable technical means. If such proof is not available, the above rules for payment transactions apply.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information must be transmitted with payment orders.

Record retention

10 years.

Obligations of the originating CASP

The originating CASP must:

  • obtain information about the originator and beneficiary from a client who initiated a crypto-asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • verify a self-hosted wallet to which the crypto-assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary CASP

The beneficiary CASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet (if necessary);
  • verify a self-hosted wallet from which the crypto-assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from a self-hosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating CASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary CASP

The intermediary CASP must:

  • receive information about the originator and beneficiary from the previous CASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or self-hosted - is used on the other end and, if it is a custodial one, establish which CASP controls the wallet;
  • verify a self-hosted wallet from which the crypto-assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary CASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Information on the wallet used;
  • c) One of the following information: number of official identity document; or address; or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Information on the wallet used.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Required.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from February 25, 2025.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full legal name;
  • b) Wallet address, or in the absence of a wallet address, the reference number related to the transaction;
  • c) At least one of the following identifying details: address; place and date of birth; customer number; national identification number; citizenship number; or tax identification number.

Beneficiary:

  • d) Full legal name;
  • e) Wallet address, or in the absence of a wallet address, the reference number related to the transaction.

Subject

Details

Threshold-based data

15,000 TL

  • < 15,000 TL: a), b), d), e). It is not necessary to verify the information on the originator and beneficiary.
  • ≥ 15,000 TL: a), b), c), d), e).

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement.


However, for crypto asset transfers to or from a wallet address that is not registered with any CASP, the CASP must obtain from the customer, who is a party to the respective transaction, a declaration containing at least one of the following identifying details about the owner of the self-hosted wallet: full legal name; address; place and date of birth; customer number; national identification number; citizenship number; or tax identification number.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

8 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 31, 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Person


Originator:

  • a) Full name;
  • b) Account number (or a unique transaction reference number);
  • c) Residential address, identification number, travel document, date and place of birth, or client identification number with the transferring financial institution, which shall refer to a record containing these data.

Beneficiary:

  • d) Full name;
  • e) Account number (or a unique transaction reference number).

Legal Entity


Originator:

  • f) Registered name;
  • g) Account number (or a unique transaction reference number);
  • h) Business address, identification number, or client identification number with the transferring financial institution, which shall refer to a record containing these data.

Beneficiary:

  • i) Refistered name;
  • j) Account number (or a unique transaction reference number).

Subject

Details

Threshold-based data

AED 3,500


Natural Person


Domestic:

  • < AED 3,500: a), b), c).*
  • ≥ AED 3,500: a), b), c).*

Cross-border:

  • < AED 3,500: a), b), c), d), e);*
  • ≥ AED 3,500: a), b), c), d), e).

* Please also see the Domestic vs cross-border transfers section.


Legal Entity


Domestic:

  • < AED 3,500: f), g), h).*
  • ≥ AED 3,500: f), g), h).*

Cross-border:

  • < AED 3,500: f), g), h), i), j);*
  • ≥ AED 3,500: f), g), h), i), j).

* Please also see the Domestic vs cross-border transfers section.

Domestic vs cross-border transfers

There is a difference.


Domestic: When the data is available to the beneficiary VASP through other means, the originator VASP is required to include the account number or the unique reference number of the transaction only (point ‘b’ in our table), provided that this number allows the tracking of transactions to the originator or the beneficiary. Moreover, the originating VASP must provide such data within three working days of receiving the request from the beneficiary VASP or the concerned authorities.


Cross-border: VASPs shall ensure that all international transfers that are less than the amount of AED 3,500 are accompanied by the data required, without the need to verify the validity of the referred data, unless there are doubts about the commission of the crime.

Batch file transfer

In the event that several individual cross-border transfers from a single originator are bundled in a batch file for transmission to beneficiaries, the batch file shall contain required and accurate originator information, and full beneficiary information, that is fully traceable within the beneficiary country; and the financial institution shall be required to include the originator’s account number or unique transaction reference number.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from December 21, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account where such an account is used to process the transaction or a unique transaction reference number if no originator account number exists;
  • c) Address, or national identity number, or travel document number, or customer identification number, or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number where such an account is used to process the transaction or a unique transaction reference number if no beneficiary account number exists.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

A VASP must ensure that for batch transfers:

  • a) it has verified the required originator information; and
  • b) the batch file contains the required beneficiary information for each beneficiary and that the information is fully traceable in the beneficiaries jurisdiction.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

6 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from June 3, 2024.

Regulation

DFSA Rulebook - Anti-Money Laundering, Counter-Terrorist Financing and Sanctions Module (AML):

  1. Section AML 9.3 Electronic fund transfers;
  2. Section AML 9.3A Additional requirements for Crypto Token transfers.

Cabinet Decision No. (10) of 2019

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or unique transaction reference number if no account number exists).
  • c) Any one of the following: address (it should be the address that was verified as part of the CDD procedure); or national identity number, such as an identity card number or passport number; or customer identification number; or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or unique transaction reference number if no account number exists).

Subject

Details

Threshold-based data

Please see the Domestic vs. cross-border transfers section.

Domestic vs cross-border transfers

There is a difference.


Domestic: a), b), c), or only b), provided that: i) those details will permit the transaction to be traced back to the originator and beneficiary; and ii) the ordering VASP must provide full originator information within three business days of a request from the beneficiary VASP or the DFSA, or immediately upon request from a law enforcement agency.


Cross-border:

  • ≤ USD 1,000: a), b), d), e);
  • > USD 1,000: a), b), c).

Batch file transfer

If several individual cross-border transfers from a single originator are bundled in a batch file for transmission, then, an ordering VASP must ensure that:

  • a) the batch file contains the originator information required;
  • b) it has verified the originator information; and
  • c) the batch file contains the beneficiary information required for each beneficiary and that information is fully traceable in the beneficiary's country.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Required if the total value of crypto tokens transferred is USD 1,000 or more.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from February 7, 2023.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value exceeding AED 3,500.

Data to be shared

Individual Person


Originator:

  • Full name;
  • Account number or virtual asset wallet address;
  • Residential address.

Beneficiary:

  • Full name;
  • Account number or virtual asset wallet address.

Legal Entity


Originator:

  • Registered name;
  • Account number or virtual asset wallet address;
  • Business address.

Beneficiary:

  • Registered name;
  • Account number or virtual asset wallet address.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the event that several individual cross-border wire transfers from a single originator are bundled in a batch file for transmission to beneficiaries, the batch file shall contain required and accurate originator information, and full beneficiary information, that is fully traceable within the beneficiary country; and the financial institution shall be required to include the originator’s account number or unique transaction reference number.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

Prior to entering into any transaction with a counterparty VASP or VASP in any other jurisdiction, VASPs must complete risk-based due diligence on such counterparty in order to mitigate AML/CFT risks.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

8 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • conduct VASP Due Diligence (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet - custodial or unhosted - is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct VASP Due Diligence (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from September 1, 2023.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Natural Persons


Originator:

  • a) Full name;
  • b) The account number (or unique transaction identifier if there is no account number);
  • c) One of the following: customer identification number; or address; or birth certificate number, passport number or national identity card number (or individual's date and place of birth).

Beneficiary:

  • d) Full name;
  • e) The account number (or unique transaction identifier if there is no account number).

Legal Entities


Originator:

  • f) The registered name (or trading name if no registered name);
  • g) The account number (or unique transaction identifier if there is no account number);
  • h) One of the following: Customer identification number; or Address of originator's registered office (or principal place of business if none or different).

Beneficiary:

  • i) The registered name (or trading name if no registered name);
  • j) The account number (or unique transaction identifier if there is no account number).

Subject

Details

Threshold-based data

EUR 1,000

Cross-border:

  • < EUR 1,000: a), b), d), e);
  • ≥ EUR 1,000: a), b) c), d), e).

Domestic vs cross-border transfers

There is a difference.


Domestic


Natural Persons:


The following data should be transferred: a), b) c)*, d), e).


Legal Entities:


The following data should be transferred: f), g), h)*, i), j).


* As a general rule, it is not required. However, the VASP of the beneficiary may also request this information, which the VASP of the originator must provide within three working days.


Cross-border


Natural Persons:


The following data should be transferred:

  • < EUR 1,000: a), b), d), e);
  • ≥ EUR 1,000: a), b) c), d), e).

Legal Entities:


The following data should be transferred:

  • < EUR 1,000: f), g), i), j);
  • ≥ EUR 1,000: f), g), h), i), j).

Where a UK VASP does not know if the counterparty (including any intermediaries) is a UK VASP, it may treat the transaction as a cross border transaction.

Batch file transfer

Where the VASP of the beneficiary is carrying on business wholly outside the UK information on the batch must be submitted securely and simultaneously with the transfer. A batch file transfer is a bundle of individual inter-cryptoasset business transfers from a single originator. The TR applies to each of the underlying transfers forming the bundle. The information must be verified by the VASP of the originator on the basis of reliability and independence.

Unhosted wallet verification

Where a VASP has determined that information should be requested, it should take reasonable steps to obtain the information from its own customer. In higher risk cases, firms should consider taking further steps to ascertain the source of funds in the unhosted wallet and thereafter consider authorising the transfer only if the control over the unhosted wallet can be reasonably established through appropriate solutions (e.g. micro deposit or cryptographic signature).

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet to which the assets should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • verify an unhosted wallet from which the assets were received (if applicable);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • verify an unhosted wallet from which the assets were received or to which they should be sent (if applicable);
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from March 18, 2013.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to transmittals of funds with an equivalent value of $3,000 or more.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number;
  • c) Address;
  • d) Amount of the transmittal order;
  • e) Execution date of the transmittal order.

Beneficiary:

  • f) Identity of the financial institution;
  • g) Full name and address;
  • h) Account number;
  • i) Any other specific identifier.

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The money transmitter must obtain or provide the required regulatory information either before or at the time of the transmittal of value, regardless of how a money transmitter sets up their system for clearing and settling transactions, including those involving CVC.

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

Not in force. Shall come into force on a date to be determined.

Regulation

Further information will be provided once the regulator releases additional details.

Regulatory body

Threshold

Data to be shared

Subject

Details

Threshold-based data

Further information will be provided once the regulator releases additional details.

Domestic vs cross-border transfers

Batch file transfer

Unhosted wallet verification

VASP Due Diligence

Time and way to share the Information

Record retention

Further information will be provided once the regulator releases additional details.

Subject

Details

Status

In force from July 20, 2021.

Regulation

Regulatory body

Threshold

The Travel Rule applies only to virtual asset transfers with an equivalent value exceeding EUR 1,000.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number or virtual wallet (or a unique reference number);
  • c) Address or national identity number or the client's identification number or the date and place of his birth.

Beneficiary:

  • d) Full name;
  • e) Account number or virtual wallet (or a unique reference number).

Subject

Details

Threshold-based data

Domestic vs cross-border transfers

No difference.

Batch file transfer

No special provisions.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted immediately and in a secure manner

Record retention

5 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Subject

Details

Status

In force from 19 August 2022.

Regulation

Regulatory body

Threshold

No threshold. The Travel Rule applies to all virtual asset transfers irrespective of value.

Data to be shared

Originator:

  • a) Full name;
  • b) Account number (or unique transaction reference number);
  • c) Address, driving licence, passport or national identification document bearing the originator's pictorial image and evidencing the originator's identity or the originator's customer idetification number or date and place of birth.

Beneficiary:

  • d) Full name;
  • e) Account number (or unique transaction reference number).

Subject

Details

Threshold-based data

USD 1,000

  • < USD 1,000: a), b), d), e). It is not necessary to verify the information on the originator and beneficiary unless there is a suspicion of money laundering, terrorist financing, or proliferation financing.
  • ≥ USD 1,000: a), b), c), d), e).

Domestic vs cross-border transfers

No difference.

Batch file transfer

In the case of a batch file transfer of virtual assets from a single originator, the obligation on the VASP of the originator to ensure that transfers of virtual assets are accompanied by the required information shall not apply to the individual transfers bundled together therein, provided that:

  • a) the batch file contains: (i) the name of the originator; (ii) where an account is used to process the transfer of virtual assets by the originator, the account number of the originator; or (iii) the address of the originator, the number of an issued government document evidencing the originator’s identity or the originator’s customer identification number or date and place of birth; and
  • b) the individual transfers of virtual assets carry the account number of the originator or a unique reference number.

Unhosted wallet verification

No requirement. May be applied based on risk assessment.

VASP Due Diligence

No requirement.

Time and way to share the Information

The required information shall be transmitted simultaneously or concurrently with the transfer of virtual assets.

Record retention

10 years.

Obligations of the originating VASP

The originating VASP must:

  • obtain information about the originator and beneficiary from a client who initiated a virtual asset transfer;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the originator by comparing it with the information gathered during the KYC or KYB;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the beneficiary VASP

The beneficiary VASP must:

  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet (if necessary);
  • receive information about the originator and beneficiary from the originating or intermediary VASP (or obtain it directly from its customer if assets are received from an unhosted wallet) and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • verify information about the beneficiary by comparing it with the information gathered during the KYC or KYB;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified; and
  • keep records related to the transfer for as long as required by national legislation.

Obligations of the intermediary VASP

The intermediary VASP must:

  • receive information about the originator and beneficiary from the previous VASP in the chain and ensure that the received information is complete by comparing it with the requirements in the originating VASP's jurisdiction;
  • in accordance with the targeted financial sanctions regime, conduct AML screening against both the originator and beneficiary;
  • carry out wallet attribution to establish which type of wallet – custodial or unhosted – is used on the other end and, if it is a custodial one, establish which VASP controls the wallet;
  • conduct transaction monitoring and report to the FIU if a suspicious transaction is identified;
  • transmit information about the originator and beneficiary to the beneficiary or intermediary VASP; and
  • keep records related to the transfer for as long as required by national legislation.

travel rule requirements canada