Travel Rule
Regulation (EU) 2023/1113 requires named originator and beneficiary information to travel with a crypto-asset transfer. FORCE populates what chain data can evidence and marks the rest as outstanding.
Required information
| Field | Source |
|---|---|
| Originator name | Your customer records |
| Originator account identifier | Chain data |
| Originator address or official identifier | Your customer records |
| Originating CASP | Register match, or your own identity |
| Amount | Chain data |
| Beneficiary name | Counterparty VASP, over your Travel Rule channel |
| Beneficiary account identifier | Chain data |
| Beneficiary VASP | Attribution, where the counterparty is labelled |
Held transfers
Where a required field is absent, the transfer is held and the reason is recorded against the packet reference. The reason maps one to one onto the reporting categories, so a held transfer can be explained to a supervisor without further reconstruction.
- Missing beneficiary name is the most common reason and usually resolves once the counterparty VASP responds.
- An unattributable beneficiary VASP cannot be resolved by asking; it needs a manual decision recorded against the case.
- A counterparty on a sanctions list is not a held transfer but a blocked one, and carries a separate reporting obligation.
What this build does not do
FORCE does not operate a Travel Rule messaging channel. It prepares and validates the packet, and shows what is outstanding. Transmission to the counterparty VASP happens over whichever protocol your firm already uses.
A field FORCE cannot evidence is shown as missing, never as satisfied. Treating an unpopulated field as complete is the failure mode this screen exists to prevent.
Text last revised 12 Aug 2026