Voir iotafinance en FrançaisYou are viewing the English version of iotafinance.comIotafinance auf Deutsch sehen
Icon for pthe ractical information section

SWIFT ISO15022 Standard
Detail view for message MT102.STP - Multiple Customer Credit Transfer

icon of the financial acronyms app for iOS

Financial acronyms

The entire acronym collection of this site is now also available offline with this new app for iPhone and iPad.

 Description of the message MT102.STP

The MT 102 STP allows the exchange of multiple customer credit transfers using a restricted set of fields and format options of the core MT 102 to make it straight through processable. The MT 102 STP is a compatible subset of the core MT 102 that is documented separately in this section.

The differences with the core MT 102 are:

  • appropriate MT 102 STP format validation is triggered by the code STP in the validation flag field 119 ({3:{119:STP}}) of the user header of the message (block 3)
  • fields 52 and 57 may only be used with letter option A
  • field 51A is not used in MT 102 STP. This message may only be used on the FIN SWIFT network since it requires special validation
  • field 23 may only contain codes CREDIT and SPAY
  • subfield 1 (Account) of field 59a is always mandatory
  • field 72, code INS must be followed by a valid financial institution BIC
  • field 72, codes REJT/RETN must not be used
  • field 72 must not include ERI information.

 Purpose of the message MT102.STP

Conveys multiple payment instructions between financial institutions

 Scope of the message MT102.STP

This message is sent by or on behalf of the financial institution of the ordering customer(s) to another financial institution for payment to the beneficiary customer.

It requests the Receiver to credit the beneficiary customer(s) directly or indirectly through a clearing mechanism or another financial institution, or to issue a cheque to the beneficiary.

This message is used to convey multiple payment instructions between financial institutions for clean payments. Its use is subject to bilateral/multilateral agreements between Sender and Receiver.

Amongst other things, these bilateral agreements cover the transaction amount limits, the currencies accepted and their settlement. The multiple payments checklist included below is recommended as a guide for institutions in the setup of their agreements.

  Structure of the message MT102.STP

Sequence A - General information  [ mandatory, nonrepetitive ]
No.
Tag
Option
Name
Status
1
20 
 
File Reference
M
2
23 
 
Bank Operation Code
M
3
50a
A
Ordering Customer
C
 
 
F
 
 
 
 
K
 
 
4
52A
 
Ordering Institution
C
5
26T
 
Transaction Type Code
C
6
77B
 
Regulatory Reporting
C
7
71A
 
Details of Charges
C
8
36 
 
Exchange Rate
C
Sequence B - Transaction Details  [ mandatory, repetitive ]
No.
Tag
Option
Name
Status
9
21 
 
Transaction Reference
M
10
32B
 
Transaction Amount
M
11
50a
A
Ordering Customer
C
 
 
F
 
 
 
 
K
 
 
12
52A
 
Ordering Institution
C
13
57A
 
Account With Institution
O
14
59a
 
Beneficiary Customer
M
 
 
A
 
 
 
 
F
 
 
15
70 
 
Remittance Information
O
16
26T
 
Transaction Type Code
C
17
77B
 
Regulatory Reporting
C
18
33B
 
Currency/Instructed Amount
C
19
71A
 
Details of Charges
C
20
71F
 
Sender's Charges
C
21
71G
 
Receiver's Charges
C
22
36 
 
Exchange Rate
C
Sequence C - Settlement Details  [ mandatory, nonrepetitive ]
No.
Tag
Option
Name
Status
23
32A
 
Value Date, Currency Code, Amount
M
24
19 
 
Sum of Amounts
O
25
71G
 
Sum of Receiver's Charges
C
26
13C
 
Time Indication
O
27
53a
A
Sender's Correspondent
O
 
 
C
 
 
28
54A
 
Receiver's Correspondent
O
29
72 
 
Sender to Receiver Information
O