Payment transparency and the travel rule

IN ONE LINE

An everyday analogy: imagine a parcel that must, by rule, carry a full label — real sender, real recipient, real addresses — so that every depot it passes through can check those names against a watchlist.

The whole safety system depends on the label being complete and honest.

If someone were to scrub a name off the label to sneak a banned party past the checks, the checks would be blinded.

So the rules require the label to be filled in fully and passed on unchanged, and the depots are trained to notice when a label looks thin, altered, or inconsistent with the parcel.

Payments work the same way: the names of who is paying and who is being paid must travel with the money, complete and unaltered, so every bank in the chain can screen them.

WHAT IT ACTUALLY IS

Payment transparency is the principle that complete and accurate information about the originator (the payer) and the beneficiary (the payee) must accompany a payment along its whole chain.

It is not only good practice; it is a standard.

The travel rule — set out in the Financial Action Task Force (FATF) Recommendation 16 (R.16) — requires that originator and beneficiary information travels with a wire transfer so that each institution handling it can screen the parties and act if one is sanctioned.

The abuse this guards against is wire stripping: removing or altering party information so that a sanctioned or otherwise prohibited name cannot be seen by screening.

Wire stripping is a serious violation, and it is exactly what transparency requirements and screening controls are designed to detect and deter.

HOW IT WORKS

For screening and correspondent-banking teams, transparency is enforced through controls, not trust.

Several work together.

Completeness checks flag payments whose originator or beneficiary fields are missing, sparse, or filled with meaningless text, because thin data is both a quality problem and a possible sign of tampering.

Cover-payment practice matters here: when a customer payment is funded separately, the funding message must carry the underlying parties — in the MT world, an MT202 COV (the cover variant) with its dedicated party fields — so an intermediary is never asked to move value blind to whose payment it is.

Consistency checks compare the customer payment with its cover and with related messages, so a beneficiary name that differs between the two surfaces as an alert.

And because every party field is screened, a stripped or altered name that would have matched a list is precisely what these overlapping checks are built to catch.

The defensive posture is to assume data can be incomplete or manipulated and design controls that notice.

THE WORDS

Travel rule

The requirement that originator and beneficiary information must travel with a transfer through the payment chain so each institution can screen the parties.

Wire stripping

The abuse of removing or altering party information in a payment so screening cannot see a prohibited name; transparency controls are built to detect and deter it.

READ FIRST

• Screening payment messages

CONNECTED TO

• CHECKPOINT Financial crime context checkpoint

SOURCES

• Wolfsberg Group Payment Transparency Standards — The Wolfsberg Group
• The FATF Recommendations: International Standards on Combating Money Laundering and the Financing of Terrorism & Proliferation — Financial Action Task Force
• Payments Signal editorial teaching models — Payments Signal