Detailed Flow in Destination Country (Receiving)

The Destination Country processing flow is shown below, split between a 4-step clearing, 5-step clearing for normal priority payments and 5-step for high priority payments:

1	The Destination Nexus Gateway sends the Nexus pacs.008 to the Destination IPS.	The Destination IPS may need to convert this message into its local format before forwarding this to the Destination SAP. No reservations need to be made at this stage.
2	The Destination IPS sends the payment instruction to the Destination SAP	The IPS is free to decide on the format of the payment message for the interaction towards the D-SAP and the D-PSP. If ISO 20022 is not used domestically, the IPS will need to translate from the Nexus pacs.008 to the domestic payment instruction format.
3	The Destination SAP confirms that the FX Provider has sufficient funds with them and applies sanctions screening and compliance checks if required. If the Destination SAP is happy to proceed with the payment, it will reserve the amount on the FXP’s account with them. If the Destination SAP is not able to validate the payment, the Destination SAP can reject the transaction.
4	The D-SAP either submits the payment instruction message to the Destination IPS, effectively giving the IPS the instruction to make payment to the Destination PSP or reject the transaction.
5	The Destination IPS, upon receiving the validated instruction from the Destination SAP ensures settlement (by reserving the pre-funded balance of the Destination PSP or otherwise).
6	The Destination IPS forwards the payment message to the Destination PSP for validation.
7	The Destination PSP will apply sanctions screening and compliance checks before crediting the Recipient.
8	The Destination PSP sends a confirmation to the Destination IPS in the form of a pacs.002 message
9	Upon confirmation of the Destination PSP, the D-IPS will settle the transaction.
10	In case of a confirmation and successful settlement, the D-IPS will confirm settlement to the Destination SAP.
11	The D-IPS will confirm settlement to the Destination Nexus Gateway via a Nexus pacs.002 message.	The Destination IPS must use the Nexus pacs.002 payment status report format to confirm the transaction to the Nexus Gateway. See Messaging & Translationfor details on the format.
12	The Destination SAP can now finalize the debit on the FXP account.
13	The Destination Nexus Gateway will confirm receipt of the Nexus pacs.002 message. This is an optional message.
14	In case the Destination PSP is not able to credit the Recipient, the Destination PSP will send a pacs.002 reject back to the Destination IPS.
15	Upon receiving the reject from the Destination PSP, the Destination IPS will reverse the settlement reservation.
16	The Destination IPS will inform the Destination SAP of the reject by sending a pacs.002.
17	The Destination IPS will inform the Destination Nexus Gateway of the reject by sending a Nexus pacs.002.
18	Upon receing the pacs.002 rejection from the Destination IPS, the Destination SAP will release the reservation on the FXPs account.
19	The Nexus Destination Gateway will confirm receipt of the Nexus pacs.002. This confirmation is an optional message.

	Normal Priority (NORM)
1	The Destination Nexus Gateway sends the Nexus pacs.008 to the Destination IPS.	The Destination IPS may need to convert this message into its local format before forwarding this to the Destination SAP. No reservations need to be made at this stage.
2	The Destination IPS sends the payment instruction to the Destination SAP	The IPS is free to decide on the format of the payment message for the interaction towards the D-SAP and the D-PSP. If ISO 20022 is not used domestically, the IPS will need to translate from the Nexus pacs.008 to the domestic payment instruction format.
3	The Destination SAP confirms that the FX Provider has sufficient funds with them and applies sanctions screening and compliance checks if required. If the Destination SAP is happy to proceed with the payment, it will reserve the amount on the FXP’s account with them. If the Destination SAP is not able to validate the payment, the Destination SAP can reject the transaction.
4	The D-SAP either submits the payment instruction message to the Destination IPS, effectively giving the IPS the instruction to make payment to the Destination PSP or reject the transaction.
5	The Destination IPS, upon receiving the validated instruction from the Destination SAP ensures settlement (by reserving the pre-funded balance of the Destination PSP or otherwise).
6	The Destination IPS forwards the payment message to the Destination PSP for validation.
7	The Destination PSP will apply sanctions screening and compliance checks and validate the Recipients account.
8	The Destination PSP sends a confirmation to the Destination IPS in the form of a pacs.002 message
9	The Destination IPS sends a Nexus pacs.002 message to the Nexus Destination Gateway	The Destination IPS must use the Nexus pacs.002 payment status report format to confirm the transaction to the Nexus Gateway. See Messaging & Translationfor details on the format.
10	The Destination Nexus Gateway confirms receipt with a Nexus pacs.002.
11	Upon confirmation of the Nexus Gateway, the D-IPS will finalize the settlement of the transaction.
12	The D-IPS will confirm settlement to the Destination SAP and the Destination PSP.
13	The Destination SAP can now finalize the debit on the FXP account.
14	Upon receiving confirmation of settlement, the Destination PSP credits the Recipient.
15	In case the Destination PSP is not able to credit the Recipient, the Destination PSP will send a pacs.002 reject back to the Destination IPS.
16	The Destination IPS will inform the Destination Nexus Gateway of the reject by sending a Nexus pacs.002.
17	The Nexus Destination Gateway will confirm receipt of the Nexus pacs.002.
18	Upon receiving the reject confirmation from the Nexus Gateway, the Destination IPS will reverse the settlement reservation.
19	The Destination IPS will inform the Destination SAP and the Destination PSP of the reject by sending pacs.002 messages.
20	Upon receing the pacs.002 rejection from the Destination IPS, the Destination SAP will release the reservation on the FXPs account.

	High Priority (HIGH)
1	The Destination Nexus Gateway sends the Nexus pacs.008 to the Destination IPS. Nexus will start a timeout timer.	The Destination IPS may need to convert this message into its local format before forwarding this to the Destination SAP. No reservations need to be made at this stage.
2	The Destination IPS sends the payment instruction to the Destination SAP.	The IPS is free to decide on the format of the payment message for the interaction towards the D-SAP and the D-PSP. If ISO 20022 is not used domestically, the IPS will need to translate from the Nexus pacs.008 to the domestic payment instruction format.
3	The Destination SAP confirms that the FX Provider has sufficient funds with them and applies sanctions screening and compliance checks if required. If the Destination SAP is happy to proceed with the payment, it will reserve the amount on the FXP’s account with them. If the Destination SAP is not able to validate the payment, the Destination SAP can reject the transaction.
4	The D-SAP either submits the payment instruction message to the Destination IPS, effectively giving the IPS the instruction to make payment to the Destination PSP or reject the transaction.
5	The Destination IPS, upon receiving the validated instruction from the Destination SAP ensures settlement (by reserving the pre-funded balance of the Destination PSP or otherwise).
6	The Destination IPS forwards the payment message to the Destination PSP for validation.
7	The Destination PSP will apply sanctions screening and compliance checks and validate the Recipients account.
8	The Destination PSP sends a confirmation to the Destination IPS in the form of a pacs.002 message
9	The Destination IPS sends a Nexus pacs.002 message to the Nexus Destination Gateway	The Destination IPS must use the Nexus pacs.002 payment status report format to confirm the transaction to the Nexus Gateway. See Messaging & Translationfor details on the format.
10	The Destination Nexus Gateway confirms receipt with a Nexus pacs.002 and stops the timer.
11	Upon confirmation of the Nexus Gateway, the D-IPS will finalize the settlement of the transaction.	It is essential in High Priority payments that the Destination IPS ensures settlement is subject to the confirmation of this Nexus pacs.002.
12	The D-IPS will confirm settlement to the Destination SAP and the Destination PSP.
13	The Destination SAP can now finalize the debit on the FXP account.
14	Upon receiving confirmation of settlement, the Destination PSP credits the Recipient.
15	In case the Destination PSP is not able to credit the Recipient, the Destination PSP will send a pacs.002 reject back to the Destination IPS.
16	The Destination IPS will inform the Destination Nexus Gateway of the reject by sending a Nexus pacs.002.
17	The Nexus Destination Gateway will confirm receipt of the Nexus pacs.002.	The Destination IPS can await the confirmation by the Nexus Gateway, but as in this case the payment is rejected, the Destination IPS is also allowed to proceed with the next steps pending the response from the Nexus Gateway.
18	Upon receiving the reject confirmation from the Nexus Gateway, the Destination IPS will reverse the settlement reservation.
19	The Destination IPS will inform the Destination SAP and the Destination PSP of the reject by sending pacs.002 messages.
20	Upon receiving the pacs.002 rejection from the Destination IPS, the Destination SAP will release the reservation on the FXPs account.
21	In the scenario there is a failure in the Destination processing (either in the Destination IPS, SAP or PSP), a pacs.002 confirming or rejecting the payment may not arrive at the Destination IPS.
22	Specifically for High Priority payments, thr Nexus Gateway will keep a timer and reject the payment when the maximum time has exceeded. The Nexus Gateway will send a Nexus pacs.002 reject to the Destination IPS.
23	Upon receiving the reject message from the Nexus Gateway, the Destination IPS will reverse the settlement reservation.	The Destination IPS needs to ensure settlement is subject to the Nexus pacs.002 from the Nexus Gateway. Even in the case a positive response has been received from the Destination PSP, the payment may still be rejected in case the pacs.002 has not been received by the Nexus Gateway in time.
24	The Destination IPS will inform the Destination SAP and the Destination PSP of the reject by sending pacs.002 messages.
25	Upon receiving the pacs.002 rejection from the Destination IPS, the Destination SAP will release the reservation on the FXPs account.