SWIFT SR2026

Address Verification.
Structured, enriched, payment-ready.

Turn free-text and partial addresses into structured, enriched payment data before payments are sent. Improve address quality for payment processing, screening, and ISO 20022 requirements through a flexible integration.

Book a demo

What changes

SWIFT Standard Release 2026 removes fully unstructured postal addresses from CBPR+ payment messages.

The minimum

Town and country, carried in the designated structured fields.

Free text addresses

SWIFT will reject messages that keep the address in free text, with no warnings and no contingency processing.

The same address, three ways

Each card uses the same address. The field structure changes the message status.

Fully structured

Accepted

<Nm>NORTHWIND CARGO LTD</Nm>
<PstlAdr>
  <StrtNm>MILL ROW</StrtNm>
  <BldgNb>14</BldgNb>
  <PstCd>EC1A 1BB</PstCd>
  <TwnNm>LONDON</TwnNm>
  <Ctry>GB</Ctry>
</PstlAdr>

Address components split into dedicated ISO 20022 fields.

Hybrid

Accepted

<Nm>NORTHWIND CARGO LTD</Nm>
<PstlAdr>
  <TwnNm>LONDON</TwnNm>
  <Ctry>GB</Ctry>
  <AdrLine>14 MILL ROW</AdrLine>
  <AdrLine>EC1A 1BB</AdrLine>
</PstlAdr>

Town and country structured; other details may stay in address lines.

Fully unstructured

Rejected

<Nm>NORTHWIND CARGO LTD</Nm>
<PstlAdr>
  <AdrLine>14 MILL ROW</AdrLine>
  <AdrLine>LONDON</AdrLine>
  <AdrLine>EC1A 1BB GB</AdrLine>
</PstlAdr>

The address is provided only as free text.

Illustrative example. The company and address do not identify a real business.

Wrong data, neatly formatted, is still wrong

Structuring formats the record. Only verification establishes that the address behind it is correct.

Problems in today’s flow

Stored records

Most payment systems keep postal addresses as a single block of free text.

Files and APIs

Corporate files, APIs and host-to-host channels bypass front-end controls.

Manual work

Payment teams have little time to structure each address by hand.

21% of payment delays and failures stem from beneficiary name and address problems, the most common single cause.

LexisNexis Risk Solutions, “True Impact of Failed Payments” (2023) · global survey of 400 payments decision-makers

StrtNmMILL ROW
BldgNb14
PstCdEC1A 1BB
TwnNmLIVERPOOL → LONDON
CtryGB

Illustrative example.

The format looks correct. The wrong town remains hidden inside structured fields.

Neatly formatted. Still wrong. The town does not match the postcode.

Caught before the payment. Verification flags it, correction fixes it: wrong-but-formatted data never reaches the payment.

01

Looks structured

PstCdEC1A 1BB
TwnNmLIVERPOOL

The format looks correct. The wrong town remains hidden inside structured fields.

02

Mismatch found

PstCdEC1A 1BB
TwnNmLIVERPOOL

Neatly formatted. Still wrong. The town does not match the postcode.

03

Corrected

PstCdEC1A 1BB
TwnNmLIVERPOOL → LONDON

Caught before the payment. Verification flags it, correction fixes it: wrong-but-formatted data never reaches the payment.

Where the work lands

The deadline is the same for everyone. The operational burden depends on where address data enters the payment flow.

Banks and financial institutions

  • Payment channels
  • Corporate portals
  • Host-to-host files
  • Saved beneficiaries
  • Payment operations

PSPs and cross-border platforms

  • Beneficiary onboarding
  • Payout flows
  • Partner bank requirements
  • Cross-border payment ops

ERP and treasury providers

  • Vendor master records
  • Supplier onboarding
  • Treasury payment files

Use the required channel change to improve payment data

The channel rework is happening either way. The only variable is whether verification comes out of it.

Stored records

Payers and saved payees are often stored as one unstructured block, which is incompatible with SWIFT's structured-address mandate.

With iPiD, the same records are parsed, structured and enriched into ISO 20022 fields.

View example
saved beneficiary
NORTHWIND CARGO LTD
AdrLine 14 MILL ROW LONDON EC1A 1BB
StrtNm MILL ROW · TwnNm LONDON · Ctry GB 

Supplier files

ERPs often store supplier addresses in one unstructured block, leaving someone to re-format them before payment.

With iPiD, address data is checked, structured and improved before the payment is sent.

View example
payout_file.csv
beneficiary_address
format one free-text column
format checked · structured · improved 

Channel change

Teams rebuild channels for structured address capture and get no verification from the work.

With iPiD, the same mandatory change returns verified addresses and, with Know Your Payee, verified payees.

View example
channel capture
rebuilt for structured payee details
returns compliance only
returns verified addresses · verified payees 

What iPiD Address Verification does

Address parsing

Structured ISO 20022 address fields.

Address verification

Trusted payment data and higher STP rates.

Enrichment and correction

Higher-quality beneficiary information and improved downstream screening.

One workflow

Less rework, less remediation, fewer operational exceptions.

How it is delivered

  • API
  • Bulk / batch
  • Part of a broader iPiD setup

One-time data clean-up, then real-time verification: SWIFT-compliant from day one, with every CBPR+ message carrying a verified, structured address.

With Know Your Payee

Verify the address and the payee in one API

Payee verification confirms the name and account details match; address verification confirms the address is complete, structured and correct. Adopt both and they run on one API, one integration. Address Verification also runs standalone, with no payee-verification setup. Compliance comes out of the mandate; verified payees and a better customer experience come out of the same work.

Where to start

Readiness depends on the quality of address data across the payment chain, not on the message format alone.

  1. Find where unstructured addresses exist today.

  2. Identify which payment flows are most exposed.

  3. Plan how messy address data will be converted into structured or hybrid formats before payments are submitted.

Reviewing your SWIFT 2026 readiness?

We can help assess where iPiD Address Verification fits into your broader payment validation strategy, and how to arrive SWIFT-compliant from day one.

Book a demo