All Collections
Travel Rule
Travel Rule - Transaction vs transfer?
Travel Rule - Transaction vs transfer?
Written by Paul Yardley
Updated over a week ago


There is an important different between a transaction and a transfer and how they are used.


Transaction are on-chain, atomically executed transactions. They are usually network specific and are what would be shown on a block explorer. A transaction is atomic in that it happens or it doesn't. There is no chance for part of the transaction to happen (in TrustVault supported chains).

TrustVault allows you to create transactions and these are workflowed via our multi-sig solution before being sent to the network.

An example of a transactions would be an Ethereum transaction such as this one.


Transfers are the value transfers that occur nearly always as a result of a transaction. There may be more than one transfer as part of a transaction.

TrustVault doesn't allow you to create transfers directly. You must create a transaction and the transfer of value is the result

Taking the Ethereum transaction from above, we can see that as a result of the transaction there were three transfers.

Why is that important?

For the TravelRule it is importat to not that Travel lrule applies to transfers. For example, if you received a transaction to your address, it may well be that you actually recieved two or more trasfers. e.g Some USDT and some USDC. Both transfers will require Travel Rule.

For outbound transactions this is very important because if there are multiple transfers in a transaction and one transfer is rejected, then it won't be possible to send the transaction as transactions are atomic. So, everything must be approved or nothing does.

Contact us

If you have any issues, please get in touch. For technical support reach out to For compliance issues reach out to

Did this answer your question?