• Initial Validations
• Duplicate Check
• Sanctions Check
• EAC Check
• Messaging

• The following processing will be covered as part of initial validations:
  • Data enrichment - Account / Bank Re-direction , Network character replacement
  • Mandatory field validations
  • Network Limit validations
• If Account re-direction or bank re-direction is maintained, then the account / bank details will be replaced by the values. Account re-direction is applicable for debtor account only.
• Network character replacement will be done for characters not allowed by the Network if the corresponding maintenance is available.
• Mandatory Fields / Referential data checks will be done based on the details received in the payment request and the values populated by system. Validation will be available to verify whether the Debtor Bank Routing Number is allowed for RFP. In case of validation failure, transaction will be rejected.
• Transfer amount limit check will be done for the minimum and maximum amount limits defined for the Network, as maintained in Inbound Payment Preferences (PUDNCPRF).

• Duplicate parameters can be maintained for the source. Based on the duplicate days and fields set, duplicate check for the RFP will be done. If the RFP is identified as duplicate, the transaction will be moved to business override queue.
• The following parameters will be available for duplicate check:
  • Debtor Account - DBTR_ACC
  • Creditor Account - CRDTR_ACC
  • Transfer Amount - TFR_AMT
  • Instruction Date - VALUE_DATE
  • Creditor Bank Routing Number - CRDTR_BANK_CODE
  • Customer - CUSTOMER_NO
  • Debtor Bank Routing Number - DBTR_BANK_CODE

The transaction can be sent for sanction screening to an external system. The external system status can be linked to one of the following system status:

• Approved
• Rejected
• Interim
• Seizure

If sanction is approved, the transaction will be resumed with the further processing. In case of seizure, no accounting is applicable. If the status is rejected, interim or timed out, the transaction is moved to sanction check queue.

The debit details will be sent to the DDA system for account validation. The external system status can be linked to one of the following system status:

• Approved
• Rejected
• Interim

If account check is approved, the transaction will be resumed with the further processing. If the status is rejected or interim, the transaction is moved to EAC queue.

• Every RFP will generate a pain.013.001.05 message. Message ID format will be the same as credit transfer messages.
• All message processing dates are required to be set to Eastern Time (Eastern Standard Time or Eastern Daylight Time, as applicable under the Energy Policy Act of 2005) by the message sender. While generating the pain.013 message, the following values will be populated for RTP:
  • Instructing Agent Member ID –.This will be populated as creditor branch Routing and Transit number
  • Instructed Agent member ID - This is the Routing and transit number of the debtor bank
  • Payment method will be TRF always
  • Clearing system Code will be TCH
  • Settlement method will be CLRG
  • Service level code will be populated as SDVA
  • Local instrument proprietary value will be as selected for the transaction
  • Charge bearer value will be populated as SLEV

• The Accept or Reject confirmation is received from the CI in pacs.002 format. For every message sent, a confirmation message is received.
• System parse and upload the received message and based on the status value received RCVD / RJCT, the outbound transaction is further processed.
• On receiving RJCT status, RFP will be marked as ‘Rejected’. Notification will be sent to creditor customer indicating the status of the RFP.