curl --request POST \
  --url https://whitebit.com/api/v4/travel-rule/deposit/verification \
  --header 'Content-Type: application/json' \
  --header 'X-TXC-APIKEY: <api-key>' \
  --header 'X-TXC-PAYLOAD: <api-key>' \
  --header 'X-TXC-SIGNATURE: <api-key>' \
  --data '
{
  "uniqueId": "550e8400-e29b-41d4-a716-446655440000",
  "walletType": "hosted",
  "originator": {
    "type": "individual",
    "firstName": "Alice",
    "lastName": "Johnson",
    "residenceCountry": "NLD",
    "walletAddress": "0x9876543210fedcba9876543210fedcba98765432",
    "address": {
      "country": "NLD",
      "city": "Amsterdam",
      "addressLine1": "Damrak 1"
    }
  },
  "vaspData": {
    "vaspId": "vasp-002"
  },
  "request": "{{request}}",
  "nonce": 1594297865000
}
'

{
  "data": {
    "uniqueId": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted"
  }
}

Submit deposit verification

Submits originator information for a deposit in status 27 (Awaiting verification). While WhiteBIT reviews the submitted data, the deposit has status 28 (Confirmation in progress).

Wallet types:

hosted - VASP-hosted wallet (exchange, custodian). Requires vaspData object.
unhosted - Self-custody wallet (hardware wallet, software wallet). No VASP required.

Party types:

individual - Natural person. Requires firstName and lastName.
entity - Legal entity. Requires fullName.

This endpoint returns the region error shown in the 422 response and the common authentication errors.

Rate limit: 1000 requests/10 sec.

The API does not cache the response.

POST

api

travel-rule

deposit

verification

curl --request POST \
  --url https://whitebit.com/api/v4/travel-rule/deposit/verification \
  --header 'Content-Type: application/json' \
  --header 'X-TXC-APIKEY: <api-key>' \
  --header 'X-TXC-PAYLOAD: <api-key>' \
  --header 'X-TXC-SIGNATURE: <api-key>' \
  --data '
{
  "uniqueId": "550e8400-e29b-41d4-a716-446655440000",
  "walletType": "hosted",
  "originator": {
    "type": "individual",
    "firstName": "Alice",
    "lastName": "Johnson",
    "residenceCountry": "NLD",
    "walletAddress": "0x9876543210fedcba9876543210fedcba98765432",
    "address": {
      "country": "NLD",
      "city": "Amsterdam",
      "addressLine1": "Damrak 1"
    }
  },
  "vaspData": {
    "vaspId": "vasp-002"
  },
  "request": "{{request}}",
  "nonce": 1594297865000
}
'

{
  "data": {
    "uniqueId": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted"
  }
}

Overview

When a deposit is detected as Travel Rule-eligible, it enters status 27 (Awaiting verification). Use this endpoint to submit the required originator data. For detailed information about wallet types, party types, and field requirements, see Travel Rule.

Required fields by scenario

Scenario	`walletType`	`originator.type`	VASP	Name fields
Individual from exchange	`hosted`	`individual`	`vaspId` or `vaspName`	`firstName`, `lastName`
Entity from exchange	`hosted`	`entity`	`vaspId` or `vaspName`	`fullName`
Individual from self-custody	`unhosted`	`individual`	Not required	`firstName`, `lastName`
Entity from self-custody	`unhosted`	`entity`	Not required	`fullName`

Get the list of available VASPs via the Get VASPs endpoint. Use vaspId if the originating VASP is in the list, otherwise use vaspName.

Verification status

After successful submission, the response contains a status field:

Status	Description
`submitted`	Data submitted, awaiting compliance review
`approved`	Immediately approved (rare)

Monitor deposit status via deposit/withdraw history.

Common errors

Transaction Not Found: Ensure the uniqueId matches a transaction in the deposit history. The transaction must exist and belong to the authenticated account.

Missing VASP for hosted wallet: When walletType is "hosted", provide either vaspId or vaspName.

Get available VASPs — Fetch VASPs list before submission
Travel Rule — Detailed requirements and workflows

Used in these guides

On/Off-Ramp integration — corporate fiat ↔ crypto over EUR/SEPA rails.
On/Off-Ramp FAQ — originator-data submission for Travel Rule holds on inbound deposits.
Payment Integration — originator-data submission for deposits in Travel Rule status 27.

Authorizations

X-TXC-APIKEY

string

header

required

The public WhiteBIT API key.

X-TXC-PAYLOAD

string

header

required

Base64-encoded JSON request body.

X-TXC-SIGNATURE

string

header

required

HMAC-SHA512 signature of the payload, hex-encoded. Computed as hex(HMAC-SHA512(payload, api_secret)).

Body

application/json

uniqueId

string

required

Transaction external ID (from deposit/withdraw history)

Maximum string length: 100

Example:

"550e8400-e29b-41d4-a716-446655440000"

walletType

enum<string>

required

Wallet type:

hosted - VASP-hosted wallet (exchange, custodian). Requires vaspData object.
unhosted - Self-custody wallet (hardware wallet, software wallet).

Available options:

hosted,

unhosted

Example:

"hosted"

originator

object

required

Originator information for travel rule compliance

Show child attributes

request

string

required

Request signature

Example:

"{{request}}"

nonce

integer

required

Unique request identifier

Example:

1594297865000

vaspData

object

VASP (Virtual Asset Service Provider) information. Required when walletType is hosted. Provide either vaspId (if VASP is in the list from /travel-rule/vasps) or vaspName (if not in list).

Show child attributes

Response

Successful submission

data

object

Show child attributes

Getting Started

Market Data

Trading

Convert

Account & Wallet

Travel Rule

Sub-Accounts

Mining Pool

OAuth

Submit deposit verification

Overview

Required fields by scenario

Verification status

Common errors

Used in these guides

Authorizations

Body

Response

Getting Started

Market Data

Trading

Convert

Account & Wallet

Travel Rule

Sub-Accounts

Mining Pool

OAuth

​Overview

​Required fields by scenario

​Verification status

​Common errors

​Related

​Used in these guides

Authorizations

Body

Response

Overview

Required fields by scenario

Verification status

Common errors

Related

Used in these guides