Link VASP customer information to transaction

Associates a customer-information record with an on-chain txHash for a given VASP counterparty. Used after create to attach originator PII to a Travel Rule–held incoming deposit (often after widget session create with txHash).

Re-posting the same vaspCustomerInformationId and txHash for the same counterparty is idempotent. Linking a different record to an already-linked txHash returns 409.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
uuid

Consumer account owner ID. Send userId or businessId (at least one required on HMAC calls). If both are sent, userId is used.

uuid

Business (KYB) account owner ID. Send userId or businessId (at least one required on HMAC calls). If both are sent, userId is used.

uuid
required

Record id from POST /counterparty/vasp/customer-information.

string
required

On-chain transaction hash to associate with this record. Re-linking the same txHash and counterpartyId with the same record is idempotent; a different record returns 409.

Responses

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