Can I still send an MT102?

Not between financial institutions on the Swift FIN network: since 22 November 2025 it is rejected (NAKed) and not converted. Send each payment as a pacs.008, or as an MT103 that Swift converts under its chargeable contingency processing.

What replaces the MT102 in ISO 20022?

There is no bulk replacement in CBPR+: the pacs.008 carries one transaction per message there, so each payment of the old batch becomes its own pacs.008.

Category 1: Customer payments and cheques

MT102 Multiple Customer Credit Transfer

Written and maintained by ZagTrader. Last reviewed 21 October 2026. How this page is sourced and checked

Retired in the 2025 standards release: no longer sent on the Swift network.

The MT102 carried several customer credit transfers in one message from the ordering customers’ bank to another bank, under a bilateral or multilateral agreement covering amount limits, currencies and settlement. Each payment had its own sequence B, and sequence C settled the total. Swift removed it from the FIN network on 22 November 2025.

Message type: MT102
Category: 1
Status: Retired (SR 2025)
ISO 20022: No direct equivalent

What MT102 is used for

Its structure was a general sequence A, a repeating sequence B with one occurrence per beneficiary, and a settlement sequence C with the total in field 32A. Use required registration in its Message User Group, and an STP variant (MT102STP) existed with the code STP in field 119.

Public bank notices (BNY, Citi) list the MT102 among the payment messages that the network NAKs since 22 November 2025, with no conversion to ISO 20022. Each payment now goes as its own pacs.008, which in CBPR+ carries one transaction per message. The same notices say messages exchanged in SCORE and in closed user groups run by market infrastructures were not covered by that change for the time being.

Withdrawn from the Swift FIN network on 22 November 2025, when MT/MX coexistence for payment instructions ended: the network now rejects (NAKs) it instead of delivering it, and Swift does not convert it to ISO 20022.

Sent by: The ordering customers’ bank
Sent to: Another bank that agreed to receive bulk payments

Fields

This is a catalogue entry: the field-by-field structure is not shown here because we publish structures only where we have checked them against public sources.

ISO 20022

Swift did not provide a replacement: bank notices state that the withdrawn MT102 is not substituted with an ISO 20022 message. Each payment is sent as a separate pacs.008.

MT102 questions

Can I still send an MT102?: Not between financial institutions on the Swift FIN network: since 22 November 2025 it is rejected (NAKed) and not converted. Send each payment as a pacs.008, or as an MT103 that Swift converts under its chargeable contingency processing.
What replaces the MT102 in ISO 20022?: There is no bulk replacement in CBPR+: the pacs.008 carries one transaction per message there, so each payment of the old batch becomes its own pacs.008.

All MT messages · Category 1 messages · ISO 20022 messages · Codes · Troubleshooting