Crypto Rules & Regulations

Overview

The Travel Rule concerns the identity information that must accompany certain transfers of crypto-assets. The sending and receiving parties may need to be identified before a transfer can be processed.

Your application collects the information requested for the selected route and submits it through the agreed integration. The responsible provider determines the applicable checks, information requirements and processing decision. Operators remain responsible for the obligations that apply to their own business.

Eligible transactions

Check the jurisdiction, provider, transaction value, customer location and payment route before moving funds. Currency alone does not determine the legal requirements. The following scenarios are a starting point for integration planning; the connected provider confirms the requirements for each flow.

Incoming and outgoing flows

• For incoming crypto, establish who sent the funds and whether the sending provider already supplies the required information.
• For deposits from a self-hosted wallet, collect the requested originator details and complete any required ownership checks.
• For outgoing crypto, including fiat-to-crypto payouts, establish the beneficiary and destination wallet before release.

Required information

The exact fields depend on the jurisdiction, provider and flow. Prepare accurate records for both sides of a transfer and only submit the personal data required by the applicable process.

Further information can include identity-document details, date and place of birth, business identifiers, or wallet-ownership evidence. Where an integration supports a same-customer flag, use it only when the party is the verified customer and the existing customer record is accurate.

Wallets & ownership

• Self-hosted / self-custodied: the customer controls the wallet. Obtain the ownership or control evidence required by the provider.
• Hosted / custodial: a service provider or operator holds or manages the wallet. Identify the custodian and the underlying customer.
• External provider or smart contract: determine the counterparty and how the connected provider classifies that destination; do not infer ownership from the address alone.

Sharing Travel Rule data

ATNM Digital Solutions connects your application to the relevant provider through the agreed Operator Services API integration. Field names, supported resources and submission endpoints depend on that integration and must be confirmed during onboarding.

Reusable route with fixed counterparties

If the provider supports storing Travel Rule details on a reusable resource, use that approach only when the same sender and recipient apply to every movement. Review and update the data whenever the parties change.

Data for an individual transaction

When counterparties vary, associate the information with the specific transfer or event using the provider’s supported process. Do not reuse one customer’s information for deposits or withdrawals belonging to someone else.

Submit data through the authenticated integration, protect access to personal information, and follow the provider’s retention and security requirements. Missing or inconsistent information may lead to a request for clarification, a hold or rejection.

Integration checklist

1. Identify the responsible licensed or registered provider and confirm the route is available for the customer.
2. Confirm jurisdiction, thresholds, required data and whether information is already transmitted by another provider.
3. Identify the originator and beneficiary, and reconcile their details with verified customer records.
4. Classify the wallets and complete the required ownership or control checks.
5. Choose reusable or transaction-specific submission, verify the provider response and resolve outstanding checks before funds are released.