Best Practices for ISO Migration for JPMC Digital Channels
Adoption of the ISO 20022 standard for high-value and cross-border payment initiation is optional at this time and clients can continue using existing methods. However, we are prepared to support you if you decide to adopt ISO 20002 pain.001.v3 via a Host-to-Host connection or SwiftNet FileAct.
Starting in November 2026, it will be mandatory for all cross-border payments to incorporate either fully structured or hybrid structured addresses, as unstructured address will be decommissioned by SWIFT CBPR+ and some national clearing systems across the globe, based on regulatory desire to improve screening capabilities.
Summary of Key Points
New Message Versions:
- Adoption of new message versions is encouraged but is not required at this time.
- New message versions align to the 2019 ISO standards: pain.001.001.09 for credits, pain.008.001.08 for debits, and pain.002.001.10 for status acknowledgments.
Certain markets may require usage of a particular message version for specific use cases
Postal Address Formatting:
- Only "Fully Structured" and "Hybrid" address options will be supported. The "Fully Unstructured" format is being discontinued.
- For any postal address sent, "Town Name" and "Country" must be included in specific data elements as a minimum requirement. (Hybrid structure)
- Examples are provided using both 2009 and 2019 schemas, illustrating the absence of <AddressLine> in "Fully Structured" formats and its presence in "Hybrid" formats.
- “Fully Unstructured” addresses will not be accepted by Swift after November 2026, with many other markets also adopting this stance.
Character Set:
- Proprietary and text data elements, excluding names and addresses, are limited to the FIN-X-Character set, which includes letters, numbers, and specific symbols.
- Names, addresses, and related remittance information can include additional characters, such as !#$&%*=^_’{|}~";<>@[\], with < and > replaced by < and >.
- Certain markets may support additional character sets.
Banking and Payment Practices:
- For in-country payments supporting local languages, additional character support will be detailed in client guides.
- When providing information about CreditorAgent or IntermediaryAgents, using BIC is recommended. If a non-BIC local bank ID or postal address is used, "Town Name" and "Country" are required.
- The "Regulatory Reporting" section should be used for conveying payment purposes and other country/currency requirements, replacing the use of <Unstructured> and <InstructionForDebtorAgent>.
Postal Address: Only Fully Structured and the Hybrid options will continue. Fully Unstructured will be discontinued and you should plan to of discontinue that method. Also, it is becoming a clearing requirement if any postal address is sent. Town Name and Country must be provided at minimum, in their specific data elements.
[Examples using 2009 schemas]
Fully Structured - Absence of AddressLine
<PstlAdr>
<Dept>Department</Dept>
<SubDept>Sub-Department</SubDept>
<StrtNm>Street Name</StrtNm>
<BldgNb>1234</BldgNb>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
</PstlAdr>
Hybrid - Presence of AddressLine <AND> Presence of (PostCode <OR> TownName <OR> CountrySubDivision <OR> Country)
<PstlAdr>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
<AdrLine>Bldg Num + Street Name</AdrLine>
</PstlAdr>
Example with the maximum 2 Address Line elements:
<PstlAdr>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
<AdrLine>Bldg Num + Street Name</AdrLine>
<AdrLine>Other info. Example: Floor or Suite</AdrLine>
</PstlAdr>
[Examples using 2019 schemas]
Fully Structured - Absence of AddressLine
<PstlAdr>
<Dept>Department</Dept>
<SubDept>Sub-Department</SubDept>
<StrtNm>Street Name</StrtNm>
<BldgNb>1234</BldgNb>
<BldgNm>Building Name</BldgNm>
<Flr>Floor</Flr>
<PstBx>Post Box</PstBx>
<Room>Room</Room>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<TwnLctnNm>Town Location Name</TwnLctnNm>
<DstrctNm>District Name</DstrctNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
</PstlAdr>
Hybrid - Presence of AddressLine <AND> Presence of (PostCode <OR> TownName <OR> CountrySubDivision <OR> Country)
<PstlAdr>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
<AdrLine>Bldg Num + Street Name</AdrLine>
</PstlAdr>
Example with the maximum 2 Address Line elements:
<PstlAdr>
<PstCd>98765</PstCd>
<TwnNm>Town Name</TwnNm>
<CtrySubDvsn>Country Subdivision</CtrySubDvsn>
<Ctry>GB</Ctry>
<AdrLine>Bldg Num + Street Name</AdrLine>
<AdrLine>Other info. Example: Floor or Suite</AdrLine>
</PstlAdr>
Character Set:
All proprietary and Text data elements EXCLUDING Name and Address for all actors and Related
Remittance Information and Remittance are limited to the FIN-X-Character set:
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
/ - ? : ( ) . , ' +
Space
All Name and Address for all actors, Related Remittance Information and Remittance
Information (structured and unstructured), Email Address where included as part of a proxy
element are extended to support the following additional characters:
!#$&%*=^_’{|}~";<>@[\]
< is replaced with <
> is replaced with >
In-country payments that support local language will show that additional character support in the individual Client Guides.
With regard to banks, when providing CreditorAgent or IntermediaryAgents, best practice is to use BIC only. If a non-BIC local bank ID is used, or if you choose to provide postal address, then TownName and Country are required.
Be prepared to use the Regulatory Reporting section for conveying purpose of payment and other country / currency requirements. No longer using <Unstructured> and <InstructionForDebtorAgent>
