Skip to main content
Binance requires Travel Rule piiData for withdrawals and deposits. Its requirements depend on the jurisdiction of your Binance entity, and on whether the counterparty wallet is private or at another VASP. For how to build, encrypt, and send the payload, see Exchanges.
  • Withdrawals: send your jurisdiction as originatingVASP.vaspCountry. When the destination is at another VASP, identify it in beneficiaryVASP. For a private wallet, omit beneficiaryVASP.
  • Deposits: send your jurisdiction as beneficiaryVASP.vaspCountry. When the funds come from another VASP, identify it with originatingVASP.vaspName. For a private wallet, omit originatingVASP.
Supported jurisdictions: Australia (AU), Bahrain (BH), France (FR), India (IN), Japan (JP), Kazakhstan (KZ), New Zealand (NZ, withdrawals only), Poland (PL), South Africa (ZA), and the United Arab Emirates (AE).

Withdrawals

“Outside JP” means AU, BH, FR, IN, KZ, NZ, PL, ZA, and AE.

Deposits

Japanese names

In Japan, names use three scripts, for businesses as well as individuals:

Examples

First-party withdrawal to a private wallet (France)

Third-party withdrawal to another VASP (France)

A withdrawal from a Binance account, by an individual in France, to a third-party beneficiary. Before encryption:
After encrypting every value in data, add it to the transaction:

Third-party withdrawal to another VASP (Australia)

Third-party deposit from a private wallet (India)

On the Help Center

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