1. Refer to the latest information available at the Swift Knowledge Centre, including Operations Guide, Service Description, Business Processing Rules and FAQ documents.
2. Understand the plans of your payment service providers like J.P. Morgan to align your plans accordingly. 
3. Have an implementation plan for fully transitioning to ISO MX messages and consider all potential operational and technology impacts. 
4. Please note that end of unstructured address deadline is November 2026, and only hybrid or fully structured address are going to be accepted by Swift after this date.
5. Develop a plan to add structured address data for your clients where they are debtor party, and work with your clients to start collecting and organizing beneficiary details in structured format. 
6. Be aware of market developments and recommendations during the implementation phase, including those related to industry truncation risks.

• As of November 2025, all payment instructions must be exchanged in the ISO 20022 MX format. Instructions sent in the MT format will be automatically converted by Swift to the MX format.
• Connection to the Swift FINPlus platform will enable Swift's In-Flow Translation service, which will allow you to receive the MX message with embedded MT message, if you are not ready to receive native MX payment messages. Please contact Swift to arrange this service,
• Check with your compliance team to understand your obligations related to enhanced data received within the MX messages.

MT9xx remains the default reporting option sent by J.P. Morgan:

• Please refer to the latest Swift communication about timeline of implementation CBPR+ messages. 
• Following Swift’s announcement extending the MT reporting deadline to November 2028 (status for March 2028) , J.P. Morgan is planning to roll out MX reporting late 2026 for clients that opt in, and will continue to use enhanced MT9xx statement and advice reporting messages as the default until further updates are provided.
• J.P. Morgan will continue to send MT9xx as the default option (note: this does not apply for serial third party credit advices where we will send pacs.008/009).
• Late 2026 you will be able to opt in to receive Cash Management messages (camt .052, .053 and .054) by contacting your J.P. Morgan representative.
• We have a camt.53 and camt.054 schema on our Swift MyStandards page, to clarify key formatting features, particularly for elements subject to interpretation. Additionally for Payment Notification camt.054 you can refer to J.P. Morgan Formatting  Guide. 

Providing enhanced information within MT9xx messages:

• Since the adoption of camt. messages is expected to take place gradually, where possible we are adapting our MT9xx messages for credits, to append useful information from MX payment transactions, leveraging CBPR+ guidelines (access to Swift resources only for registered users):
  • Providing pacs End2End ID Transaction reference as the "Related Reference" (e.g., MT910 field 21, MT940 Field 61 subfield 7) for credit transactions within the MT9xx series messages (excluding scenarios where we already customize this for clients).
  • Mapping enhanced ISO data fields from the MX messages into the MT9xx series messages where there is enough space to do so (MT910 field 72, MT940 field 86) while avoiding impact to existing reference and data mapping features.
  • Including "+" at the end of fields where possible, when data cannot be included due to insufficient space; this may apply to Related Reference, Party and Agent details and Sender to Receiver / Detailed Transaction Information fields within MT9xx series messages. 
  • These features are available for most EMEA account locations.

ISO camt message types do require an RMA. To lessen the operational impact, Swift provided an optional bootstrap event for camt.052/053/054 message types in recent years.

We strongly encourage our clients to opt-in to—taking part in the bootstrap events, this will save time and the manual effort of bilateral RMA exchanges at the point of migration. Please consult the Swift RMA Support Page for Swift plans.

A new hybrid postal address format was introduced to Swift FINPlus network in November 2025, allowing simultaneous usage of structured and unstructured elements, with structured Town Name and Country as mandatory minimum.

Please continue to follow all current local laws and regulations for payment and beneficiary address information as required. ​

Note: Financial Transactions and Reports Analysis Centre of Canada (FINTRAC ) requires full complete address that includes street number, street name, city, province or state, postal code or zip code, and country code.​

Timelines:

• Fully structured: already allowed today and preferred & recommended option in the future
• Fully unstructured: Only allowed until November 2026
• Hybrid address: Allowed as of November 2025 (no end-date)

The hybrid address format permits the concurrent use of structured elements within the Postal Address and the 'Address Line' element.

When utilizing a hybrid address, Town Name and Country are mandatory separate components within the Postal Address, similar to their requirement in a fully structured address.

The Address Line element in the postal address can consist of up to 2 lines, each containing up to 70 characters (2*70) in the Hybrid format.

It is important that the structured address information provided in the respective structured elements is not duplicated in the Address Line elements.

For details please refer to The Payments Market Practice Group (PMPG) guidelines here or here.

When sending future-value dated transactions from now until 14^th of November, with the settlement date post 14^th November 2026, please aim to include hybrid / structured address within the messages for J.P. Morgan to process these payments straight-through.

For J.P. Morgan approach for Hybrid Address in bank electronic channels and impact on Corporate clients initiating payments, please check here.

J.P. Morgan will continue to accept Swift MT210 messages until 2028 (in line with the Swift roadmap) in account locations where those messages are accepted today. J.P. Morgan accepts camt.057 messages instead of MT210 messages in those account locations; however, note only single camt.057 messages are accepted and not multiple advices within the same message.

For returned payments, where  possible, we will provide return reason information as well as  the most relevant reference information to clients (i.e., their original debit or credit references) to aid reconciliation and onward processing.

Information on our camt. 052/3/4 message formatting is provided within our camt.053 and camt.054 schema, on our Swift MyStandards page.

Other details: J.P. Morgan is now sending pacs.004 for returning settled payments. Clients wishing to receive these messages in MT format can do so by using the Swift in-flow translation service.

Clients can use pacs.004 message to initiate return messages via J.P. Morgan although it is also acceptable to continue using MT with /RETN/ codewords, or even initiate the return as a new payment.

Please reference the ISO codes for returns messages, as per industry guidelines.

For CBPR+ transaction legs, J.P. Morgan will initially issue recalls and rejections and respond to incoming requests (including incoming camt.056 FI to FI Cancellation message) using existing MT message types and practices. We will start sending the camt.056 and camt. 029 (Resolution of Enquiry) messages as industry adoption increases.

Similarly, J.P. Morgan will continue to use the MT199 in most instances to reject payment requests for CBPR+ transaction legs and will start sending the pacs.002 negative Customer Status Report as industry adoption increases.

As per recent Swift announcement, Swift is postponing the mandate to exchange all payment cancellation messages via the Stop and Recall Process (SRP) to November 2027. ​

As a result, all payment cancellation messages (including CCT) can continue to be exchanged bilaterally in both MT and ISO 20022 formats until November 2027. Stop and Recall will continue to be available to Case Management and GPI participants.  ​

 ​For details, please refer to  KB article​

We do not plan to send (or receive) any optional pacs.002 positive or pending status reports in the future.

We're working hard to ensure the services driven by bilaterally agreed codewords for data patterns continue working seamlessly for clients moving to MX messages. If this applies to you and you would like more information, please refer to our Frequently Asked Questions. For more information on formatting bilaterally agreed codewords within the pacs.008 and 009 schemas, please refer to J.P. Morgan's Swift MyStandards schemas on Swift‍.‍com. If you require further clarification or need access to J.P. MyStandards, please contact your J.P. Morgan representative.

• Check our testing guide, it aims to provide our clients with a useful reference point for their CBPR+ readiness, expanding on J.P. Morgan’s lessons learned as an industry leader in ISO 20022 adoption.
• Reference the Swift MyStandards schemas and the CBPR+ sample message library on Swift.com
• Access J.P. Morgan's Swift MyStandards schemas on Swift.com (currently available for pacs.008, pacs.009, and camt.054 and camt.053) which identifies how to populate bilaterally agreed codewords and indicators in the new schemas. (You will need to request access to this user group on Swift.com)
• Use Swift’s Sparring Partner tool, which may reduce the need for bilateral testing between Swift members. (For more information on this tool, please contact your Swift representative.) 

The end of coexistence for MT101 messages is due by 14^th of November 2026, with all client migrations to be completed ahead of this date. As per Swift changes all Swift members involved in CBPR+ migration are required to be ready to receive the pain.001 v9 bank to bank messages since November 2025 (SR2025).

J.P. Morgan adopted the CBPR+ pain.001 v9 bank to bank message and is able to receive from November 2025, on a send basis Q4 2026, and a relay date to be confirmed.

In addition to this, using a risk based approach, J.P. Morgan has decided it will not require a specific pain.001 bilateral agreement.

End of coexistence for MT101 message is due end of November 2026, with all client migrations to be completed ahead of that milestone.

J.P. Morgan will initiate charge claims via MT191 and CAMT.106, and J.P. Morgan accepts incoming camt.106. and MT191 charge claims. 

J.P. Morgan's Gateway service enables us to capture a Client’s Fedwire- or CHIPS-initiated transactions through J.P. Morgan and complement those transactions with value-added services and products.

As the Federal Reserve Bank adopted the ISO 20022 message format for the Fedwire Funds Service, clients should adhere to the Federal Reserve's formatting guidance to participate in the Fedwire service.

J.P. Morgan’s Gateway service is fully capable of supporting the ISO 20022 message format with no special or additional formatting requirements to maintain its current functionality.

CLS USD Nostro Services

• J.P. Morgan will accept CLS USD Nostro Pay-ins via pacs.009 (using the CLSTIME element - <SttlmTmReq> <CLSTm>) or Instructions for Next Agent containing the CLS codeword and time.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLS Third Party Service

• Drawdowns used for the CLS Third Party Service will continue to be sent in MT format until further notice.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLSNow

• J.P. Morgan will accept payments via pacs.009; please use existing codewords in Instructions for Next Agent.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLSCCP

• J.P. Morgan will accept payments via pacs.009; please use existing codewords in Instructions for Next Agent.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

• J.P. Morgan will liaise with each clearinghouse to discuss individual clearinghouse migration plans. To note that drawdowns will now be sent via pacs.010 messages and payments will be sent via pacs.009.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

• J.P. Morgan will liaise directly with SwapAgent to discuss migration plans.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

• ISO 20022 Payments Migration and Interoperability Considerations
• Best Practice Guidelines for the Payment Industry Migration to ISO 20022 (published January 2022) (launches download)
• PMPG Industry Guidance on the introduction of the Hybrid Postal Address 

These guidelines for banks have been developed by CBPR+ to manage potential risks where enhanced data elements are truncated or dropped altogether at some point in the payment chain.

Truncation during Market Infrastructure transaction legs:

The industry guidance may also be applied to a transaction leg settled across a local Market
Infrastructure (i.e., currency clearing systems) that has not yet adopted the ISO 20022 standard.

CHIPS migrated to ISO 20022 on April 2024, and has made provisions to allow ISO-enabled data from CBPR+ messages to be passed between clearing participants from March 20, 2023.

FED migrated to ISO 20022 on July 14th, 2025.

1. FED: cut-off times
   The FED is strictly enforcing their cutoff time for 3rd party payments at 6.45 p.m. EST. Payments received after cut-off time will be held for next business day processing.
2. FED: IRS formatting guidelines
   It is necessary that IRS Tax Payments are formatted according to their specific guidelines. Please refer to IRS Tax payments section of the FED guidelines, including the name and address (access to Swift resources is for registered users only) or recent FED communication.
3. Changes to Postal Address Data Validation
   In the Federal Reserves November 2025 Newsletter and currently on their website, The Fed confirms the intention to remove fully unstructured Postal address in favor of a single hybrid postal address for all parties and agents across all message types.

              ISO 20022 2025 Releases

              October 2025 ISO 20022 Newsletter

TARGET2 and EURO1 migrated to the new standard on March 20, 2023.

ECB announced earlier start times for TARGET2 and EURO1 settlement processing. As of March 20, 2023, both TARGET2 and EURO1 began settlement processing at 02:30 CET, instead of 07:00 CET for TARGET2 and 07:30 CET for EURO1. This means clients may receive inbound clearing credits from 02:30 CET onwards.

Also, TARGET2 will no longer accept unpublished 11-digit BICs within payment messages. This includes 11-digit BICs of valid 8-digit BICs.

• To ensure payment messages sent to J.P Morgan containing unpublished 11-digit BICs can still be settled through TARGET2, where we’re able to identify such instructions, the associated outbound payment message will be sent using the corresponding 8-digit BIC.
• Clients who want to continue using unpublished 11-digit BICs within payments settled via TARGET2 should take steps to publish the BICs with Swift.

Effective May 1, 2025, the Bank of England (BoE) has mandated the use of enhanced data fields in CHAPS payment messages.

As of May 1, 2025, CHAPS payments need to include:

Legal Entity Identifier (LEI) - for CHAPS payments between financial institutions

Purpose Code (PoP) - for CHAPS payments between financial institutions; only relating to property transactions

J.P. Morgan has updated technology, processes and procedures to meet the requirements of this mandate.

Clients using the ISO 20022 message format are encouraged to incorporate these elements more broadly in their UK payment instructions. Although payments lacking LEI or PoP will not be immediately rejected, BoE reserves the right to change its policy in the future.

The Bank of England have communicated plans to mandate Purpose Code (PoP) for ALL CHAPS payments instructed via JPM access channels (i.e. excluding Swift) from the second half of 2027.  

For more details please visit Bank of England announcement here.

This the link to Bank of England ISO 20022 landing page

The Bank of England has announced earlier start times for CHAPS settlement processing, targeted for September 2027. Settlement will be enabled from 01:30 GMT, under an optional participation model. This means clients may receive inbound clearing credits from 01:30 GMT onwards.

For more details please visit Bank of England announcement here.

The Philippine Payment and Settlement System (PhilPaSS) migrated to the new standard in July 2021.

The MAS Electronic Payment System (MEPS+) migrated to Like for Like (L4L) ISO messages in August 2022.

The Bank of Thailand Automated High-value Transfer Network (BAHTNET) migrated to the new standard in August 2022.

The Real Time Electronic Transfer of Funds and Securities (RENTAS) system migrated to the new standard in September 2022.

SAMOS migrated to the new standard in September 2022.

The High Value Clearing System (HVCS) migrated to the new standard in March  2023.

The New Zealand  High Value Clearing System migrated to the new standard in March  2023.

The Japan Foreign Exchange Yen Clearing System (FXYCS) ISO 20022 messages updated its standards to Version 8 in November 2025, compatible with CBPR+.

The Hong-Kong Dollar Clearing House Automated Transfer System (CHATS) migrated to the new standard in April 2024.

Lynx, Canada’s high-value payment system introduced ISO 20022 in 2023 with full transition effective November 2025.

Under Canada's Proceeds of Crime (Money Laundering) and Terrorist Financing Act and related regulations, all Canadian financial institutions including J.P. Morgan must collect complete remitter and beneficiary information for wires sent in SWIFT MT101, pacs.008 and pain .001 formats. To comply, J.P. Morgan requires complete remitter and beneficiary information on all wire payments sent or received through your accounts with us in Canada.

Complete remitter and beneficiary information includes: full account name, full account number, beneficiary bank’s SWIFT BIC (or the bank’s full name and address), and the beneficiary’s full physical address. A full physical address must include: street number or building name, street name, city or town, state or province (mandatory where applicable, e.g., Canada, USA, Australia), and country, preferably in the 2 character ISO format. Note: A P.O. Box is not acceptable without a full physical address. Some Canadian banks may require the Canadian Clearing code to avoid processing delays, and some may require that the beneficiary account number be prefixed by a transit code. Check your payees’ standard settlement instructions to confirm requirements.

Financial institutions may reject or delay your wires if the required information is not provided or if the address information does not include a full physical address. J.P. Morgan will reject wire payments with incomplete remitter or beneficiary information.