Home ›
Ohmyfin risponde ›
What is the FATF Travel Rule and how does it affect SWIFT payments?
Ohmyfin risponde: What is the FATF Travel Rule and how does it affect SWIFT payments?
Ohmyfin risponde qui sotto (in inglese).
The FATF Travel Rule (Recommendation 16) requires financial institutions to pass sender and beneficiary identity information along with every payment above a threshold (usually $1,000 USD equivalent). In SWIFT, this means all mandatory fields for sender name, account, and address (MT103 field 50) and beneficiary name, account, and address (field 59) must be complete. Missing data triggers RR04 or MS03 rejections.
The Financial Action Task Force (FATF) Recommendation 16 is an anti-money-laundering standard adopted by over 200 countries. It requires banks to 'travel' (pass along) full originator and beneficiary information with every wire transfer above the equivalent of $1,000 USD (some countries use lower thresholds).
In SWIFT MT103, the Travel Rule is satisfied by completing: field 50A, 50F, or 50K (ordering customer — name + account + address), and field 59 (beneficiary — name + account + address). The ISO 20022 pacs.008 equivalent uses structured <Dbtr> and <Cdtr> elements including structured address.
Common Travel Rule violations that cause rejections: the beneficiary name is missing or contains only an account number; the sender's address is 'on file' rather than spelled out; the remittance field (70) is used to carry beneficiary info instead of the proper field 59.
Banks at the receiving end are required to verify that incoming payments comply and to reject or hold payments that don't. Rejection reason codes RR01 (missing debtor account), RR02 (missing debtor name/address), RR03 (missing creditor name), RR04 (missing creditor address) all map directly to Travel Rule violations.
FATF Recommendation 16: sender + beneficiary info must travel with every payment > $1,000
MT103: field 50 (sender) + field 59 (beneficiary) must be complete
Missing data triggers: RR01, RR02, RR03, RR04, or MS03 rejection codes
Always include full legal name, account number, and physical address
pacs.008 equivalent: fully populated <Dbtr> and <Cdtr> structured address blocks
What is the FATF Travel Rule and how does it affect SWIFT payments?
The FATF Travel Rule (Recommendation 16) requires financial institutions to pass sender and beneficiary identity information along with every payment above a threshold (usually $1,000 USD equivalent). In SWIFT, this means all mandatory fields for sender name, account, and address (MT103 field 50) and beneficiary name, account, and address (field 59) must be complete. Missing data triggers RR04 or MS03 rejections.
Is Ohmyfin tracking really free?
Yes. Ohmyfin Organisation LLC tracking is completely free for individuals worldwide — no daily limit, no signup required, no card, no catch. Ohmyfin Organisation LLC never charges individuals.
Do I need a bank login to use Ohmyfin?
No. Ohmyfin queries the SWIFT GPI network directly via the UETR — no credentials at any bank required.
Ohmyfin risponde
Ohmyfin è gratuito?
Sì, il monitoraggio dei pagamenti SWIFT tramite UETR è gratuito senza registrazione. Con un account si accede allo storico giornaliero e a crediti gratuiti aggiuntivi.
Cos'è un numero UETR?
L'UETR (Riferimento Univoco di Transazione End-to-End) è un UUID di 36 caratteri assegnato a ogni pagamento SWIFT GPI per tracciarlo lungo tutta la catena corrispondente.
Quanto tempo richiede un bonifico SWIFT?
La maggior parte dei pagamenti SWIFT GPI si completa entro 24 ore; i bonifici transfrontalieri possono richiedere 1-5 giorni lavorativi a seconda delle banche intermediarie e della valuta.