BEFORE YOU BEGIN
- EU transfer-information rules have applied since 30 December 2024.
- The EUR 1,000 self-hosted-address threshold is not a general exemption.
- Keep personal information in the provider’s secure data channel.
Think about the information route
Regulation (EU) 2023/1113 sets information requirements for in-scope crypto-asset transfers involving service providers. The EBA’s Travel Rule guidelines explain how providers detect missing information and handle transfers that do not contain what is required. They apply from 30 December 2024.
For an operations team, the task begins before the wallet transaction. Establish who the originator and beneficiary are, whether each is a company or an individual, and which provider receives the supporting information. Use the company’s exact legal name consistently across the account, instructions and records.
A self-hosted address changes the workflow
Transfers involving a self-hosted address are not automatically outside the framework. For specified transfers exceeding EUR 1,000, the regulation requires measures to assess ownership or control of the address. This threshold does not make smaller in-scope transfers anonymous or remove the broader information requirements.
Ask the provider which evidence it accepts and who must supply it. Do not invent a universal proof-of-wallet procedure: requirements and implementation can differ with the direction of the transfer and the assessed risk. Never disclose private keys or a seed phrase as evidence of control.
Prepare one transfer record
Use an internal record that connects the business purpose, authorised sender, beneficiary, asset, network, amount and destination. Record the relevant provider reference and the date information was submitted. This is an operational control, not a claim that every field appears in every statutory message.
- Confirm whether the destination is an account at a provider or a self-hosted address.
- Resolve legal-name mismatches before initiating a material transfer.
- Use the requested secure channel for personal and company information.
- Retain the transfer identifier and any exception correspondence.
Treat an exception as a case
If the provider requests more information, preserve the exact request and ask which element is missing. Avoid retrying the transaction through another route merely to bypass the review. The same unresolved question can reappear at the next provider.
Keep personal data out of public transaction notes and internal documents with unnecessary access. Agree who may view the record and how it is retained. The useful outcome is a complete, consistent explanation that accompanies the movement of value, not a large file of unrelated identity documents.
Read the source in context. Provider policies, eligibility and national implementation can change. This field note explains an operating framework, not an account approval or individual legal opinion.
Back to all field notes