Respond to VOP Requests with Qombo’s On-Demand Solution
Keep your account-holder data in-house and answer VOP requests in real time. Instead of storing your database, Qombo calls an endpoint you implement whenever a PSP queries one of your IBANs, then performs the match and responds to the requesting PSP.
This is one of two ways to handle the responding side of VOP. The other is Responding — Cloud, where Qombo stores your data and manages everything.
Endpoint
| Method | Path | Purpose |
|---|---|---|
POST | /account-holder | Implemented by you. Returns the account-holder data for the requested IBAN. |
This endpoint lives on your sideThe path above is the technical specification of the endpoint you expose. Qombo calls it; you don't call Qombo.
How it works
- Qombo validates and authorizes the incoming request from the other PSP.
- Qombo calls your
/account-holderendpoint with the requested IBAN. - You return the account-holder information.
- Qombo performs the identity match and responds to the requesting PSP.
What Qombo sends you
iban— the account to look up.identifiersType(optional) — the company identifier types to return, when set.
What you must return
accountInformation— either an individual (primaryAccountHolder/secondaryAccountHolder) or an organisation (namesand/oridentifiers).- Optionally
accountTypeandaccountLabel(a custom account name when the default naming doesn't fit). - Respond
404when the IBAN is unknown, or the account is closed or blocked.
For the accepted identifier types and formats, see company identifiers.
Performance & availability
Because responses are fetched in real time, your endpoint must meet high standards:
- 24/7 uptime — keep it always reachable.
- Fast response times — answer quickly to avoid delaying the VOP response.
If your endpoint is down or unresponsive, Qombo returns a 500 Internal Server Error to the requesting PSP.