FIN message transfer services

The following FTM SWIFT services can be used to process FIN messages:
SIPN FIN service

This service sends outbound messages from a SWIFTNet FIN application to an SAG for transport over the SIPN to another FIN user or to the FIN system. It also delivers inbound messages received from another FIN user or from the FIN system to a SWIFTNet FIN application. It consists of the following flows:

  • The SIPN FIN Send message flow of this service sends a message from a client application to a specific recipient. Error messages or intermediate responses from the FIN Send message flow are placed into the reply queue specified in the corresponding request.
  • The SIPN FIN acknowledgment message flow processes an inbound SWIFT acknowledgment (ACK/NAK) and generates an FTM SWIFT message to hold it. This message is placed into the reply queue specified in the request to which the acknowledgment refers. The acknowledgment is always contained in a reply message that the flow sends to the reply queue which is specified in the MQMD header of the outbound message. The correlation identifier in the MQMD header of this reply message is the message identifier of the outbound message.
  • The SIPN FIN Receive message flow processes any other inbound SWIFT message and generates an FTM SWIFT message to hold it. This message is placed into the output queue associated with the logical terminal (LT) to which the SWIFT message is addressed. This queue is specified by attributes Queue and QueueManager of CT DnfLTApplicationSettings during configuration of the FIN LT.
Note: An organization that acts as a FIN Copy central institution must provide an application to receive each FIN Copy to Central Institution Message (MT096) and, if operating in Y-Copy mode, to generate a FIN Copy Message Authorisation/Refusal Notification (MT097). FTM SWIFT authenticates each message using on PKI signatures and their digests.

When operating in Y-Copy mode, a FIN Copy application must respond to each MT096 message with an MT097 message. The MT097 message must contain the message-reference field (MRF) of the original user. This field is specified in the MT096 message.

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 reference data of such unanswered MT096 messages.

Financial Message transfer service for FIN messages (FMT FIN service)
This service stores outbound messages from a SWIFTNet FIN application in local processing tables for transport to another FIN user and delayed NAK messages (MT015).
  • The FMT FIN Send message flow of this service or the SIPN FIN Send message flow send a message from a client application to a specific recipient on the same FTM SWIFT instance without transfer over SIPN. Error messages or intermediate responses from the FIN Send message flow are placed into the reply queue specified in the corresponding request.
  • The SIPN FIN acknowledgment message flow processes the generated acknowledgment in SWIFT format (ACK/NAK) and generates an FTM SWIFT message to hold it. This message is placed into the reply queue specified in the request to which the acknowledgment refers. The acknowledgment is always contained in a reply message that the flow sends to the reply queue which is specified in the MQMD header of the outbound message. The correlation identifier in the MQMD header of this reply message is the message identifier of the outbound message.
  • The SIPN FIN Receive message flow processes generated inbound message in SWIFT format and generates an FTM SWIFT message to hold it. This message is placed into the output queue associated with the logical terminal (LT) to which the SWIFT message is addressed. This queue is specified by attributes Queue and QueueManager of CT DnfLTApplicationSettings during configuration of the FIN LT.
If so configured, these services:
  • Perform access control checks
  • Store a copy of the message in the audit database
  • Create an entry for the message in the message warehouse
  • Validate the message
  • Authenticate the message
  • Count the message
For more information about these functions, see Managing FTM SWIFT data.

Message flows

Table 1 lists the FIN services and their message flows.
Table 1. FIN services and their message flows
Service Description Message Flow
SIPN FIN Send flow DNF_ILC_FIN
Acknowledgment flow DNF_ILS_ACK
Receive flow DNF_ILS_FIN
FMT FIN Send flow
DNF_PF_IS
DNF_ILC_FIN
Acknowledgment flow DNF_ILS_ACK
Receive flow
DNF_PF_IR
DNF_ILS_FIN
Note: For simplification, the terms FIN Send message flow, FIN Receive message flow, and FIN acknowledgment message flow are used throughout this section instead of the message flow names.

Interface queues

  • For the SIPN FIN service 
    instance.ou.DNF_ILC_FIN
  • For the FMT FIN service: 
    instance.ou.DNF_ILC_FIN
instance.ou.DNF_PF_IS
    Note: When FMT FIN capability was configured:
    • The SIPN FIN service is able to send FIN messages via the SIPN as before, but is also able to send FIN messages internally. The path taken by a particular message depends on its contents:
      • If the message type and FIN service name correspond to values configured for the destination (BIC8), or if the FMT flag is set in the RFH2 of the message, the message is sent internally.
      • Otherwise, the message is sent via the SIPN.
      Applications that currently use the SIPN FIN service can continue to run unchanged. In this case the service interface queue is 
      instance.ou.DNF_ILC_FIN
    • The FMT FIN service sends FIN messages internally, regardless of the message contents. Applications that are to send all messages internally can use this service and service interface queue 
      instance.ou.DNF_PF_IS

Process

The Send message flow:
  1. Retrieves an outbound message from the input queue of the FIN Send message flow.
  2. Performs access control, if enabled.
  3. Records the message for auditing purposes and stores it in the message warehouse database table, if enabled.
  4. Validates the contained SWIFT message, if enabled.
  5. If requested, the SIPN FIN and FMT FIN services calculate CHK and TNG trailers, and add them to the SWIFT message.
  6. The SIPN FIN and FMT FIN services also calculate message and FIN Copy digests.
  7. The FMT FIN service also performs ISN-OSN-transformation and generates resulting OSN and ACK messages.
  8. In addition, a delayed NAK message is generated if all of the following conditions are met:
    • The message is sent from another instance.
    • The message is not allowed to be received.
    • The sending SWIFTNet FIN application requested to get a delayed NAK.
    • The receiving destination is allowed to send delayed NAK messages.
  9. Checks whether the following conditions are met:
    • The receiving LT stated in the application header of the FIN message is configured as FMT destination. This requires that the following attributes be set for the OU: 
      add -ou <ou> -ct DnfFmtfDestination -co <BIC8_rec_LT>
add -ou <ou> -ct DnfLTMap -co <BIC9_rec_LT> -attr OU -val <OU_rec_LT>
      where:
      BIC8_rec_LT
      BIC8 of receiving LT. This CO must exist.
      BIC9_rec_LT
      BIC9 of receiving LT
      OU_rec_LT
      OU, where receiving LT is configured and must be configured in DNFSYSOU.
    • The receiving FMT destination is configured as enabled. This requires that the following attribute is set for the OU: 
      add -ou <ou> -ct DnfFmtfDestination -co <BIC8_rec_LT> attr enabled
      where:
      BIC8_rec_LT
      BIC8 of receiving LT. This CO must exist.
    If not, the message cannot be processed.
  10. If the message was put in a queue with a name of the form instance.ou.DNF_PF_IS, it sends the message via FMT unconditionally. If the message was put in a queue with a name of the form instance.ou.DNF_ILC_FIN, it sends the message via FMT only if either of the following is true:
    • The value of the Dnf.FIN.FMT.Mode element is set to forced.
    • All of the following conditions are met:
      • The FMT FIN service is enabled for the OU of the sending LT. This requires that the following attribute is set for the OU: 
        add -ou <ou>
    -ct DnfFinParametersSnfil
    -co DnfFinParametersSnfil
    -attr FmtFinSendingEnabled
      • The message is of a message type that is assigned for FMT for the FMT destination (optional). If not, the message is sent via the SIPN.
      • If the message type requires a service name (field: 103, for example, for copy services), special services can be explicitly assigned to FMT. If not, the message is sent via the SIPN.
  11. Generates and sends a reply message as an intermediate response to the sending application, if requested.
  12. Transforms the message and routes it to the recipient.

Errors

The Dnf.FIN.Completion.ReasonList.Reason.Value field can contain one of following reason codes:
  • DNFH3712E
  • DNFH3713E
  • DNFH3750E
  • DNFH3752E
  • DNFH3753E
  • DNFH3754E
  • DNFH3755E
  • DNFH3756E
  • DNFH3758E
  • DNFH3760E
  • DNFH3761E
  • DNFH3762E
  • DNFH3763E
  • DNFH3764E
  • DNFH3790E
  • DNFH3792E
  • DNFH3799E
  • DNFH3821E
  • DNFH3860E
  • DNFH3861E
  • DNFH3862E
  • DNFH3865E
  • DNFH3958E
  • DNFH3959E
  • DNFH3960E
  • DNFH3961E
  • DNFH3970E
  • DNFP9420E
  • DNFL9430E
  • DNIY5000E to DNIY5199E
See Codes for the accompanying message text and for additional error messages that could be issued.