Edit

FIN Response Reconciliation

  • Article

The FIN Response Reconciliation (FRR) feature of A4SWIFT reconciles a FIN response with the corresponding original message sent by A4SWIFT. This establishes the status of the original message, and enables A4SWIFT to take steps based upon that status. Without reconciliation, this would not be possible. A4SWIFT would know that it successfully (or unsuccessfully) sent the original message to SAA, and it would have the response that it received from SAA, indicating the status of the transmission, but it would not be able to make the connection between the two. FRR establishes that connection.

FIN responses are acknowledgments (ACKs) or negative acknowledgments (NAKs) sent by SAA to A4SWIFT, or sent by the SWIFT network to SAA and then forwarded by SAA to A4SWIFT. The presence or absence of these acknowledgments defines the business status of the message. You can monitor this status through Business Activity Monitoring (BAM) reporting.

You can also implement custom application behavior around FRR. A custom handler can implement your own logic for handling reconciled sets of FIN responses. For an example of a custom handler that processes messages that FRR has correlated with a MTS21_FIN_ACKNAK NAK message, see FRR NAK Handler Sample.

The FRR orchestration is installed by default by the A4SWIFT setup program. You need to configure the FRR system by creating a receive pipeline, receive locations, and send ports. You also need to configure FRR to specify how long it should wait for delayed NAKs, and for responses in general. For more information about FRR configuration and administration, see Configuring FIN Response Reconciliation and Administering FIN Response Reconciliation.

This section contains: