Pre-validation related maintenances:

Pre-validation System Maintenance (Function ID: PMDPYVAL) to define pre-validation system /Network to a Pre-validation System Maintenance (Function ID: PMDNWVAL)/Source Network Preferences (Function ID: PMDSORNW) for pre-validation.

Outward request processing: Rest API (/beneficiaryprevalidationrequest) and screen are provided for initiating outward Payee prevalidation request (Function ID: PMDBENVL). Outward requests can be initiated from transaction input screens /SI template screens/Beneficiary Registration screens for India Payments NEFT.

Inward request processing: On receiving the request from external Pre-validation system, if OBPM is co-deployed with FCUBS /FC Core, a call is made to the core system to validate Account, Account Name & Account Status and the response is provided to external system. Details can be viewed from Inbound Payee Pre-validation request screen Function ID: PMDBENRQ. Core system API details can be maintained in ECA system Interface maintenance (Function ID: PMDINECA) for the Interface Type-Account Inquiry.

India payments (NEFT/RTGS) Beneficiary Look -up:

Additional configurations are provided for maintaining Maximum query limit for payee pre-validation (Function ID: PMDVLPRF)and for linking System/External error code with Pre-validation system Reason code (Function ID: PMDPVRSN).NPCI Connectivity Details maintenance (Function ID: PJDXMLCN) is modified for Beneficiary Name look-up related APIs.

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 the Refresh button.

Beneficiary Inward request processing: Based on the response received from ECA system, OBPM sends the response back to NPCI, calling RespBeneDetails API. Out of the box support is available for FC Core accounts.

SCT/SCT Instant Verification of Payee (VOP) Changes:

EPC Directory Service provides information on Reachability and interoperability between VOP scheme participants. File upload is provided in XML format through File Envelope screen and the File type is epcDirectoryService. The uploaded records are available in Verification of Payee Participant Details screen (Function ID: PMDVOPPT).

Outward request processing: Outward requests can be initiated from transaction input screens /SCT SI template screen/Settlement Instruction screen. This can be initiated from PMDBENVL screen or the related AP. On receiving a valid outward request, Rest API request is generated and sent to external system in EPC format provided for VOP. URL is taken from EDS uploaded details - primary URL for Creditor Agent BIC.

Note: Outward VOP request generated from transaction will always be for Creditor IBAN+Name combination . Creditor IBAN+Identifier can be verified from PMDBENVL screen or using the related API.

Inward request Processing: On receiving the request, if OBPM is co-deployed with FCUBS, a call is made to the core system to validate Account provide Account Name & Account Status in the response (provided API CustomerAccDetailService/application.wadl is supported for FCUBS version). Identifier validation is done only if the scheme code received in the request and scheme code returned by FCUBS are same.

Note: Verification of Payee API authentication is done by exchanging VOP participants QWAC certificates and validating the authenticity. This will be an implementation activity based on the Routing and Verification Mechanisms or Receiver BICs, Bank will be communicating with. No out of the box support will be provided for this from product.

Support is provided for applying charges on outward Prevalidation requests sent. The charges can be liquidated by running the Auto job or manually selecting the records from PMSBENVL Summary screen.