v1

latestOpenAPI 3.0.22026-07-26123510445.2 KB
Travel Rule

Submit Deposit Sender Travel Rule

Submit the originator (sender) Travel Rule data for an incoming deposit. Call this when a deposit notification arrives with need_travel_rule=true; once accepted, that deposit and later deposits from the same source address can proceed. Deposit-sender entries are kept separately from the withdrawal address book — query them with address_kind=deposit_sender. Calling again with the same source_address and network updates the existing entry. Stablecoin Account API Publisher Disclaimer

post/v1/ramp/wallet_address/deposit-sender

Headers

x-on-behalf-ofstring

Specifies the sub-account on whose behalf the request is made. This should be set to the account_id, which can be retrieved via the List Connected Accounts API. If omitted or empty, the request is executed using the master account. More information at Connected Accounts.

x-idempotency-keystring uuid

A unique identifier (UUID) used to maintain operation idempotency, ensuring that repeated executions of the same operation do not result in unintended effects or duplication. It helps preserve data consistency in the face of network errors, retries, or failures.

Request body

source_addressstring required

Deposit source address. Use the from_address from the deposit notification; it must match that deposit.

networkstring required

Network of the deposit. Use the network from the deposit notification.

Example request

{
  "source_address": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7",
  "network": "TRX",
  "meta_data": {
    "wallet_type": "hosted",
    "address_party": "third_party",
    "beneficiary_information": {
      "entity_type": "individual",
      "first_name": "John",
      "last_name": "Doe",
      "company_name": "Acme Pte Ltd",
      "country": "sg",
      "city": "Singapore",
      "vasp_id": "I1QNLP",
      "vasp_name": "Binance"
    }
  }
}

Response

Deposit sender Travel Rule accepted

codeinteger required
messagestring required
{"stackTrail":"components:schemas:DepositSenderResponse:properties:data","oasType":"schema","type":"unknown","description":"Always `null`; a successful response means the submission was accepted.","example":null,"nullable":true}

Example response

{
  "code": 200,
  "message": "Success"
}