Inbound Request for Payment Processing

Inbound payments follow the below listed processing steps:

Initial Validations

System performs the below validations similar to the outbound payments:
- Account/Bank re-direction Account re-direction is done for the credit account
- Mandatory field checks/ Referential data checks

Any failure during validation processing results in a transaction reject and pacs.002 message sent to CI with appropriate reason code.

Note:

Reason code is populated based on the error code linkage in USRTP reason code mapping (Function PUDRSNMP) screen.

Customer Restrictions check

This is done based on the new maintenance US RTP –RFP Restrictions (Function ID: PUDRFPRT).
If no RFP is allowed or the particular credit account is disallowed, then pacs.002 message is sent out with RJCT status.

External Account Check

If no RFP is allowed or the particular credit account is disallowed, then pacs.002 message is sent out with RJCT status.
If ECA is rejected and auto cancellation is applicable or if manually cancelled from the queue, pacs. 002 is generated with RJCT status and reason code linked to the error code.

Sanction Check

In case of seizure , inbound RFP message will marked as seized .No further action will be possible for this RFP.
Seizure accounting is applicable, if configured - Dr. Customer account & Cr. Seizure GL.
On successful completion of sanction check customer notification is generated. Inbound RFP is marked with the status ‘Pending ‘ till the customer response is received and processed.

Note:
No further notification will be sent to the creditor FI in this case. This has to be operationally handled.