What happens if Travel Rule information is missing?

If required Travel Rule information is missing, incomplete, or cannot be validated, the related transfer may be delayed, restricted, rejected, or require further review.

Travel Rule requirements are designed to ensure that certain information about the originator and beneficiary is available for in-scope transfers. The exact information required and the workflow shown in BE Custody may depend on the transfer type, jurisdictional requirements, counterparty, and your organisation’s configuration.

Why Travel Rule information matters

Travel Rule information supports compliance checks for in-scope digital asset transfers.

Depending on the transfer, information may be required about:

  • The originator
  • The beneficiary
  • The sending or receiving entity
  • The destination wallet or address
  • The counterparty virtual asset service provider, where applicable
  • The purpose or context of the transfer, where required

Missing or incorrect information can prevent the transfer from progressing through the expected workflow.

What may happen if information is missing?

If required information is missing, BE Custody may require additional information before the transfer can proceed.

Depending on the workflow and transfer status, the transfer may:

  • Remain pending
  • Require completion of additional fields
  • Require review by an authorised user
  • Require internal compliance review
  • Be delayed while information is checked
  • Be rejected or cancelled if the required information cannot be provided

The exact outcome depends on the transfer, configuration, and applicable compliance requirements.

What should users check?

Before submitting Travel Rule information, check that:

  • The beneficiary or originator details are accurate
  • The counterparty information is complete, where required
  • The wallet or address information matches the transfer
  • The asset, network, and amount are correct
  • The information matches the organisation’s internal records
  • Any required internal compliance process has been followed

Do not submit information if you are unsure whether it is accurate.

What if the information is incorrect?

If information has been entered incorrectly, follow your organisation’s internal process or contact Bitpanda Enterprise Custody Support through the approved support channel.

Do not attempt to bypass required Travel Rule fields or provide placeholder information unless this is explicitly permitted by your organisation’s compliance process.

Who is responsible for providing the information?

Your organisation is responsible for ensuring that required Travel Rule information is accurate and provided by an authorised user or process.

The person completing the information may vary depending on your organisation’s operating model. It may involve operations, compliance, treasury, or another authorised team.

What should I do if I am unsure?

If you are unsure what information is required, do not submit incomplete or uncertain information.

Check with your organisation’s compliance or operations team. If further support is required, contact Bitpanda Enterprise Custody Support through the approved support channel.

Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in a support request.

Was this article helpful?
0 out of 0 found this helpful