Skip to main content
The Travel Rule requires Virtual Asset Service Providers (VASPs) to share originator and beneficiary information for cryptocurrency transfers above certain thresholds. This regulatory requirement, mandated by frameworks like FATF and MiCA, helps prevent money laundering and terrorist financing. WhiteBIT provides API endpoints for Travel Rule compliance, enabling B2B clients to submit required data for deposits and withdrawals.

When Travel Rule applies

Travel Rule verification is required when:
  • The transaction involves cryptocurrency deposits or withdrawals
  • The account is registered in the European Economic Area (EEA)
  • The transaction meets regional threshold requirements
  • The Travel Rule API is enabled for the account
The Travel Rule API is not available to all accounts. To request access, contact the assigned Account Manager or email institutional@whitebit.com.

Wallet types


Party types


VASP identification

When the destination or originating wallet is hosted:
  • VASP in list — Use vaspId from the Get VASPs endpoint response
  • VASP not in list — Use vaspName with the VASP’s name as a string fallback

Country codes

All country fields use ISO 3166-1 alpha-3 codes (3-letter):

Deposit verification

Flow

Verification is performed against the originator (sender) address the deposit came from, not the generated deposit address. Status 28 means the submitted data is under review; it resolves either to a successful credit or to a rejection. A rejected deposit is canceled rather than refunded automatically. To return the funds, submit a separate refund request via Refund deposit (POST /api/v4/main-account/refund-deposit). Deposits canceled under Travel Rule are eligible for refund.

Deposit examples

Individual from hosted wallet (VASP in list):
Entity from hosted wallet (VASP not in list):
Individual from unhosted wallet:

Withdrawal with Travel Rule

Flow

Withdrawal examples

Individual to hosted wallet (VASP in list):
Entity to hosted wallet (VASP not in list):
Individual to unhosted wallet:

Legacy format (withdrawals only)

The API still accepts the legacy flat format for withdrawals, but it will not pass Travel Rule verification. To complete Travel Rule compliance, use the new structured format.
Field mapping: Legacy format example (won’t pass verification):

What’s next

Get available VASPs

Retrieve the list of VASPs for travel rule submissions.

Submit deposit verification

Submit originator data for a deposit pending verification.

Create withdraw request

Create withdrawals with travel rule data.

EEA definition

European Economic Area countries where Travel Rule applies.