Submit deposit verification
Submit originator information for a deposit pending travel rule verification via the V4 API.
Overview
When a deposit is detected as Travel Rule-eligible, it enters a “ready for verification” state. 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
vaspId if the originating VASP is in the list, otherwise use vaspName.Verification status
After successful submission, the response contains astatus field:
Common errors
Missing VASP for hosted wallet: WhenwalletType is "hosted", provide either vaspId or vaspName.
Related
- Get available VASPs — Fetch VASPs list before submission
- Travel Rule — Detailed requirements and workflows
Authorizations
The public WhiteBIT API key.
Base64-encoded JSON request body.
HMAC-SHA512 signature of the payload, hex-encoded. Computed as hex(HMAC-SHA512(payload, api_secret)).
Body
Transaction external ID (from deposit/withdraw history)
100"550e8400-e29b-41d4-a716-446655440000"
Wallet type:
hosted- VASP-hosted wallet (exchange, custodian). RequiresvaspDataobject.unhosted- Self-custody wallet (hardware wallet, software wallet).
hosted, unhosted "hosted"
Originator information for travel rule compliance
Request signature
"{{request}}"
Unique request identifier
1594297865000
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).
Response
Successful submission