MT 102 STP Multiple Customer Credit Transfer

Note:

The use of this message type requires Message User Group (MUG) registration.

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 either field 59a 59 or 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.

IMPORTANT:

To trigger the MT 102 STP format validation, the user header of the message (block 3) is mandatory and must contain the code STP in the validation flag field 119 ({3:{119:STP}}).