After Travel Rule information is submitted in BE Custody, the transfer may continue through the relevant compliance, review, approval, and transaction workflow.
The exact workflow depends on the transfer type, the information provided, jurisdictional requirements, counterparty details, your organisation’s configuration, and any internal review process.
What happens next?
After submission, the transfer may:
- Continue to the next step in the BE Custody workflow
- Require additional review
- Require further information
- Be reviewed by an authorised internal team
- Be delayed while information is checked
- Be approved to proceed, where requirements are met
- Be rejected or cancelled, where required information cannot be provided or validated
The status shown in BE Custody should be reviewed together with your organisation’s internal process.
Does submitting information mean the transfer is complete?
No. Submitting Travel Rule information does not necessarily mean the transfer has been completed.
The transfer may still need to pass through additional steps, such as:
- Internal review
- Compliance checks
- Transaction approval
- Quorum approval
- Network submission
- Blockchain confirmation
Users should continue to monitor the transfer status and follow the relevant internal process.
What if more information is required?
If further information is required, complete it only if you are authorised to do so and the information is accurate.
Do not submit placeholder, incomplete, or uncertain information unless this is explicitly permitted by your organisation’s compliance process.
If you are unsure, escalate internally to the appropriate operations, compliance, treasury, or governance contact.
What if the transfer is delayed?
A delay may mean that the transfer requires additional information, validation, review, or approval.
Users should check:
- Whether all required Travel Rule fields have been completed
- Whether the information matches internal records
- Whether the transfer requires compliance review
- Whether any further action is required in BE Custody
- Whether the transfer has also completed the normal transaction approval workflow
If support is required, contact Bitpanda Enterprise Custody Support through the approved support channel.
What if the transfer is rejected or cancelled?
If a transfer is rejected or cancelled, do not automatically recreate the transfer.
First check the reason for the rejection or cancellation and follow your organisation’s internal process. Depending on the reason, the transfer may require corrected information, additional review, or a new instruction.
What information should I keep internally?
Your organisation should retain any records required by its internal policies and applicable compliance process.
This may include:
- The transfer instruction
- Originator or beneficiary information
- Counterparty details, where applicable
- Internal approvals or tickets
- Compliance review notes
- Relevant BE Custody status information
- Any support or escalation records
Follow your organisation’s internal retention and record-keeping requirements.
What should I do if I need support?
When contacting Bitpanda Enterprise Custody Support about a Travel Rule workflow, include:
- Your organisation name
- The relevant wallet or sub-wallet
- The asset and network
- The transfer amount
- The transfer status shown in BE Custody
- The approximate date and time
- Any relevant transfer or transaction reference
- A short description of the issue
- Any steps already taken
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in a support request.