Validation based on ASP data

An MSIF transfer service automatically checks whether the requests it is to send or the requests that it has received are compatible with the application service profile (ASP) of the SWIFT service that is to be or was used. For more information about ASPs, see Application service profiles.

For SendMsg, SendFile, and DownloadFile scenarios, an MSIF transfer service checks whether the options specified for a scenario are compatible with the contents of the ASP (see Table 1). If not, the MSIF transfer service rejects the request and changes the transfer status of the scenario to Invalid.
For MsgReceived, FileReceive, and RespondDownload scenarios, an MSIF transfer service checks the ASP for elements that the ASP requires it to recognize but that it does not recognize. If the MSIF transfer service detects such an element, it issues an event and includes a response message and a PartialOk code in the notification that it passes to the receiving application.

Table 1. ASP settings checked by an MSIF transfer service
Description	Option name	Possible values
Delivery mode (real-time or SnF)	DeliveryMode	RT or SNF
Whether the SAG is to sign the request digests	Signed	True or False
If the SAG is to sign the request digests, which cryptographic method is to be used to sign the request digests	CryptoMethod	CryptoBlock or SignatureList
Whether SWIFT is to perform non-repudiation processing	NRIndication	True or False (or not set)
If the use of T-Copy or Y-Copy is optional, whether it is to be used	Copy	True or False (or not set)
For an SnF transfer that uses Y-Copy, whether SWIFT, after the third party authorizes the file, is to send an authorisation notification to the sender	AuthNotif	True or False (or not set)