Crypto Deposits

This module contains endpoints for managing cryptocurrency deposits, including updating travel rule information.

Core endpoints

Update Travel Rule

Update or add the required Travel Rule information for a specific transaction.

Typical Workflow

The following outlines the process for handling a deposit that requires Travel Rule compliance:

Deposit Received: A cryptocurrency deposit is credited to a user's account on the platform.

Webhook Notification: If the deposit is subject to Travel Rule regulations, the partner will receive a Crypto Deposit Webhook (/crypto-deposit-webhook) with status WAITING_FOR_TR_DATA. This webhook notifies the partner that additional compliance information is required for the deposit. See LINK TO WEBHOOK CRYPTODEPOSIT for full details.

Example webhook payload:

{
  "externalUserId": "8bdd8c8a-e9b7-475e-9690-8a34e8b78dab",
  "cryptoDepositId": "facc5951-bdc8-46bc-a01c-9b36f25be6af",
  "amount": 0.001,
  "currency": "eth",
  "status": "WAITING_FOR_TR_DATA",
  "transactionHash": "0x10d5bd4367fd6623a16f56889abb3bb2352b8ea7df7b21537f1fc56fc2d07a87",
  "createdAt": "2025-03-20T11:34:37.646Z"
}

Data Submission: The partner is required to call the Update Travel Rule endpoint to submit the necessary compliance data for the specified deposit.

Verification and Final Processing: After the data is submitted, the deposit undergoes verification. Based on the verification outcome, the deposit is either released to the user's account or rejected.

Technical summary:

A crypto deposit is created (automatically or via another process).

If required, update travel rule information using Update Travel Rule.

Check the deposit status as needed.

Core endpoints#

Typical Workflow#

Core endpoints

Typical Workflow