Travel Rule
What the Travel Rule is, why it applies to crypto payments through BEEM, and what is changing for your integration.
Preview — not yet liveBEEM is preparing for the Travel Rule. The related API fields are being released in stages so you can build and test ahead of time. They are optional today and not yet enforced — and become enforceable on 1 July 2026, in line with AUSTRAC's commencement date. Nothing changes in your live integration until then.
What the Travel Rule is
The Travel Rule is a global anti-money-laundering measure for businesses that move crypto on behalf of customers. It requires the provider sending a payment to pass certain details about the sender and the recipient to the provider receiving it — so that key information "travels" with the payment, the same way it already does for traditional bank transfers.
It originates with the Financial Action Task Force (FATF), the global financial-crime watchdog. FATF first applied it to bank wire transfers and extended it to crypto in 2019. Individual countries have adopted it on their own timelines.
Why it applies to BEEM
BEEM is regulated in Australia under the Anti-Money Laundering and Counter-Terrorism Financing (AML/CTF) regime, supervised by AUSTRAC. Under AUSTRAC's reforms, virtual asset service providers must apply the Travel Rule to crypto transfers from 1 July 2026 — so BEEM, and the merchants who transact through BEEM, need to collect and share Travel Rule information on relevant payments from that date.
In plain termsAs a regulated provider, BEEM needs to know who is sending and receiving the crypto that moves through the platform, and pass that information securely to the provider on the other side of the transaction.
What information travels
FATF defines a small set of data points that accompany a payment:
| Party | Information |
|---|---|
| Originator (sender) | Name · wallet address or a unique transaction reference · a physical address or customer identifier |
| Beneficiary (recipient) | Name · wallet address or a unique transaction reference |
The exact requirements can vary by transaction size. BEEM handles the secure exchange of this information with the provider on the other side — your part is to supply the details BEEM asks for on each payment.
What this changes for your integration
Travel Rule information applies across both BEEM payment primitives, inbound and outbound:
- Payment Links — In and Out
- Channels — inbound deposits
In practice, you'll be able to provide additional details about the sender and/or recipient when you create or receive these payments. BEEM takes care of validating and transmitting that information.
Rolling out in stages
| Stage | What happens |
|---|---|
| Now — preview | Travel Rule fields are available in sandbox. Optional. Build and test against them. Nothing is enforced. |
| Before 1 July 2026 | Fields become available in production. Still optional — adopt at your own pace. |
| From 1 July 2026 | Fields become enforceable, in line with AUSTRAC's Travel Rule commencement date for virtual asset transfers. |
How to prepare
- Start populating the new Travel Rule fields in sandbox now, so your integration is ready ahead of the 1 July 2026 deadline.
- Move to sending them in production as soon as the fields go live there.
- If you have questions about your obligations, speak to your account manager.
What's next
What's available now while requirements are optional, and how to prepare.
What changes when enforcement begins and complianceDetails becomes required.
The cross-API model that ties Channels, Payment Links, Contacts, and Travel Rule RFIs together.
Manage the saved counterparties whose data satisfies Travel Rule requirements.