Submit Travel Rule information for a crypto deposit

Submits originator (sender) Travel Rule information for a crypto deposit held for compliance review. Forwards the collected data and optional wallet screenshot to the Travel Rule service, which decides whether the compliance hold is released. Returns the resulting submission status.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The unique identifier of the crypto deposit

Body Params

Travel Rule submission payload: sender type, wallet type, and conditionally CASP DID, sender PII, source address, and a base64-encoded wallet screenshot.

string
enum
required

Whether the deposit originates from the customer's own wallet (me_to_me) or a third party (you_to_me).

Allowed:
string
enum
required

Whether the source wallet is hosted by an exchange/CASP or self-custodied.

Allowed:
string

Decentralized identifier of the originating CASP. Applicable when wallet_type is exchange.

string

On-chain source address of the deposit. Applicable when wallet_type is self_custody.

sender_pii
object

Personally identifiable information of the sender. Applicable when sender_type is you_to_me.

string

Base64-encoded wallet screenshot. Required by the Travel Rule service above a jurisdictional notional threshold for self-custody deposits.

string

MIME type of the screenshot. Required when screenshot is provided.

Headers
string
required

HMAC-SHA256 signature of the request, base64-encoded. See the Authentication guide for the exact signing formula.

string
required

Current Unix timestamp in seconds. Must be within 60 seconds of server time or the request is rejected.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json