Possible duplicate message (PDM)

During an SnF transfer, if SWIFT encounters a problem while delivering a message or file from an SnF queue to the MSIF transfer service, it can resend the corresponding request primitive with a PDMHistory indication. When the MSIF transfer service receives such a primitive, it attempts to automatically recover the original scenario. The TimeToRecover SAG communication option specifies the interval during which the MSIF transfer service automatically attempts to recover the scenario. For more information, see the description of the TimeToRecover option in SAG communication options: SagCommOptions.

For message transfers you can specify, for each receive option-set CO (that is, each CO of type DnfEfaMsgReceiveOptionSet), whether duplicate transfers are to be allowed for the scenarios that use that CO.

Duplicate transfers are allowed for PDMs

All inbound message transfers are accepted and a reason code indicating that the transfer is a possible duplicate is passed to the receiving application:

For a message transfer, the MSIF transfer service includes message DNFO2626I in the MsgReceived notification.

Duplicate transfers are not allowed for PDMs

If the MSIF transfer service determines that a transfer is a duplicate:

For a message transfer, the MSIF transfer service accepts the duplicate message, but does not deliver it to the application.

For file transfers these configuration options are not available yet, and MSIF does not deliver duplicate transfers to the application.