For 3rd Party Deposits, Travel Rule information must be provided for each deposit account at the time of creation. Because each deposit account is tied to a single end customer, the merchant supplies the customer's identifying information upfront via the API when creating the account.

⚠️
Each deposit account must belong to one customer only. Do not share the same deposit address with multiple customers. Keep the address secure and only share it with the specific customer who will be using it.

Providing Travel Rule Information

Travel Rule data is submitted as part of the POST /v3/deposits/crypto/accounts request body, inside a customerProfile object. The merchant identifies whether the end customer is an individual or a company and provides the corresponding fields. Below are examples of how the customerProfile object can be filled in. Please note the required Travel Rule fields can vary by jurisdiction.

Individual Customer

{
  "type": "individual",
  "profileId": "customer-unique-id-123",
  "firstName": "Jane",
  "lastName": "Doe",
  "streetAddress": "Sheikh Zayed Road 1",
  "city": "Dubai",
  "country": "AE",
  "postalCode": "00000"
}

Individual profile fields:

Field	Type	Description
`profileId`	string	Your internal identifier for this customer. Use the same value for the same customer across all requests — Confirmo will recognise them and skip re-collection of TR data.
`customerEmailAddress`	string	Customer's email address. Used to send verification prompts if additional information is required.
`firstName`	string	Customer's first name.
`lastName`	string	Customer's last name.
`dateOfBirth`	string (ISO 8601)	Date of birth in `YYYY-MM-DD` format.
`placeOfBirth`	string	City or country of birth.
`country`	string (ISO 3166-1 alpha-2)	Two-letter country code (e.g. `CZ`, `US`, `GB`).
`city`	string	City of residence.
`postalCode`	string	Postal / ZIP code.
`streetAddress`	string	Street address including house number.

Company Customer

{
  "type": "company",
  "profileId": "company-unique-id-123",
  "registeredName": "Acme Corp",
  "registrationNumber": "12345678",
  "streetAddress": "Sheikh Zayed Road 1",
  "city": "Dubai",
  "country": "AE",
  "postalCode": "00000"
}

Company profile fields:

Field	Type	Description
`profileId`	string	Your internal identifier for this company. Reusing the same `profileId` for the same company avoids repeat verification.
`customerEmailAddress`	string	Contact email for the company. Used to send verification prompts if additional information is required.
`registeredName`	string	Registered legal name of the company.
`registrationNumber`	string	Company registration number.
`country`	string (ISO 3166-1 alpha-2)	Two-letter country code of registration.
`city`	string	City of registered address.
`postalCode`	string	Postal / ZIP code of registered address.
`streetAddress`	string	Street address of registered office.

The `profileId` and Repeat Customers

The profileId is your own identifier for a customer — it can be any string that uniquely identifies them in your system (e.g. a user ID or email address).

You can use a consistent profileId per customer across all API calls (invoices, payouts, deposits) to ensure a smooth experience and avoid duplicate verification prompts.

What Happens If Information Is Missing

If customerProfile is not provided, or if required fields are missing, the deposit account will not be created and you will get back an error message specifying the missing field.

Providing Travel Rule Information

Individual Customer

Company Customer

The profileId and Repeat Customers

What Happens If Information Is Missing

The `profileId` and Repeat Customers