SWIFTNet notifications

For a SendMsg, SendFile, or RespondDownload scenario, the SIPN can issue the following types of SWIFTNet notifications:

Y-Copy authorisation notification

For a SendMsg or SendFile scenario that uses a Y-Copy service, the SIPN passes to the sender a system message containing information about whether the third party authorized or refused the transfer:

Y-Copy authorisation: A Y-Copy notification of authorisation (abbreviated to Y-Copy authorisation) indicates that the third party approved the transfer. A SendMsg or SendFile request specifies whether the SIPN is to create such a notification and pass it to the sender.
Y-Copy refusal: A Y-Copy notification of refusal (abbreviated to Y-Copy refusal) indicates that the third party refused the transfer. The SIPN always creates and passes such a notification to the sender.

Non-delivery warning

For a SendMsg or SendFile scenario that uses SnF delivery mode, if the message or file was not delivered to the receiver within the time limit specified by the sender, the SIPN passes to the sender a system message containing a non-delivery warning.

Delivery notification

For a SendMsg (SnF only), SendFile (real-time or SnF), or RespondDownload (real-time only) scenario, the SIPN passes to the sender a system message (for SendMsg or SendFile in SnF delivery mode) or SNL primitive (for SendFile in real-time delivery mode or RespondDownload) containing information about the delivery of a message or file:

Successful-delivery notification

The receiver indicated that the transfer was successful. The corresponding SendMsg, SendFile, or ProvideFileForDownload request specifies whether the receiver (for a real-time transfer) or the SIPN (for an SnF transfer) is to create a successful-delivery notification and pass it to the sender.

Failed-delivery notification

One of the following situations occurred:

A file was transferred in real-time delivery mode and the receiver indicated that the transfer was unsuccessful.
A message or file was transferred in SnF delivery mode and the receiver either indicated that the transfer was unsuccessful or did not retrieve the message or file within 15 days.
A message or file was transferred using a T-Copy or Y-Copy service, and a third party either indicated that the transfer was unsuccessful or did not retrieve the message or file within 15 days.

Under any of these circumstances, the SIPN always creates and passes such a notification to the sender.

An MSIF transfer service treats SWIFTNet system messages that do not contain SWIFTNet notifications as normal InterAct messages, and receives them using a MsgReceived scenario. When a duplicate SWIFTNet notification is received, it is discarded and no DeliveryAck notification or event is generated.