Travel Rule information should be completed by an authorised user or process within your organisation.
The appropriate person or team depends on your organisation’s operating model, internal controls, compliance responsibilities, and BE Custody configuration. In many organisations, this may involve operations, compliance, treasury, or another authorised function.
Why ownership matters
Travel Rule information may be required before an in-scope transfer can proceed.
The information provided should be accurate, complete, and consistent with your organisation’s internal records. Incorrect or incomplete information may delay the transfer, require additional review, or prevent the transfer from progressing.
Which teams may be involved?
Depending on your organisation’s setup, Travel Rule workflows may involve:
- Operations teams
- Compliance teams
- Treasury teams
- Authorised Signers
- Administrators
- Client operations or customer-facing teams
- API or integration teams, where Travel Rule information is submitted programmatically
The exact ownership should be defined by your organisation’s internal process.
What should the responsible user check?
Before submitting Travel Rule information, the responsible user should check:
- The transfer is expected and authorised
- The asset, network, amount, wallet, and address are correct
- The originator information is accurate, where required
- The beneficiary information is accurate, where required
- Counterparty information is complete, where required
- The information matches internal records
- Any required internal compliance or operations review has been completed
- The information is being submitted through the approved BE Custody workflow or integration
Do not submit placeholder, incomplete, or uncertain information unless this is explicitly permitted by your organisation’s compliance process.
What if responsibilities are unclear?
If it is unclear who should complete Travel Rule information, do not submit uncertain information.
Escalate internally to the appropriate operations, compliance, treasury, or governance contact. Your organisation should define who is authorised to complete, review, and approve Travel Rule information for relevant transfers.
Can Travel Rule information be submitted through an API?
Where supported and configured, Travel Rule information may be submitted through approved API or integration workflows.
Organisations using API-based workflows should ensure that responsibility for data quality, validation, error handling, and reconciliation is clearly defined internally.
API credentials and integration details should be protected and managed according to the organisation’s security process.
What should I do if information is missing?
If required Travel Rule information is missing, check with the appropriate internal team before continuing.
If further support is required, contact Bitpanda Enterprise Custody Support through the approved support channel and include the relevant transfer details.
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in a support request.