Skip to main content
Bitstamp requires Travel Rule piiData for withdrawals and deposits. Its requirements do not depend on jurisdiction: the same fields apply to withdrawals and deposits, first party and third party. For how to build, encrypt, and send the payload, see Exchanges.

Required fields

In each path, {party} is beneficiary for withdrawals and originator for deposits.

Identify the counterparty VASP

Identify the counterparty VASP by its Bitstamp VASP ID, a UUID, in beneficiaryVASP.vaspCode for withdrawals or originatingVASP.vaspCode for deposits. Bitstamp publishes the full list of VASPs it supports through its VASP list endpoint.

Example

On the Help Center

To provide Bitstamp Travel Rule data in the Console, see Bitstamp travel rule.