Sanctions Screening for Payments: How to Screen SWIFT, SEPA, and Cross-Border Transfers

Today, there are numerous payment methods that come with their own inherent advantages, risks, and complexities. Therefore, it may easily become complicated to conduct proper sanctions screening across all of them. In this post, we have elaborated upon how to screen all of these payment methods against sanctions lists.

Why Payment Screening Is Different from Customer Screening

Placed within the broader framework of ongoing due diligence in international Anti-Money Laundering (AML)/ Counter Terrorism Financing (CTF), customer screening concerns the process that individuals and entities go through before an organization establishes a business relationship. After this step, it is periodically refreshed based on the data collected during the onboarding, such as the name, date of birth, nationality, registration details, and UBOs.

On the other hand, payment screening evaluates each transaction in real-time before the execution due to the possible risks that originators, beneficiaries, or intermediaries may bring. Each transfer may introduce new risk factors through originators, beneficiaries, intermediary institutions, or geographic elements embedded in the payment message, which results in different control objectives. While customer screening determines whether a relationship may be established or maintained, whereas payment screening determines whether a specific transfer may be executed.

There are materially different operational constraints that come with this distinction. Often, onboarding decisions can typically accommodate review queues and enhanced due diligence workflows. Transaction screening, however, often operates under significant time pressure. This becomes especially apparent in particularly in cross-border and instant payment environments, where controls are expected to be capable of identifying and managing sanctions risk before funds are made available.

According to the guidance issued by the Office of Foreign Assets Control (OFAC) on compliance considerations for instant payment systems, sanctions compliance programs must be designed to address the speed and operational characteristics of such systems. What this actually means is that faster payment rails do not reduce sanctions obligations. Instead, they require appropriately designed pre-execution or exception-based screening controls.

What Gets Screened in a Payment Message?

In this part, we are going to explore the details of the process.

Who Gets Screened?

Originator / Ordering Customer: Name, address, account number, date of birth, place of birth, national ID or passport of the party that initiates the transfer.

Beneficiary: Name, aliases, account number, address, and beneficiary bank details of the party that receives the funds.

Intermediary and correspondent banks: Additional financial institutions that process the payment, particularly relevant under sectoral sanctions and jurisdictional restrictions.

Ultimate parties: In some arrangements, the beneficiary may not be the final recipient. Therefore, if known or inferable, parties referenced in the remittance information, trade counterparties, and owners subject to the OFAC 50 Percent Rule must be covered.

What Gets Screened?

Name Fields (Primary Screening Elements)

For MT103:

• :50a: Ordering Customer
• :59a: Beneficiary Customer
• :52a: Ordering Institution
• :57a: Account With Institution
• :56a: Intermediary Institution

Equivalent in ISO 20022 (pacs.008):

• <Dbtr> (Debtor)
• <Cdtr> (Creditor)
• <DbtrAgt>
• <CdtrAgt>
• <IntrmyAgt1-3>

Address / Geographic Data

MT103:

• Part of :50K: (Ordering Customer – free text)
• Part of :59: (Beneficiary – free text)

ISO 20022:

• <PstlAdr>
• <Ctry>
• <TwnNm>
• <AdrLine>

Account Identifiers

MT103:

• :20: Transaction Reference
• :50a / :59a: Account numbers
• :57A: BIC
• :52A: BIC

ISO 20022:

• <IBAN>
• <Othr><Id>
• <BICFI>

Remittance Information / Purpose of Payment

MT103:

:70: Remittance Information

:72: Sender to Receiver Information

ISO 20022:

<RmtInf>

<Ustrd> (Unstructured)

<Purp>

<InstrForCdtrAgt>

MT103 vs ISO 20022 - Field Mapping For Screening

Screening Category	MT103 Field	ISO 20022 Equivalent	Screening Objective
Originator Name	:50A/F/K	<Dbtr>	Sanctioned person/entity
Beneficiary Name	:59/59A	<Cdtr>	Sanctioned person/entity
Originator Bank	:52A	<DbtrAgt>	Sanctioned FI
Intermediary Bank	:56A	<IntrmyAgt>	Sanctioned FI
Beneficiary Bank	:57A	<CdtrAgt>	Sanctioned FI
Address	:50K / :59	<PstlAdr>	Jurisdiction screening
Account Number	:50 / :59	<IBAN> / <Id>	Indirect exposure
Purpose / Free Text	:70 / :72	<RmtInf>	Concealed risk indicators

Key Supervisory Expectations

From FATF & BCBS: These authorities expect screening to be in real-time or near-real time, apply to both inbound and outbound payments, include list updates without delay, address false positive governance, and include testing and validation.

From OFAC: OFAC expects a strict liability regime. Particularly, its adherence to 50 Percent Rule (which designates entities owned by more than 50% by sanctioned persons to be blocked) plays an important role. Even if the entity is not explicitly listed, it is still applicable.

From EU Regulations: EU Regulations specifically highlight immediate asset freeze obligation and emphasize that no funds or economic resources can be made available to listed persons.

SWIFT Message Screening: MT103, MT202, and Beyond

Message Type Reference	Description	What it requires
MT103	Single Customer Credit Transfer	It carries the classic sanctions-relevant information (ordering customer, beneficiary, banks, and remittance/instructions. (50a/56a/57a/58a/59a)
MT202	General Financial Institution Transfer	It focuses heavily on institutions and BICs but MT202 COV must additionally additionally includes the underlying customer parties. (50a/59a)
MT700	Issue of a Documentary Credit	It includes trade-finance narrative fields like description of goods/services, shipment/port fields, applicant, and beneficiary. (45A/44E/44F/46A/50/59)
MT710	Advice of a Third Bank’s Documentary Credit	It includes many of the same elements as MT700, including applicant, beneficiary, goods, and transport information. (50/59)

MT103 – Single Customer Credit Transfer

This primary sanctions-relevant payment message designates customer-to-customer payment message.

Key Fields Requiring Screening:

Field	Description	Screening Dimension
:50a	Ordering Customer	Name screening
:59a	Beneficiary Customer	Name screening
:52a	Ordering Institution	BIC screening
:53a	Sender’s Correspondent	BIC screening
:54a	Receiver’s Correspondent	BIC screening
:56a	Intermediary Institution	BIC screening
:57a	Account With Institution	BIC screening
:70	Remittance Information	Narrative screening
:72	Sender to Receiver Info	Narrative screening

Screening Risks: Direct SDN/asset freeze exposure, indirect exposure via sanctioned banks, jurisdictional sanctions (country in address/IBAN), concealed counterparties in free text, and vessel or goods references in narrative. MT103 must be screened in real time prior to execution.

MT202 – General Financial Institution Transfer (Non-COV)

It is historically used for cover payments and refers to bank-to-bank transfer without customer data. MT202 does not carry underlying customer information.

Key Fields:

Field	Description	Screening Dimension
:52a	Ordering Institution	BIC screening
:53a	Correspondent	BIC screening
:54a	Correspondent	BIC screening
:56a	Intermediary	BIC screening
:57a	Account With Institution	BIC screening

Risk Consideration: Since MT202 lacks customer fields, it was historically used to obscure underlying sanctioned parties. This transparency gap led to regulatory reform. Its screening focus is on sanctioned financial institutions, jurisdictional exposure, and correspondent risk.

MT202 COV – Cover Payment Message

MT202 COV designates bank-to-bank transfer carrying underlying customer information and was introduced following FATF transparency concerns under Recommendation 16. It includes all MT202 institutional fields, but also:

Field	Description	Screening Dimension
:50a	Ordering Customer	Name screening
:59a	Beneficiary Customer	Name screening
:70	Remittance Information	Narrative screening

Regulatory Importance: MT202 COV ensures full transparency of originator and beneficiary, screening of underlying customer data, and prevention of sanctions evasion through correspondent structures. It should be stated that both institutional and customer screening are mandatory.

MT700 – Issue of a Documentary Credit

MT700 refers to trade finance instrument (Letter of Credit). It should be noted that trade messages carry significantly broader sanctions exposure.

Key Fields:

Field	Description	Screening Dimension
:50	Applicant	Name screening
:59	Beneficiary	Name screening
:32B	Currency/Amount	Sectoral sanctions relevance
:44A–F	Shipment / Ports	Geographic screening
:45A	Description of Goods	Goods screening
:46A	Documents Required	Narrative screening
:47A	Additional Conditions	Narrative screening
:41A	Available With Bank	BIC screening

Additional Risks:

Trade finance screening must consider:

• Dual-use goods
• Embargoed commodities
• Sanctioned ports
• Sanctioned vessels (IMO numbers)
• Shipping routes
• Front companies
• Transshipment jurisdictions

Trade sanctions enforcement has shown that narrative goods descriptions are critical control points.

MT710 – Advice of a Third Bank’s Documentary Credit

MT710 refers to advising bank notifying beneficiary of a documentary credit issued by another bank. Although it is very similar to MT700, MT710 also introduces additional banks, may amend original trade terms, and introduce new jurisdictions.

Key Fields:

Field	Description	Screening Dimension
:50	Applicant	Name screening
:59	Beneficiary	Name screening
:41A	Advising Bank	BIC screening
:44A–F	Shipment Data	Geographic screening
:45A	Goods Description	Goods screening

Screening must include newly introduced financial institutions, and changes in trade routes or shipment data.

Other High-Risk SWIFT Messages

Sanctions exposure is not limited to payment messages.

MT760 – Guarantees / Standby L/C

MT760 creates contingent financial obligations and requires screening of applicant, beneficiary, counter-guarantor, and underlying trade references.

MT799 – Free Format Trade Message

It designates high risk due to unstructured content and requires robust narrative screening logic.

MT299 / MT999 – Free Format Messages

These are often used for clarifications and must be screened if referencing sanctioned parties.

ISO 20022 Equivalents

As the industry migrates to ISO 20022:

MT Message	ISO 20022 Equivalent
MT103	pacs.008
MT202	pacs.009
MT202 COV	pacs.009 (with underlying data)
MT700	tsmt.001 / trade services messages

Screening logic must map:

• MT :50a → <Dbtr>
• MT :59a → <Cdtr>
• MT :57a → <CdtrAgt>
• MT :70 → <RmtInf>

Regulators expect consistent screening logic across MT and ISO messages.

Core Supervisory Expectation

Across all message types, sanctions screening must:

1. Cover all identified parties
2. Screen all financial institutions in the chain
3. Detect jurisdictional restrictions
4. Analyze narrative/unstructured fields
5. Operate prior to making funds available where legally required
6. Be updated immediately upon list changes

Failure in any of these dimensions has resulted in significant enforcement actions globally.

SEPA and EU Payment Screening Obligations

SEPA (Single Euro Payments Area), governed at scheme level by the European Payments Council, standardizes euro payments across the EU and additional SEPA-participating countries. However, SEPA Credit Transfers (SCT), SEPA Instant Credit Transfers (SCT Inst), and SEPA Direct Debits remain fully subject to EU restrictive measures and related sanctions obligations. This is primarily due to the fact that EU sanctions apply to funds and economic resources regardless of the payment mechanism.

EU restrictive measures are adopted by the Council of the European Union under Article 215 of the Treaty on the Functioning of the European Union (TFEU) and are implemented through directly applicable Council Regulations published in the Official Journal of the European Union. These Regulations impose, inter alia, asset-freeze obligations and prohibit making funds or economic resources available, directly or indirectly, to listed natural or legal persons, entities, or bodies. Consequently, any euro-denominated payment executed through SEPA must comply with these prohibitions.

Transfer of Funds Regulation (EU) 2015/847 and Data Transparency

Regulation (EU) 2015/847, commonly referred to as the Transfer of Funds Regulation (TFR), governs the information that must accompany transfers of funds and the obligations of Payment Service Providers (PSPs) for carrying required payer and payee data through the payment chain. It requires that accurate payer and payee information accompany transfers, establishes verification obligations for PSPs of the payer, and sets out procedures for handling missing or incomplete information by intermediary and beneficiary PSPs. While running sanction checks is not explicitly mandated in the Regulation, the obligation to ensure data completeness, traceability, and integrity throughout the payment chain constitutes a structural prerequisite for effective sanctions screening and asset-freeze enforcement.

PSD2 Governance and Risk-Based Control Framework

Under the Revised Payment Services Directive (PSD2) (Directive (EU) 2015/2366), Payment Service Providers operating in the EU must apply effective risk-based governance, internal control mechanisms, and security frameworks to manage operational and compliance risks. Although PSD2 is not itself a sanctions instrument, it requires PSPs to implement systems and processes that prevent unauthorized or unlawful transactions, thereby reinforcing the institutional obligation to integrate sanctions-related controls within transaction processing and execution logic. Supervisory expectations in Member States reflect that sanctions compliance forms part of the broader compliance and risk management framework required under PSD2.

Regulation (EU) 2024/886 and SEPA Instant Credit Transfers

In addition, Regulation (EU) 2024/886 (Instant Payments Regulation) amended the SEPA framework to address sanctions screening in the context of SEPA Instant Credit Transfers. Given the requirement that SCT Inst transactions be executed within a maximum of 10 seconds and on a 24/7 basis, the Regulation introduces harmonised obligations for PSPs to verify whether their customers are subject to targeted financial restrictive measures. This reform aims to reconcile the immediacy of instant payments with the asset-freeze obligations under EU sanctions law. This ensures that compliance mechanisms do not undermine execution timelines but continue to prevent funds from being made available to listed persons.

EU Sanctions Legal Architecture and Consolidated List

EU sanctions measures are codified in Council Regulations and Decisions and are binding in their entirety across Member States. Enforcement and supervision are carried out by national competent authorities designated by each Member State. The central reference source for sanctions screening is the EU Consolidated Financial Sanctions List. This list reflects the designations adopted under Council Regulations. European Commission (DG FISMA) maintains this consolidated list and publishes it through the Official Journal and related EU platforms. On the other hand, the European External Action Service provides policy coordination and public access tools, including the EU Sanctions Map.

Operational Implications for SEPA Screening

Accordingly, SEPA payment instruments, whether batch SCT, SCT Inst, or SDD, must be processed within a compliance framework that ensures identification of payer, payee, and relevant agents (as reflected in ISO 20022 data elements such as Debtor, Creditor, Debtor Agent, Creditor Agent, and, where applicable, Ultimate Debtor or Ultimate Creditor), combined with screening against applicable EU restrictive measures. The uniform technical format of SEPA payments does not diminish sanctions obligations because it provides the structured data environment within which those obligations must be effectively operationalized.

Cross-Border Payment Screening Challenges

Correspondent banking chains: Each cross-border payment goes through multiple institutions in the chain and each of these institutions apply their own controls. In practice, the originator’s bank screens the payment based on its full customer due diligence (CDD) information, intermediary banks screen based only on the data transmitted within the payment message, and the beneficiary’s bank conducts screening based on the received instruction and its own customer relationship.

However, this layered control structure creates several risks such as information asymmetry, inconsistent screening outcomes, and repeated investigations. This has led to the reinforcement of international standards, such as FATF Recommendation 16. This change specifically addresses transparency gaps in correspondent and cover payment structures.

Data Quality, Truncation, and Message Formatting Constraints: Cross-border payments are highly sensitive to message formatting constraints. Differences between SWIFT MT formats, ISO 20022 messages, and local clearing systems may result in character limitations, truncation of names or addresses, loss of diacritical marks, removal of middle names, and abbreviation of legal entity identifiers.

Data degradation during message transmission increases both false positives and false negatives in sanctions screening. Even if there are minor variations in spacing, punctuation, or character encoding, these can radically affect matching logic. The effectiveness of sanctions screening is therefore directly dependent on upstream data quality and message integrity.

Transliteration and name-variation issues: Multiple spellings, abbreviations, and derivations in names make cross-border traffic especially vulnerable to false positives and negatives. These often happen when processing alphabets such as Arabic, Chinese, and Cyrillic due to several reasons such as vowels not always being written explicitly, varying prefixes, and certain letters not having a direct Latin equivalent. Let’s say a sanctions list contains “Mohammed Al Hassan” but it appears “Muhamad Elhassan” in the payment message, matching will most likely fail.

Sanctions list differences across jurisdictions: Designation criteria, scope, ownership rules, update frequency, and data formats may vary from one jurisdiction to another. For example, the EU Consolidated List may differ from the OFAC list, which makes screening against only one jurisdiction’s list insufficient for institutions with multinational exposure.

Extraterritoriality and Conflict of Laws: The extraterritorial application of certain sanctions regimes can further complicate cross-border screening. A transaction permissible under EU law may nonetheless be prohibited under U.S. sanctions if it involves U.S. persons, U.S. financial institutions, U.S. dollar clearing, or secondary sanctions exposure.

Conversely, EU law includes mechanisms such as the Blocking Statute, which may restrict compliance with certain third-country extraterritorial measures. This creates legal and operational tension for global institutions because they are expected to design screening frameworks capable of navigating conflicting regulatory requirements.

Ownership Structures and Indirect Exposure: Sanctions screening does not only involve matching listed names. Cross-border complexity increases when dealing with layered corporate ownership structures, beneficial ownership opacity, front companies, shell entities, and complex trade structures. Indirect exposure through ownership or control requires integration of beneficial ownership data with screening systems because incomplete ownership transparency significantly weakens screening effectiveness.

Real-Time Constraints and List Updates: Cross-border payments operate across time zones and settlement systems. Sanctions lists may be updated at different times, and propagation of updates across internal systems may not be instantaneous. This raises challenges such as payments getting screened before designation but settled after designation, timing discrepancies between institutions, or handling of post-settlement freezes. These operational pressures are often amplified by real-time screening requirements, particularly in instant payment contexts.

Sanctions Evasion Typologies in Cross-Border Flows: Cross-border payments are frequently used as vehicles for sanctions evasion. Typologies identified by international bodies include nested correspondent banking, use of third-country intermediaries, trade-based money laundering, misdescription of goods, use of sanctioned vessels or ports, and rapid restructuring of ownership. Effective screening requires continuous adaptation to evolving evasion techniques.

De-Risking and Systemic Implications: The cumulative complexity of cross-border sanctions compliance has led many institutions to terminate correspondent relationships in higher-risk jurisdictions. This phenomenon is commonly referred to as “de-risking”. Although it reduces sanctions exposure, this activity may limit financial inclusion, disrupt humanitarian flows, and increase concentration risk in the banking sector. Therefore, balancing compliance rigor with proportionality remains an ongoing policy challenge.

The OFAC 50% Rule in Payment Screening

OFAC considers entities owned 50% or more in the aggregate by one or more blocked persons to be blocked, even if they do not appear on the SDN List. In practice, this means that multiple blocked persons’ ownership interests must be added together when assessing whether the 50% threshold is met (e.g., 25% + 25% = 50%). The same guidance clarifies that “property” and “interests in property” are interpreted broadly and include direct and indirect interests.

However, it should be mentioned that if an entity is merely controlled, it is not automatically blocked under the 50% Rule. OFAC’s interpretation of the rule “speaks only to ownership and not to control,” and an entity that is controlled but not 50% or more owned by blocked persons is not automatically considered blocked under this rule. At the same time, this does not eliminate compliance risk. For example, an entity may still be designated separately by OFAC under a relevant sanctions program, and institutions typically treat strong control signals as heightened risk even where the mechanical 50% ownership threshold is not met (as part of broader sanctions risk management).

When screening transactions, often only named parties are scanned because ownership information is not carried in the payment message, which creates a structural limitation. For example, SWIFT/ISO 20022 payment messages identify the transacting parties and agents, but do not carry a reliable corporate ownership graph or beneficial ownership percentages. As a result, transaction-only name screening can miss situations where the named counterparty is not listed but is blocked by operation of the 50% Rule.

This neglects OFAC’s 50% Rule and therefore results in a material sanctions compliance gap. In order to detect exposure under this rule, institutions must integrate corporate hierarchy and beneficial ownership intelligence into their screening workflows so they can evaluate whether any counterparty is directly or indirectly owned 50% or more in the aggregate by blocked persons.

Additional operational considerations

Direct vs indirect ownership mapping: OFAC’s guidance explicitly includes indirect ownership. Practically, institutions must be able to “look through” ownership chains to determine whether blocked persons’ interests aggregate to 50% or more. This requires entity-resolution (matching the payee to the correct legal entity) and ownership mapping that can handle subsidiaries, holding companies, and layered structures.

Aggregation logic and what does not get attributed: The Revised Guidance explains the aggregation principle and provides interpretive examples. It also clarifies that the analysis hinges on whether blocked persons’ combined ownership reaches the threshold; if an entity is less than 50% owned by blocked persons, it is not automatically blocked under the 50% Rule (though other risk signals may still be relevant).

List screening vs “rule-based” blocking determination: OFAC’s 50% Rule is a prime example of why sanctions compliance is not only “list matching.” A transaction can be prohibited even when no party name matches the SDN List, because the counterparty is blocked through ownership. This is why institutions typically combine name screening against OFAC lists and ownership-based determinations under the 50% Rule.

Governance and maintenance challenge: Even with specialized tools, effectiveness depends on the quality and freshness of ownership data, which may be incomplete, outdated, or opaque in some jurisdictions. OFAC’s guidance and FAQs emphasize the need for appropriate due diligence when considering transactions involving non-listed entities that may be owned by blocked persons.