Background
In 2018, SWIFT launched the Cross Border Payments & Reporting Plus (CBPR+) programme to migrate existing MT 1xx, 2xx and 9xx interbank messages to the MX/XML standards already used in SEPA. All MT payment, reporting, investigation and related formats must transition to the corresponding PACS, CAMT and PAIN messages. SWIFT adopted a phased approach, prioritising the migration of PACS messages.
Since 22 November 2025, MT payment instructions such as MT103, MT200 and MT202(COV) have been replaced by their PACS equivalents (PACS.008 and PACS.009(COV)) on SWIFT’s FINplus service. As a temporary fallback, SWIFT offers an MT to MX conversion service for institutions unable to migrate in time. Although this service applies additional validation rules, it allows financial institutions to continue sending MT messages, which SWIFT will convert to the appropriate PACS format. ING has been fully MX-ready since November 2025 and does not rely on this service.
In September 2025, SWIFT published an updated roadmap defining new end dates for remaining CBPR+ message categories, including payment initiation, exceptions and statements. The figure below summarises the updated roadmap, followed by additional detail on each milestone.
Scope of CBPR+ messages migrating to ISO 20022 with end-of-coexistence dates
Please find more information in this Opens in a new tabOpens a pdfCBPR+ roadmap.
Mandatory migration 2026
| MX pay initiation format (FINplus)* | MT equivalent (FIN) | Description | Swift timeline |
|---|---|---|---|
| No MX equivalent | MT101 (multiple) | (interbank) Request for Transfer (multiple) | Will be removed when migrating to PAIN.001 |
| pain.001 (.001.09) | MT101 (single) | (interbank) Customer Credit Transfer Initiation | Available upon request, migration is ongoing. Compliance date as per the Swift CBPR+ guidance: November 14, 2026. |
| pain.002 (.001.10) | No MT equivalent | (interbank) Customer Payment Status Report | Available upon request in several ING entities (opt in). Compliance date as per the Swift CBPR+ guidance: November 2027. |
| camt.055 (.001.08) | MT192 | Customer Payment Cancellation Request | Available upon request in several ING entities (opt in). Compliance date as per the Swift CBPR+ guidance: November 2027. |
| camt.029 (.001.09) | MT196 | Resolution Of Investigation | Available upon request in several ING entities (opt in). Compliance date as per the Swift CBPR+ guidance: November 2027. |
*To prevent any repairs or rejections during the processing of your payment instruction messages, please ensure adherence to the SWIFT formatting guidance and the ING formatting recommendations mentioned in the Interbank Payment Initiation Guidelines - CBPR+. (Swift account needed)
ING’s MX readiness and product offer
- PAIN.001
According to the Swift CBPR+ guidance, interbank MT101 Request-for-Transfer message will be discontinued by 14 November 2026 and will be replaced with CBPR+ pain.001 (v9) message format. ING is migrating FI counterparties to ISO 20022 MX CBPR+ pain.001.001.09 ahead of the deadline. This ensures there is no expected impact on our corporate clients or on the current remote initiation service, which allows debiting their account in ING or initiating payments from accounts opened in counterparty financial institutions via ING channels.
ING acceded to the Opens in a new tabSwift Rulebook for Payment Initiation Relay in its most recent applicable and published version, as updated from time to time.
Steps to Migrate from FIN MT101 to FINplus pain.001:
- ING initiates migration by BIC, starting with the INGBNL2A incoming flow (ongoing).
- ING shares its Usage Guidelines via MyStandards, which can be accessed by FI counterparties here: Interbank Payment Initiation Guidelines - CBPR+. (Swift account needed)
- Counterparty requirements include:
- Accession to the Swift ISO 20022 Payment Initiation Relay Rulebook.
- Presence of BIC11 in the Swift directory: ISO 20022 Payment Initiation Relay Rulebook.
- Exchange of the ING Code of Conduct.
- Message format testing, including Swift MyStandards and penny tests if needed.
- FINplus RMA setup for pain.001/pain.002 and camt.055/camt.029 (if confirmed on the counterparty side) serves as the final stage prior to production message exchange.
- PAIN.002
Pain.002 (Customer Payment Status Report) is used to report the status of a payment.
According to the Swift CBPR+ guidance, adoption of ancillary messages (pain.002, camt.29/camt.055) is subject to bilateral agreement but must be completed by November 2027. ING targets readiness (negative status only) by November 2026. Timelines differ per ING BIC.
- CAMT.029, CAMT.055
Camt.055 (Customer Payment Cancellation Request) is used to request cancellation of a payment.
Camt.029 (Resolution of Investigation) is used to report the outcome of a cancellation request.
According to the Swift CBPR+ guidance, adoption of ancillary messages (camt.29, camt.055) is subject to bilateral agreement, but must be completed by November 2027. ING targets readiness by November 2026. Timelines differ per ING BIC.
More information on the above topics can be found on the page: FAQ Swift ISO 20022.
- PACS
ING is fully incoming and outgoing PACS capable and had migrated the vast majority of its outgoing payment traffic to PACS in March 2023 already.
| MX pay format (FINplus) | MT equivalent (FIN) phased out - 22 November 2025 | Description | Swift timeline |
|---|---|---|---|
| PACS.008 | MT103 | Customer Credit Transfer | Available on FINplus since March 2023 |
| PACS.009 | MT200/202 | Financial Institution Transfer | Available on FINplus since March 2023 |
| PACS.009 COV | MT202 COV | Financial Institution Transfer Cover | Available on FINplus since March 2023 |
| PACS.004 | MT103/202 RETURN | Return of Funds | Available on FINplus since March 2023 |
| PACS.002 | No MT equivalent | Status Report Message | Available on FINplus since March 2023 |
- CAMT
CAMT reporting formats – SWIFT has recently updated the timelines for MX CAMT reporting implementation. As of November 2027, it is mandatory to receive CAMT statements from (non) supervised financial institutions (SUPE and NOSU clients). As of November 2028, the MT (FIN)/CAMT (FINplus) coexistence periods ends and CAMT will be the only format allowed for payment reporting.
ING is currently able to offer CAMT MX reporting services to Financial Institutions loro account holders in several of its entities for the intraday and end-of-day reporting. Many of our entities offer an extended like-for-like MX report which means the CAMT contains the same attributes found in the MT report but is enriched with some key additional MX references for convenience (e.g. UETR, E2E ID).
These MX reporting services are available on an opt-in basis and, when enabling CAMT for a client (per BIC), the existing FINplus RMA needs to be updated. We highly advise organising basic testing upfront where reconciliation validation on the client side should be included. Please reach out to your ING Relationship Manager if you are interested in enabling and/or testing our new CAMT services.
More information on ING’s readiness for CAMT can be found in the table below or on the Swift website:
| MX reporting format (FINplus) | MT equivalent (FIN) phased out - November 2028 | Description | Swift timeline |
|---|---|---|---|
| CAMT.052 (v8) | MT941/942 | Balance/Interim Transaction report | Available upon request in several ING entities (opt in) |
| CAMT.053 (v8) | MT940/950 | End of day Customer/Bank Statement | Available upon request in several ING entities (opt in) |
| CAMT.054 (v8) | MT900/910 | Confirmation of Debit/Credit | Available upon request in several ING entities (opt in) |
See also this Opens in a new tabStandards MT November 2025 – Standards Release Guide. (Swift account needed)
General note on the CBPR+ scope
The following guidelines on scoping can be found on swift.com:
CBPR+ aims at migrating cross-border payments and cash reporting messages on the Swift network used in the interbank space. This includes all messages exchanged between FIs (Swift Financial type), with Supervised and/or Non-Supervised user categories (SUPE and NOSU). MT message exchanges in the Swift for Corporates (SCORE) service will continue as they are for the foreseeable future. Closed User Groups operated by non-Swift entities (i.e. Payment Market Infrastructure Closed User Groups) will continue as they are for the foreseeable future. Other categories of MT messages (e.g. MT 3xx, 5xx) won’t be impacted and can therefore still be used after the end of coexistence.
Corporate entities are not subject to the CBPR+ initiative of SWIFT. However, if a question on certain topics/messages arise, please reach out to your ING Relationship Team.