How it works

How Verification of Payee Verification of Payee

From the moment a payer types a name and IBAN to the answer on screen — the complete Verification of Payee flow, the EPC scheme request, and the four outcomes that come back in under a second.

Fluxul Verification of Payee
Plătitor Nume + IBAN introduse
Schema VoP Cererea este trimisă băncii
Banca beneficiarului Numele verificat față de cont
PotrivireRăspuns în < 1 secundă
Overview

A real-time question between two banks

Verification of Payee works by turning the payer's bank and the begunstigdeului bank into two ends of a single, real-time question: does this name belong to this IBAN?

The exchange happens through the EPC Verification of Payee scheme over standardised APIs, so it slots into the existing payment flow without changing how people pay. The whole round trip completes before the payer authorises the overboeking.

The result is always one of four standardised outcomes, so the payer — or the system initiating a batch of payments — gets an unambiguous signal every time.

The flow

Verification of Payee, krok după kroku

Four stages, completed in real time between the requesting and responding leverancierii de servicii de plată.

  1. 1

    Zbieranie nazwy și numeru IBAN

    The payer enters (or imports from an invoice) the begunstigde name and IBAN, exactly as for a normal SEPA overboeking.

  2. 2

    Przekierowanie până la PSP begunstigdeului

    The requesting PSP looks up the responding PSP from the IBAN and sends a secure VoP request through the EPC scheme.

  3. 3

    Match at the bank

    The responding PSP compares the submitted name against the registered titularul contului and returns a standardised Overeenkomst result and the responding BIC.

  4. 4

    Show the answer

    Match, Bijna overeenkomst, Geen overeenkomst or not available is surfaced to the payer in under a second — before authorisation, never after.

The four outcomes

Co returnează verificatie

VoP responses are standardised în toată Europa — each maps to a clear scheme code.

Match (MTCH)

The name matches the titularul contului. Safe to send with confidence.

Close Overeenkomst (CMTC)

Almost right — the verified name is suggested so the payer can confirm or correct it.

Brak conformității (NMTC)

The name does not belong to this IBAN. A strong signal to stop and double-check.

Not available (NOAP)

bancă begunstigdeului nu poate teraz zverifica datelor. Decyzja trebuie până la betalerului.

Why real time matters

Verification of Payee vs. a manual IBAN check

Why an in-flow, real-time check beats checking names by hand after the fact.

Capability Manual / no check Verification of Payee
When it happens After the payment, if at all Before authorisation, in real time
Kto corespunde Zgadywanie prin betalerului Sam bancă begunstigdeului
Speed Od minut până la dni Under a second
Format rezultatu Nieustrukturyzowany Cztery standaryzowane rezultati
Scales to bulk payments No Yes — name checks via API
Where it fits

One flow, many entry points

The same VoP mechanism works wherever a euro overboeking starts.

Online & mobile banking

Surface the Overeenkomst result inline as the payer reviews a new begunstigdey, before they confirm.

Bulk & ERP payments

Zverifică numery IBAN leverancierilor și salariilor în partiach poprzez API înainte de zwolnieniem paczki plăți.

Inicjowanie plăți

PISPs and platforms call VoP at initiation so the payer sees a verified name before consenting.

begunstigdeului (CoP)

How the check works, answered

The mechanics in plain terms.

It is designed for instant payments and typically returns a result in well under a second, before the payer authorises the overboeking — so the payment experience stays fast.

The requesting bank sends the name and IBAN; the responding bank returns a standardised Overeenkomst outcome (and, on a Bijna overeenkomst, the verified name as a suggestion). Full account-holder details are not exposed.

The name is almost right — a missing middle name, a legal vs trading name, a transliteration. The service can return the verified name so the payer confirms or corrects without guessing.

No. VoP is informative: it gives a clear answer, but the decision to send, fix or stop stays with the payer. That is exactly why it is effective against social-engineering scams.

Yes. Through the API, names and IBANs can be verified in bulk — ideal for treasuries and ERPs checking supplier and payroll details before a payment run.

You send the begunstigde name and IBAN and receive a small structured response with one of four outcomes — Overeenkomst, Bijna overeenkomst, Geen overeenkomst or not possible. See a full request and response in our VoP example.

Yes. Under the Verordening instantbetalingen, euro-area PSPs have offered VoP since 9 October 2025 and non-euro EU PSPs must comply by 9 July 2027.

See Verification of Payee în your flow

Porozmawiaj cu nami o schemă EPC, API și uruchomieniu produkcyjnym înainte de swoim terminem.