1. India IMPS Payments User Guide
  2. IMPS Inbound Payments
  3. IMPS Inbound Payments Processing
  4. Inbound IMPS Payment Processing
  5. Initial Validations

Initial Validations

The validations are similar to that of Outbound Payments.Mandatory field checks/ Referential data checks are done as below:

'OrgID' Validation:

System performs following steps:
  • Derive the 'OrgID' field value from Header (<Head>) tag.
  • Validate if the 'OrgID' field value from the XML is same as maintained on India Payments Out bank Identifier screen (PMDIOBID).
    • If above step is successful, then payment is processed ahead.
    • If above step fails, then payment is rejected.

Transaction Type (P2P/P2A) derivation -

System derives the IMPS transaction type from the 'Payee Address type' tag from XML file.
  • If the <Payee. AC> -> addrType is 'Account' then the inbound transaction is P2A.
  • If the <Payee. AC> -> addrType is 'Mobile' then the inbound transaction is P2P.

Beneficiary Details Derivation

System derives the beneficiary account number, beneficiary Branch IFSC, Beneficiary MMID and Beneficiary Mobile Number from the ‘<Payee.Ac.Detail>’ tag of the inbound XML file.
  • For P2P – Based on the MMID and Mobile Number combination in XML file, derive beneficiary account number from the India Payments account preferences screen (PMDEXACP).
  • For P2A – Payee IFSC and Account Number is present in XML file.

Beneficiary account type is present in the inbound XML message. System derives the beneficiary account type and populate the same in the Response File.

Transaction Account Branch Derivation

For P2A - Derive Based on IFSC Code present in ‘<Payee.Ac.Detail>’ tag.

For P2P - Based on the MMID and Mobile Number combination in XML file, derive beneficiary account number from the India Payments account preferences screen (PMDEXACP).

Parent topic: Inbound IMPS Payment Processing