VOP Requester Bulk API for Banks

This section describes version 1 of the VOP Requester Bulk API for Banks which is used by EU/Non EU banks or other PSP's in the batch payments journey as a pre-payment beneficiary name validation and to comply with all requirements set forth by the EPC Rulebook as part of the Instant Payments Regulation.

Document History

Endpoints

The SurePay Verification of Payee Bulk API allows Requesting PSPs (Payment Service Providers) to submit batch files for feedback on the accuracy of beneficiary details before processing payments. This pre-payment verification helps prevent fraud and errors, fostering trust and confidence in the payment process.

Overview

What's new?

Version 1 of the VOP Bulk API introduces several new use cases as outlined in the EPC VOP Rulebook and API specifications:

• Multiple Checks: The ability to send and receive multiple checks in one request.
• Organisation ID verification: Checking against an organisation ID (e.g. VAT or LEI number) is introduced.
• Additional information about the account number: Additional information can be included with the account number, enabling the responding Payment Service Provider (PSP) to accurately determine the correct account holder for matching.
• BIC routing: The Bank Identifier Code (BIC) of the responding PSP as well as the requesting PSP is added. This ensures, correct routing through the EDS and correct identification of both parties as well as enhancing the overall security and reliability of the process.
• Alignment with ISO 20022: The API is based on the ISO 20022 standard, ensuring consistency with the specifications as published by the EPC.

How does it work?

The SurePay EPC Verification of Payee Bulk API consists of a bulk upload, an intelligent algorithm, a status check and the results file that can be easily integrated into the bank's batch payments environment through the API's described in this document. The logic can be summarised as follows:

• The Bulk Solution is integrated with all relevant VOP participants, enabling it to submit VOP requests and process their responses.
• When a Bulk API request is submitted with a specified dataset (from the PSP), the Bulk Solution responds with a Task ID. This Task ID allows the payer to check the request's status and retrieve the results once processing is complete.
• The Bulk Solution queues the bulk file and processes each entry by generating a VOP request, identifying the respective payee's VOP endpoint, and submitting the request. The responding PSP may be part of the SurePay ecosystem or external. If within the SurePay ecosystem, the response may include additional data points beyond the VOP Scheme API.
• Once all VOP responses are received, the Bulk API generates a response file for the payer, containing all the relevant information as specified in this document.
• The Task ID's status is updated throughout the process, as outlined in this document, allowing the payer to track progress and determine when the response file is ready.
• When the Bulk response file is ready for retrieval, the status is updated, and the PSP can retrieve the responses using the specified endpoint.
• Each individual record within the Bulk request includes a unique reference to ensure traceability throughout the processing chain.
• A single Bulk request can include up to 100,000 individual records or a maximum file size of 100MB, whichever limit is reached first.
• The solution operates asynchronously and offers three endpoints:
  • An endpoint to submit bulk requests
  • An endpoint to check the status of a bulk request
  • An endpoint to retrieve results once processing is complete
• Rate limits are applied to prevent system overload and ensure efficient processing of records.