Travel Rule compliance

Stablecoin Account API Publisher Disclaimer The FATF Travel Rule requires identifying the counterparty of a crypto transfer in certain cases. In the Stablecoin Account API, that information travels in one object — meta_data — used in three places:

Create Address Book and Update Address Book — describing the beneficiary of a withdrawal destination.
Submit Deposit Sender Travel Rule — describing the originator of an incoming deposit.

When `meta_data` is required

meta_data is optional at the API level, but must be provided (and pass validation) when any of these apply:

Scenario	Why
The address belongs to a third party (`address_party: third_party`)	Beneficiary identity is required
The wallet is hosted by an exchange (`wallet_type: hosted`)	The custodian VASP must be identified
The address is a Binance-routed withdrawal destination	The withdrawal is rejected until the address book entry carries Travel Rule data (error: `missing travel_rule_data for binance withdraw`)
A deposit arrives with `need_travel_rule: true`	The deposit is held until originator data is submitted

Once you provide meta_data, its fields are validated — a provided-but-invalid object fails the request.

Field reference

Top level — both fields are required whenever meta_data is present:

Field	Type	Values	Description
`wallet_type`	string	`hosted`, `unhosted`	`hosted` for a custodial/exchange wallet (requires VASP details); `unhosted` for a self-custody wallet
`address_party`	string	`first_party`, `third_party`	`first_party` when the address belongs to the account holder; `third_party` when it belongs to another beneficiary
`beneficiary_information`	object	—	Required when `address_party` is `third_party` or `wallet_type` is `hosted`

Inside beneficiary_information, requirements depend on the entity and wallet type:

Field	Required when	Description
`entity_type`	Third party	`individual` or `corporation`
`first_name`, `last_name`	Third party and `entity_type: individual`	Beneficiary given and family name
`company_name`	Third party and `entity_type: corporation`	Beneficiary company name
`country`	Third party	ISO 3166-1 alpha-2, lowercase — use a `countryCode` from List Countries
`city`	Third party	Use a `regionName` from List Regions
`vasp_id`	Hosted wallet (at least one of `vasp_id` / `vasp_name`)	Use an `identifier` from List VASPs
`vasp_name`	Hosted wallet	The VASP’s name. If the exchange is not in the VASP list, put its name here and omit `vasp_id`
`id_type`, `id_primary`	Optional	Beneficiary identity document type and number

Typical validation errors: invalid wallet_type, invalid address_party, invalid entity_type, individual third party requires first_name and last_name, corporation third party requires company_name, third party requires country and city, hosted wallet requires vasp_id or vasp_name.

Examples

An individual third-party beneficiary at an exchange (hosted):

{
  "wallet_type": "hosted",
  "address_party": "third_party",
  "beneficiary_information": {
    "entity_type": "individual",
    "first_name": "John",
    "last_name": "Doe",
    "country": "sg",
    "city": "Singapore",
    "vasp_id": "I1QNLP",
    "vasp_name": "Binance"
  }
}

A corporate third party using a self-custody wallet (unhosted):

{
  "wallet_type": "unhosted",
  "address_party": "third_party",
  "beneficiary_information": {
    "entity_type": "corporation",
    "company_name": "Acme Pte Ltd",
    "country": "sg",
    "city": "Singapore"
  }
}

The account holder’s own self-custody wallet — beneficiary information can be omitted:

{
  "wallet_type": "unhosted",
  "address_party": "first_party"
}

Look up reference data

Three read-only endpoints supply the values that beneficiary_information fields must come from:

Address book — where withdrawal-side meta_data lives
Travel Rule for deposits — the originator-side flow
Send withdrawals
List VASPs API

Getting Started

Assets & Balances

Deposits

Withdrawals

Conversions & Transfers

Reference

When `meta_data` is required

Field reference

Examples

Look up reference data

​When meta_data is required

​Field reference

​Examples

​Look up reference data

​Related

When `meta_data` is required

Field reference

Examples

Look up reference data

Related