Bitfinex Travel Rule

Bitfinex requires Travel Rule piiData for withdrawals only. For deposits, the sending VASP sends the originator data to Bitfinex directly. For how to build, encrypt, and send the payload, see Exchanges.

Required fields for withdrawals

Path	Values	Required when
`data.beneficiary.participantRelationshipType`	`FirstParty`, `ThirdParty`	Always
`data.beneficiary.entityType`	`Individual`, `Business`	Always
`data.beneficiary.names[0].primaryName`	Free text, with `nameType` `Latin`	`Individual`
`data.beneficiary.names[0].secondaryName`	Free text	`Individual`
`data.beneficiary.company.name`	Free text	`Business`
`data.beneficiary.postalAddress.streetName`	Free text	Always
`data.beneficiary.postalAddress.buildingNumber`	Free text	Always
`data.beneficiary.postalAddress.city`	Free text	Always
`data.beneficiary.postalAddress.postalCode`	Free text	Always
`data.beneficiary.postalAddress.country`	Free text	Always
`data.beneficiaryVASP.vaspCode`	Value from the Bitfinex VASP list	Always

Identify the counterparty VASP

Bitfinex publishes the full list of VASPs it supports through its VASP list endpoint.

On the Help Center

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

Get Started

Transactions

API Co-Signers

Workspace & Security

Webhooks

Direct Custody Wallets

Manage Wallets

Embedded Wallets

Canton

Gas Management

Treasury & Trading

Smart Contracts & Tokenization

Assets & NFTs

Identity & Compliance

Compliance Screening

Compliance Tooling

Payments

Offchain Signing

Key Link

Integrations

Required fields for withdrawals

Identify the counterparty VASP

On the Help Center

​Required fields for withdrawals

​Identify the counterparty VASP

​On the Help Center

Required fields for withdrawals

Identify the counterparty VASP

On the Help Center