International Wire Compliance: SWIFT, Screening, and Regulatory Requirements

International wire transfers are the lifeblood of global commerce and a primary vector for cross-border financial crime. Every day, the global SWIFT network carries millions of payment messages that collectively represent trillions of dollars in cross-border value transfers. Ensuring that these payments are compliant with applicable sanctions regimes, carry accurate originator and beneficiary data, and are subject to appropriate AML monitoring is a major operational challenge for any institution with cross-border payment capability. For payment institutions routing international wires through correspondent banking relationships, the compliance requirements are layered across multiple regulatory regimes and multiple institutions in the correspondent chain.

The SWIFT MT103 and Mandatory Data Fields

The primary message format for international wire transfers in the SWIFT network is the MT103 — a single customer credit transfer. The MT103 structure defines mandatory and optional fields, and several of those fields are the direct mechanism for regulatory compliance. Field 50 (Ordering Customer) must contain the name and address or account number of the originating customer. Field 59 (Beneficiary Customer) must contain the name and address or account number of the beneficiary. Field 70 (Remittance Information) carries narrative payment reference data. Field 23B (Bank Operation Code) classifies the transaction type.

The completeness and accuracy of these fields is directly regulated. In many enforcement cases, financial institutions have faced penalties not for routing payments to sanctioned parties (which was the underlying regulatory breach) but for systematically stripping or omitting beneficiary data in MT103 messages — a practice that prevented correspondent banks from conducting their own screening. The NYDFS enforcement actions against several European banks in the 2010s centred heavily on this systematic data stripping practice.

EU Wire Transfer Regulation 2015/847

The EU's Wire Transfer Regulation (Regulation (EU) 2015/847, which replaced 1781/2006) implements FATF Recommendation 16 (the Travel Rule) in the EU context. It requires payment service providers to ensure that transfers of funds are accompanied by information on the payer and the payee. For transfers within the EU, this means name, account number, and address/identification number. For transfers outside the EU, full payer and payee information must accompany the transfer throughout the payment chain. The regulation also requires intermediary PSPs to detect missing information and to decide whether to execute, reject, or hold the transfer where information is incomplete.

The UK retained EU 2015/847 in its domestic law following Brexit, and it continues to apply in substantially the same form. The regulation was implemented through the Transfer of Funds (Information on the Payer) Regulations 2017 in UK law. Post-Brexit, UK regulation has not diverged materially on wire transfer data requirements, though future legislative changes remain possible.

OFAC Screening and the 50% Rule

For any US dollar-denominated international wire — and for many non-USD wires that pass through US correspondent banks — OFAC screening is a critical compliance requirement. US financial institutions are prohibited from processing transactions involving SDN-listed parties or jurisdictions subject to comprehensive sanctions programmes. Because most USD clearing passes through US correspondent banks, these requirements have extraterritorial effect: a UK payment institution routing a USD wire through a US correspondent must ensure the transaction would not violate OFAC rules, or risk its correspondent refusing or blocking the payment.

The OFAC 50% Rule — discussed in detail in CCYFX's dedicated sanctions article — extends SDN restrictions to entities that are 50% or more owned by SDN-listed parties, even if those entities are not themselves named on the SDN list. For wire payment screening, this means that name-matching against the published SDN list is necessary but not sufficient: institutions must also identify and screen entities that may fall within the 50% rule through ownership structure analysis.

Correspondent Chain Compliance

In a multi-bank correspondent chain, each institution in the chain bears its own compliance obligations. The originating bank must collect and transmit accurate payer information. Intermediary banks must pass on originator and beneficiary data and must screen against their own sanctions lists. The receiving bank must screen the incoming payment before crediting the beneficiary. Where any institution in the chain detects a potential match, the payment may be delayed, queried, or rejected — creating operational friction that is a recurring complaint from businesses making cross-border payments.

For payment institutions that do not have direct SWIFT connectivity but route payments through a correspondent banking relationship, the compliance responsibility for screening is shared between the PI and its correspondent. The PI typically performs pre-screening before submitting payments to the correspondent, while the correspondent performs its own independent screening. The contractual arrangements between the PI and correspondent should clearly allocate responsibility for each screening obligation and the process for handling queried or blocked payments.

Transaction Monitoring for Cross-Border Payments

Beyond sanctions screening, cross-border wire payments require transaction monitoring for AML indicators. High-risk corridors — payments to jurisdictions on the FATF grey or black list, to countries subject to UK financial sanctions regimes, or to jurisdictions with elevated corruption or financial crime risk — should be subject to enhanced monitoring. Specific red flags for cross-border wire AML include: payments to beneficiaries with no apparent commercial relationship with the payer; round-sum or regularly recurring cross-border payments that do not correspond to known business activities; payments where the stated purpose (field 70) is absent, vague, or implausible; and payments structured to fall just below reporting thresholds.