Travel Rule Enforcement for Paxos Trust Company (PTC): Overview and Who It Affects

This notice is for customers whose Paxos accounts are onboarded to the Paxos Trust Company (PTC) entity. Starting November 30, 2026, PTC will begin enforcing U.S. Travel Rule requirements on crypto transfers to external destination addresses. From that date, any transfer of $3,000 USD-equivalent or more to an external address will need Travel Rule information saved on the destination address before it can be sent.

If your account is with Paxos Global PTE (Singapore), this change does not apply to you. See the PTE Travel Rule FAQ.

This overview explains what is changing and points you to the guide that matches how you use Paxos.

What is changing

Today, Travel Rule information can be provided on each individual transaction. Going forward, it is collected once per destination address and stored on the address itself. Once an address has valid Travel Rule information, every later transfer to that address inherits it automatically. Collect once, transact many times.

Travel Rule information is tied to the specific destination address you save it on. For 3P integrations, information saved for one end user is not applied to another end user.

You may see this information called different names depending on how you use Paxos. In the Dashboard it appears as Beneficiary Details; in the API it is the travelrule_metadata field. It is the same requirement either way.

• Applies to crypto transfers to external addresses (withdrawals, and orchestrations for API integrators) of $3,000 USD-equivalent or more.
• Takes effect on November 30, 2026.
• Above-threshold transfers to an address that is missing valid Travel Rule information will be rejected at enforcement.

Which guide applies to you

How you provide Travel Rule information depends on how you use Paxos.

I connect to Paxos through the API

If you integrate with Paxos programmatically, use the guide that matches your account. The table below helps you tell which one you are.

	First-party ("1P")	Third-party ("3P")
What it means	You use Paxos to hold and move crypto for your own company. The crypto belongs to you.	You use Paxos to hold and move crypto on behalf of your own end users, for example a fintech app holding balances for many individual customers.
This is you if	The crypto belongs to your business, you are the only party sending it out, and you do not set up separate profiles or sub-accounts for other people inside Paxos.	You set up an account inside Paxos for each of your own customers, and you move crypto out to those customers' wallets.
How you provide the information	You manage your own destination addresses, through the API or the Dashboard.	You collect beneficiary details for each end user within your own product and submit them through the API.
Your guide	API Guide for 1P Customers	API Guide for 3P Customers

I manage crypto through the Paxos Dashboard

If you add and manage withdrawal addresses in the Paxos Dashboard rather than through the API, you can add beneficiary details directly in the Dashboard.

Read: Travel Rule Enforcement (PTC): Updating Beneficiary Details in the Dashboard

Note: if you are a 3P customer, the Dashboard manages only your own account's addresses. Beneficiary details for your end users must be provided through the API. See the 3P API guide above.

Not sure which describes you?

Contact your account manager or email support@paxos.com and we will point you to the right guide.

What is not affected

• Withdrawals under $3,000 USD-equivalent.
• First-party transfers between Paxos sub-accounts you own.
• Fiat (cash) payments and internal Paxos-to-Paxos transfers.

Getting help

For full technical detail, see the Travel Rule developer guide. For anything else, contact your account manager or email support@paxos.com.