Crypto exchanges commonly use multiple hot wallets to manage outgoing transfers. At the time of initiating a Travel Rule data exchange, the exact hot wallet that will be used to conduct the on-chain transfer may not yet be determined. In such cases, you can submit the Travel Rule transaction with any valid originator wallet address and later update it to reflect the actual wallet used for the transfer.

This ensures that the Travel Rule data accurately matches the on-chain transaction while allowing your internal wallet management processes to operate independently of Travel Rule compliance workflows.

📘

Note

The described wallet address updating method only works with Travel Rule transactions.

Use case

Go with the Update wallet address method when all of the following conditions apply:

• Your organization operates multiple hot wallets for outgoing crypto transfers.
• The specific wallet address used for the on-chain transfer is determined after the Travel Rule data exchange has been initiated or completed.
• You need to modify the originator wallet address to match the actual on-chain transaction.

How wallet address update works

This is the general flow of the originator wallet address update:

1. Travel Rule transaction submission via API. You can create a Travel Rule data exchange transaction using any of the available API methods:
   1. Send transaction for existing applicants
   2. Send transaction for non-existing applicants
   3. Bulk transaction import
2. Completion of the Travel Rule data exchange. The data exchange proceeds as usual — the transaction is matched with the counterparty VASP, and the required originator and beneficiary data is exchanged.
3. Conduct of the on-chain transfer. Your system selects the appropriate hot wallet and performs the on-chain transaction.
4. Modification of the originator wallet address.

📘

Note

• At the creation stage, provide one of your hot wallet addresses as the originator wallet address in the applicant.paymentMethod.accountId field.
• The wallet used for the on-chain transfer may differ from the one specified in the original Travel Rule transaction.

Update originator wallet address

To modify the originator wallet address:

Call the Update wallet address endpoint to replace the originator wallet address with the one actually used for the on-chain transfer.

After a successful request, the data.applicant.paymentMethod.accountId field in the transaction will reflect the updated wallet address.

🚧

Important

• The update modifies the originator wallet address only.
• Ensure that the updated wallet address corresponds to the actual on-chain transaction to maintain data integrity.
• The wallet address update does not trigger a new Travel Rule data exchange — it updates the existing transaction record.

Visibility and audit trail

The wallet address change is recorded in the transaction timeline and is visible in the Sumsub Dashboard. This provides a clear audit trail showing:

• The original wallet address submitted during the Travel Rule data exchange.
• The updated wallet address that reflects the actual on-chain transfer.
• The timestamp of the change.

If the Sumsub protocol (SNS) was used for the data exchange, the wallet address update is also indicated in the mirrored transaction on the beneficiary VASP side. This ensures that both parties maintain accurate and consistent records.