Last reviewed: · Curated by Ohmyfin Organisation editorial.
Field 50F is the structured ordering-customer format — carrying name, address, country and identifier in tagged sub-fields. Replacing legacy 50K as the ISO 20022 transition completes. Draft an MT103 with 50F →
Format specification: field 50F uses a sub-field structure with numeric tag prefixes on each line. Line 1: the party identifier (account number preceded by a slash, or national ID in the format /C1/identifier where C1 is a 2-character country code, or a BIC). Lines 2 onwards use numeric tags: 1/ for name (up to 35 characters), 2/ for address line (up to 35 characters, repeatable), 3/ for country code and town (2-letter ISO country code, slash, town name up to 33 characters), 4/ for date of birth (format YYYYMMDD), 5/ for place of birth (country code, slash, city), 6/ for customer identification number, 7/ for national identifier (e.g. passport, national ID), 8/ for additional information.
The tagged sub-field structure of 50F makes it machine-readable in a way that 50K is not. Automated sanctions-screening systems can extract the name (tag 1/), address (tag 2/ + tag 3/), and identifier (tags 6–7) from a 50F field with high confidence, without needing to parse free-format text heuristically. This significantly reduces false positives and false negatives in sanctions screening, which is a major compliance cost driver for correspondent banks.
Banks worldwide migrated from 50K to 50F as part of the SWIFT MT/MX transition. The SWIFT Standards Release updates progressively made 50F mandatory in more scenarios. By the end of the CBPR+ coexistence period (November 2025), the expectation is that all MT103 messages on cross-border SWIFT corridors use 50F for individual and corporate ordering customers, reserving 50K only where legacy systems cannot yet produce 50F.
One important difference between 50F and 50K is how they handle corporate ordering customers. A corporate using 50F would typically have: line 1 as the account number (e.g. /12345678); tag 1/ for the company's full legal name; tag 2/ for the registered street address; tag 3/ for country code and city; and optionally tag 6/ or 7/ for the company registration number or tax ID. This structured data feeds directly into the ISO 20022 Debtor element format, making 50F the natural bridge between the MT103 legacy format and the richer pacs.008.
Under the FATF Travel Rule, 50F is strongly preferred over 50K because it provides machine-parseable identity data rather than free-form text. SWIFT has published guidance stating that 50F should be used in all new MT103 implementations that can support it. Banks receiving MT103 messages with 50F can automatically populate their pacs.008 Dbtr element from the 50F tags with minimal manual mapping.
| Example value | :50F:/12345678\nJOHN DOE\n1/123 MAIN ST\n2/LONDON GB |
|---|---|
| Valid characters / format | Account + structured name/address (lines 1-7) |
| Required on MT103 | Mandatory |
| Required on MT202 | Not used |
| Required on pacs.008 | Mandatory |
| Notes | Structured ordering customer. Replaced by <Dbtr> ISO20022 block. |
Structured data in 50F dramatically improves automated sanctions screening, reduces false positives, satisfies FATF Travel Rule requirements more reliably, and makes translation to ISO 20022 pacs.008 accurate and automatic. 50K free-format text must be parsed heuristically, which is error-prone and expensive for compliance teams.
Tag 1/ = name (individual or company name, up to 35 chars). Tag 2/ = address line (repeatable for multi-line addresses). Tag 3/ = country code and town (e.g. GB/London). Tag 4/ = date of birth (YYYYMMDD). Tag 5/ = place of birth (country/city). Tag 6/ = customer identification number. Tag 7/ = national identifier (passport, national ID). Tag 8/ = additional information.
50F is the strongly preferred variant for individuals and corporates on all new MT103 implementations per SWIFT standards guidance. It has been progressively mandated in more corridors through SWIFT Standards Releases. After the CBPR+ migration deadline (November 2025), 50F should be used in all MT103 cross-border payments where the ordering customer is not an FI.
Yes — tag 7/ in field 50F carries a national identifier, which can be a passport number, national ID number, or driver's licence number. The format is typically: 7/[document type code] [document number] [country issuer]. Check your bank's specific implementation guide for the exact format expected.
Field 50F is a compact line-based tagged format within the MT103 character set constraints. The pacs.008 Dbtr XML element has explicit sub-elements for each piece of data (Nm, PstlAdr, Id, etc.) with no character-set restrictions and richer address structure. When SWIFT translates a 50F to pacs.008, it maps each tag to the corresponding Dbtr sub-element.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →