PII Data Handling

Travel Rule messages carry personally identifiable information (PII) about the originator and the beneficiary — names, addresses, national identifiers, dates and places of birth. Whether you see that data depends on the transaction's direction.

OUTGOING Transactions

• The destination wallet belongs to the receiving VASP. Confirming it means the receiving VASP has acknowledged ownership of the custodial wallet.
• PII is always included for you as the originating VASP.

INCOMING Transactions

INCOMING payloads only include the full originator and beneficiary PII once the destination wallet is confirmed.

Destination wallet	What is visible
Confirmed	The full originator and beneficiary data.
Not confirmed	PII is excluded. Only the party type and high-level transaction information are visible.

Example

An INCOMING transaction whose destination wallet is not confirmed returns the parties without their personal data:

transaction-pii-excluded

{
  "direction": "INCOMING",
  "asset": "BTC",
  "amount": 0.875,
  "status": "PENDING",
  "originator": {
    "type": "NATURAL"
  },
  "beneficiary": {
    "type": "NATURAL"
  }
}

The same transaction with a confirmed destination wallet returns the full originator and beneficiary objects, as described in Transactions.

Wallet Confirmation

Wallets registered through Create Wallet are created as confirmed automatically.

tip

For INCOMING transactions, register your customers' deposit addresses as wallets before you expect Travel Rule messages to them, so the originator's data is available for your compliance review.