Category 1: Customer payments and cheques
MT102 STP Multiple Customer Credit Transfer (STP)
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
Retired in the 2025 standards release: no longer sent on the Swift network.
The MT102 STP was the straight-through variant of the MT102: several customer credit transfers in one message, with fewer letter options and stricter validation triggered by the code STP in field 119 of the user header. Swift removed it from the FIN network on 22 November 2025.
- Message type
- MT102 STP
- Category
- 1
- Status
- Retired (SR 2025)
- ISO 20022
- No direct equivalent
What MT102 STP is used for
Compared with the MT102 it allowed only option A for the ordering institution (52A) and the account with institution (57A), dropped field 51A, limited field 23 to CREDIT and SPAY, made the beneficiary account line mandatory and did not allow /REJT/, /RETN/ or ERI in field 72, so that the receiving bank could process each payment automatically.
Bank notices list the MT102 STP with the MT102, MT103 REMIT, MT201 and MT203 as payment messages rejected by the network since 22 November 2025, without conversion to ISO 20022.
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 STP 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
No replacement message: the withdrawn MT102 STP is not substituted with an ISO 20022 message. Each payment is sent as its own pacs.008.
All MT messages · Category 1 messages · ISO 20022 messages · Codes · Troubleshooting