FINCopy or FINInform for a central institution

An organization that acts as a FINCopy or FINInform central institution must provide an application to receive each Service Message (MT096) and, if operating in Y-Copy mode, to generate a Central Institution Response (MT097).

When operating in Y-Copy mode, the central institution must provide an application to respond to each MT096 message with an MT097 message. The authentication data that FTM SWIFT calculates for an MT097 message, that is, FINCopy digest 2, are based on a copy of the MT096 message that FTM SWIFT stores in its FINCopy authentication (FCA) table. The MT097 and MT096 messages are correlated using the original-usermessage-reference field, which is contained in both messages. As a result, the application does not need to include data from the MT096 in the MT097 message.

The MT097 message is signed using a signer DN that is specified for each combination of FINCopy service, type of FINCopy service (live or T&T), and LT connection number. For more information about LT connections, see LT connections. For a description of how to configure the signer DNs used by a central institution for FIN Y-Copy, see Configuring signer DNs for FIN Y-Copy.

An application might decide not to respond to an MT096 message, for example, because it contains a possible duplicate indicator (PDE or PDM). FTM SWIFT periodically purges the FCA of all records for such unanswered MT096 messages by deleting all records for which an expected response was not received.