A Comprehensive Guide to Implementing the Travel Rule for Secure Financial Transactions
The Travel Rule is a regulatory requirement designed to enhance transparency and security in financial transactions. This rule benefits consumers and merchants by:
- Preventing fraud and unauthorized transactions
- Enhancing security through proper verification
- Ensuring compliance with current financial regulations
- Protecting both merchants and customers during financial exchanges
Integration Options
- New merchants can easily integrate with our Travel Rule full set APIs by downloading our updated Postman Collection. The collection is available in Postman API repository. It contains all necessary request parameters and examples to quickly implement compliant transactions.
- Existing Merchants simply require adding a few additional fields related to end user information at the payment (deposit) and payout (withdrawal) levels. Endpoints are not subject to change.
- Applicability: the Travel Rule applies to all chosen integration methods: Rapid Integration, Invoice, Hosted Payment Page (HPP), Embedded Payment Page (EPP), RBL Integration, payout APIs.
Implementation Examples HPP - Deposit Example
| Parameter | Value | Description |
|---|---|---|
externalId | "your-external-id" | Unique identifier for the transaction |
targetAmount | "100" | Amount of the transaction |
currency | "USDT" | Currency code for the transaction |
mainCurrency | "TRX" | Main blockchain currency |
targetCurrency | "GBP" | Target currency for conversion |
returnUrl | "https://getorbital.com" | URL to return to after completion |
notifyUrl | "http://notify.com" | Webhook URL for notifications |
primaryColor | "#4097F6" | Primary UI color for HPP |
secondaryColor | "#4097F6" | Secondary UI color for HPP |
email | "[email protected]" | User's email address |
format | "json" | Response format |
firstName | "John" | User's first name (Travel Rule) |
lastName | "Doe" | User's last name (Travel Rule) |
streetName | "Main Street" | Street name (Travel Rule) |
townName | "London" | Town or city (Travel Rule) |
countryOfResidence | "GB" | Country code (Travel Rule) |
buildingNumber | "42" | Building number (Travel Rule) |
postcode | "E14 5AB" | Postal code (Travel Rule) |
identificationType | "nationalRegistration" | Type of ID (Travel Rule) |
documentCountryOfIssue | "IT" | Country issuing document (Travel Rule) |
documentNumber | "P123456789" | ID document number (Travel Rule) |
documentType | "ARNU" | Document type code (Travel Rule) |
customerId | "CUST12345678" | Customer ID (Travel Rule) |
OUTBOUND Transactions (Withdrawals/Payouts)
| Field Name | Value | Required |
|---|---|---|
| firstName | TEXT (max 100 characters) | yes |
| lastName | TEXT (max 100 characters) | yes |
Parameters Logic
INBOUND Transactions (Deposits/Payins)
Field Name | Value | Required |
|---|---|---|
firstName | TEXT (max 100 characters) | yes |
lastName | TEXT (max 100 characters) | yes |
streetName | TEXT (max 70 characters) | yes |
townName | TEXT (max 35 characters) | yes |
countryOfResidence | ISO-3166-1 alpha-2 codes or the value XX | yes |
buildingNumber | TEXT (max 16 characters) | yes |
postcode | TEXT (max 16 characters) | yes |
identificationType | nationalRegistration or placeOfBirth | yes |
documentCountryOfIssue | ISO-3166-1 alpha-2 codes or the value XX | when identificationType=nationalRegistration |
documentNumber | TEXT (max 35 characters) | when identificationType=nationalRegistration |
documentType | Types accepted ARNU Alien registration number CCPT Passport number RAID Registration authority identifier DRLC Driver license number FIIN Foreign investment identity number TXID Tax identification number SOCS Social security number IDCD Identity card number LEIX Legal Entity Identifier | whenidentificationType=nationalRegistration |
customerId | TEXT (max 50 characters) | whenidentificationType=nationalRegistration |
dateOfBirth | TEXT (YYYY-MM-DD) | when identificationType=placeOfBirth |
placeOfBirth | TEXT (max 70 characters) | when identificationType=placeOfBirth |
Based on the above chart, If a customer paying-in, is a Natural Person, Orbital will require:
- First Name and Last Name
- Full Address (Country, Postal Code, Town/City, Street Name, House Number)
- National ID Number (e.g. Passport no) AND Customer Identification Number (Internal ID for your customer) OR
- Date and Place of Birth
OR
If your customer paying-in, is a Business, Orbital will require:
- Registered/Trading Name
- Registered or official office address (Country, Postal Code, Town/City, Street Name, Building Number)
- Legal Entity Identifier (LEI) or Company Identifier
Best Practices
- Always validate user input before submission to ensure all required fields are present
- Use standardized formats for country codes (ISO-3166-1 alpha-2)
- We've implemented proper error handling for cases where Travel Rule data is incomplete
- We do ensure that all data are transmitted securely and in compliance with data protection regulations
Support
- For additional support or questions regarding Travel Rule implementation, please contact your Relationship Manager and Integration teams.