In the VoP scheme, PSPs must be able to respond to verification requests from other PSPs. The Qombo Responding API offers two implementation options, allowing you to choose the approach that best fits your needs.
Regardless of the option chosen, you only need to provide account holder data, while Qombo handles all the complexities, including authentication, request validation, matching, and responses to requesting PSPs.
The matching algorithm provided by Qombo complies with the EPC’s VoP Scheme Rulebook and recommendations.
Select a method to expose your client information between the two options.
Delegate the management and storage of your account holders to our systems. You submit your data at your discretion, and Qombo acts as the responding PSP in the VoP EPC ecosystem.
With this approach, Qombo validates the request, then queries your system for account holder details related to an IBAN.
You must implement an API endpoint to provide this information.
Qombo handles the matching calculations and responds to the requesting PSP.
When the on-demand service is chosen, the SFTP method can be used as a fallback if the API endpoint is not an available option. More informations here:
Companies might be identifies by a name (legal name or trade name) and/or by a legal identifier (e.g. VAT Number). We highly recommend to permit other PSPs to check your clients with the legal identifier you have in your system. Relying solely on a company name increases the risk of homonym fraud, where two separate companies share the same or very similar names, potentially leading to incorrect matches.
Before going live, you will need to provide your project manager the legal identifier types you authorise to control your clients accounts (as a Responding PSP).