Screening payment messages
Payments are screened in flight: party fields, agent identifiers, and free text — and how the message is structured decides how well that works.
L0 Explain simply
An everyday analogy: the parcel gate reads labels, and labels come in two kinds. A well-designed label has separate printed boxes — sender here, receiver there, contents note in its own field — so the checker knows exactly what each word is. A messy label is one scrawled paragraph mixing names, addresses, and remarks, so the checker must treat every word as potentially a name. Payment messages are the labels. Older formats and free-text fields are the scrawled paragraph: everything must be checked, and a street name can look like a listed person. Structured formats are the printed boxes: the checker can apply the right test to the right field. Both must be screened — but one produces far more confident answers.
L1 Core concepts
Transaction screening reads the whole message: originator and beneficiary names and addresses, intermediary and agent identifiers, countries, and the free-text spaces — remittance information and payment purpose — where any name might appear. It runs at a point where the payment can still be stopped, typically as the payment engine processes the instruction, because a check after settlement can only report, not prevent. Message format shapes precision. An MT103 carries parties in line-oriented text fields where name, street, and city blur together; a pacs.008 provides structured elements so a name is labelled as a name and a country as a country. The screening engine maps each message type's fields to screening attributes, and that mapping is part of the control — an unmapped field is an unscreened field.
L2 Practitioner view
Free text is where practitioners earn their pay. Remittance lines produce the noisiest hits — geographic terms, ship names, ordinary words that collide with short list names — yet they cannot be skipped, because a listed party mentioned only in the payment reference is still a listed party, and the linked free-text scenario shows exactly that. Role matters too: an intermediary bank screens traffic where neither party is its customer, so it decides holds with the least context and often must query another bank for information before it can dispose of an alert. Holds have operational physics: a held payment sits in a queue while cut-offs approach, so escalation paths and staffing follow the clock. And upstream data handling — truncation or lost structure in translation between formats — quietly shrinks what the filter can see.
L3 Technical details
Design decisions worth knowing: institutions document which fields of which message types are screened and why, since screening everything indiscriminately buries reviewers while screening too little creates blind spots — field scope is a risk decision with an owner. Structured ISO 20022 data enables field-aware rules: country codes checked as countries, name elements matched as names, identifiers compared as identifiers, which measurably reduces false positives from address text — but only where senders actually populate the structured elements rather than pasting unstructured text into them. Migration periods are the danger zone: when a rail moves from MT to ISO 20022, every screening field mapping must be rebuilt and retested, and the sanctions-hold exception scenario in the CBPR+ flow shows how a screening stop plays out mid-chain.
Sources & standards2
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Transactions/message screening: parties, routing data, and free-text fields
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group · Party information transparency in payment messages
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
L4 Standards & sources
Two Wolfsberg Group documents frame what a payment message must keep visible to the filter. The Payment Transparency Standards govern the data side: payment service providers should not omit, delete, or alter debtor or creditor information to defeat detection by others in the chain, should reflect each party's role in the appropriate field, and should carry originator and beneficiary details through a cover payment — the leg that once travelled without customer names. The Wolfsberg Guidance on Sanctions Screening covers the filter side: its transactions/message screening section identifies what to screen — parties, agents, routing data, and free text such as reference and purpose — noting that amounts and dates add no screening value. Both are market practice rather than law, anchoring what correspondent-banking counterparties and examiners expect a screenable message to contain.
Sources & standards2
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group · Standards on party information: no omission or alteration of debtor/creditor data; party roles in appropriate fields; cover payment transparency
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Transactions/message screening: data elements to screen, including free-text fields
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
SEE THE PAYMENT MOVE
Read the steps as text
- 02ProcessingBank Alfa validates, screens, and debitsBank Alfa (debtor agent)
Checks and screening run on rich, structured fields — one of ISO 20022's main gains. The customer account is debited on acceptance.
- DR Debtor's account at Bank Alfa — USD 1,250,000.00
Screening checkpoint: Outbound screening on structured data — Structured names and addresses screen more precisely than free-text lines, cutting false positives.
- 04ProcessingMeridian screens in the middle of the chainMeridian Bank (intermediary agent)
The intermediary agent screens the structured parties and checks cover on Bank Alfa's account.
- 05SettlementThe correspondent settles across its booksMeridian Bank (intermediary agent)
Settlement is a book transfer between the two banks' USD accounts at Meridian — same mechanics as the MT world; the message standard changed, the money movement did not.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 1,250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 1,250,000.00
- 07ProcessingCassia validates the incoming paymentCassia Bank (creditor agent)
Inbound screening and account checks before the credit is applied.
- 08PostingThe creditor is creditedCassia Bank (creditor agent)
The structured remittance information lets the creditor reconcile the invoice automatically.
- CR Creditor's account at Cassia — USD 1,250,000.00
Sources for this topic3
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Transactions/message screening
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group · Roles and responsibilities for party information in payments
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The label analogy reduces format differences to structured versus free text; real MT fields have partial structure and real ISO 20022 usage varies by community. Field-mapping examples are illustrative, and all parties in the linked scenarios are fictional.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.