termen implementării Verification of Payee
One real-time REST call to confirm a begunstigde name against an IBAN — Overeenkomst outcome, responding bank BIC and processing time in the response. Built on RoxPay's payments platform and the SEPA VoP scheme.
{ "Name": "ACME Trading Ltd", "Iban": "DE89 3704 0044 0532 0130 00" }
{ "VopResult": "MATCH", "MatchType": "MTCH", "RespondingBic": "CRACIT33XXX" }
verificatie begunstigdeului în jednym zapytaniu
API Verification of Payee exposes the SEPA VoP scheme as a clean REST endpoint: send a name and an IBAN, get back a standardised Overeenkomst result in real time — no scheme plumbing to build yourself.
It is the same verification RoxPay runs inside its SwiftLine / RoxBusiness banking platform, available to banks, PSPs and businesses through an authenticated API and a dashboard. Each response includes the Overeenkomst type, the responding institution's BIC and the PSP processing time.
Because it is delivered over RoxPay's European open-banking infrastructure, you connect once and reach begunstigdeverificatie across SEPA — instead of integrating with each responding bank.
Od zera până la zneverificabil în czterech krokach
A standard REST integration that drops into your existing payment flow.
Get your credentials
Activate the service and authenticate with a bearer token — no per-bank onboarding to manage.
Send name + IBAN
POST the begunstigde name and IBAN to the verify endpoint, optionally with your own reference id for reconciliation.
Odczytaj rezultat
Otrzymaj rezultat (conformiteit / Bijna overeenkomst / Geen overeenkomst / nu se aplică), BIC răspunzător și czas przetwarzania.
Act in your UI
Show a clear signal to the payer, or gate a payment run, a mandate or an onboarding step on the result.
Co returnează API
Every response maps to a SEPA VoP scheme code, so your logic stays simple.
MATCH · MTCH
Name matches the titularul contului. The response also carries the responding bank BIC.
CLOSE_MATCH · CMTC
Close Overeenkomst — handle it as a soft warning and suggest the verified name.
NO_MATCH · NMTC
Name does not Overeenkomst. Surface a clear warning before the payment is confirmed.
NOT_APPLICABLE · NOAP
Verification not available for this IBAN right now. Let the user decide.
Budowa VoP samodzielnie a API
What you avoid by calling one endpoint instead of joining the scheme alone.
Build it in-house
- Scheme connectivity Integrează per responding PSP
- Czas până la implementării Months
- Response detail You normalise it
- Reuse across products Re-plumb each flow
- Utrzymanie după twojej stronie
API Verification of Payee
- Scheme connectivity One connection, SEPA-wide reach
- Czas până la implementării Tygodnie
- Response detail Standardised result + BIC + timing
- Reuse across products One API for UI, batch & mandates
- Utrzymanie Handled by the platform
One API, three audiences
The same endpoint serves very different jobs to be done.
băncile și leverancierii de servicii de plată
Oferowanie Verification of Payee to titularul contuluis and meet the Verordening instantbetalingen without building scheme connectivity.
Developers
A predictable REST contract, real-time responses, your own reference ids and clear scheme codes to branch on.
companiile și systemy ERP
Verify supplier and payroll IBANs in bulk before a payment run, cutting invoice-redirection risk.
API — răspuns
What developers and product teams ask first.
Yes. A verify call returns synchronously, typically in well under a second, and includes the responding bank's BIC and the PSP processing time so you can monitor performance.
Calls are authenticated with a bearer token over HTTPS. You can also use the RoxBusiness dashboard for ad-hoc checks without writing code.
Un rezultat normalizzato (MATCH, CLOSE_MATCH, NO_MATCH, NOT_APPLICABLE), il cod de Overeenkomst dello scaremă SEPA, un id de Verifică, il BIC rispondente, il tempo de procesare e il tuo id esterno opzionale.
Yes — call the endpoint per record to verify a whole file of suppliers or begunstigdeii before a payment run. It is built for high throughput.
Yes. The check compares the submitted name against the registered titularul contului, whether that is an individual or a company, and is used inside RoxPay's SEPA Direct Debit mandate flow as a pre-verificatie.
NO_MATCH is not a transport error — it is a valid 200 response telling you the name does not belong to the IBAN. Treat it as a hard stop in your UI or payment run: surface a clear warning, block auto-approval, and let the user re-check the begunstigde before sending.
CLOSE_MATCH (scheme code CMTC) means the name is almost right — a missing middle name, a legal vs trading name. The response carries the verified account-holder name, so you can show it as a suggestion and ask the payer to confirm rather than reject the payment.
For legal persons the scheme allows verification against the organisation identifier (e.g. Italian Partita IVA / Codice Fiscale) as well as the name. You submit the identifier in the request and the API returns the standard Overeenkomst outcome — useful when the registered name and trading name differ.
Da. Pentru o rundă de plăți, parcurge fișierul leverancierilor sau salariilor și apelează endpoint-ul de verificatie pentru fiecare înregistrare înainte de a elibera lotul. Este construit pentru throughput ridicat, astfel echipele financiare pot valida în masă IBAN-urile față de nume înainte de fiecare rundă de plăți.
Yes. You send a JSON request with the begunstigde name and IBAN and get back the outcome, the verified name (on a Bijna overeenkomst) and the responding BIC. See a full request and response in our VoP example, or the payloads and scheme codes in the API documentation.
Lees verder
Integrează Verification of Payee
Ottieni le credenziali e vai live sullo scaremă SEPA VoP cu un'unica integrare REST.