2.9.3 India Payments NEFT/RTGS - Beneficiary Name Lookup

For outbound NEFT/RTGS transactions, Beneficiary Name Lookup ensures credit is sent to the correct party. The remitting member invokes NPCI’s API, which forwards the request to the beneficiary member. The response from the beneficiary member is then relayed back to the remitter via NPCI Switch.

Additional configurations are provided for maintaining Maximum query limit for payee prevalidation (Function ID: PMDVLPRF) and for linking System/External error code with Prevalidation system Reason code (Function ID: PMDPVRSN). NPCI Connectivity Details maintenance (Function ID: PJDXMLCN) can be used for Beneficiary Name look-up related API maintenances.

Note:

If signature to be validated in the API calls from NPCI, the existing IMPS system parameters are to be used.

Beneficiary look-up Outward request processing:

Outward requests can be initiated from transaction input screens /SI template screens/ Beneficiary Registration screen. This can be initiated from PMDBENVL screen or the related API. If the outward request received is valid, system calls NPCI ReqBeneDetails API and sends the details.NPCI sends an acknowledgement message on receipt of the request. On receiving the acknowledgement, OBPM sends the response to the request received from channels/UI as "Beneficiary look-up request submitted”.NPCI provides the Beneficiary name by calling RespBeneDetails API. On receipt of the details, Beneficiary Name is displayed on the screen which can be viewed on pressing refresh button.

Beneficiary look-up Inward request processing:

Based on the response received from ECA system, OBPM sends the response back to NPCI calling RespBeneDetails API.

Note:

For India payments Beneficiary lookup, inward requests integration with FC Core is provided.