Verification of Payee: developer guides
Technical guides for integrating Verification of Payee — the API and response codes, webhooks, latency, idempotency, retries, rate limits and name matching.
16 articles in this topic
Monitoring and Observability for Verification of Payee
A VoP integration can fail quietly: rising latency, a shift in outcomes, a creeping error rate. Good observability catches it before payers feel it.
Verification of Payee Rate Limits and Throughput
A payment run that verifies thousands of payees needs a plan for rate limits and throughput. Here is how to scale Verification of Payee without hitting a wall.
Verification of Payee and Data Residency
Payee verification handles personal data about the people being paid. Where that data is processed and stored matters for GDPR — and for your due diligence.
Audit Logging for Verification of Payee
A Verification of Payee outcome is only useful later if you logged it well. Here is what to record for each check, how long to keep it, and what to leave out.
Handling Verification of Payee Timeouts and Retries
A slow responding PSP should degrade your checkout gracefully, not break it. Here is a practical pattern for timeouts, retries and the not-available outcome in Verification of Payee.
How to Test Verification of Payee in a Sandbox
You can't test VoP properly by only checking the happy path. Here's how to exercise every outcome — match, close, no match, not applicable — and the error paths before you go live.
Verification of Payee Webhooks and Asynchronous Results
Most Verification of Payee checks return in under a second, but networks fail and some responding banks are slow. Webhooks let you handle asynchronous VoP results cleanly without blocking the payer.
Idempotency and Reconciliation in the Verification of Payee API
Retries happen. Without idempotency you double-count checks; without a correlation id you can't tie results back to payments. Here's how to get both right with one field.
Verifying Companies: Legal Persons and Organisation Identifiers in VoP
Company names are messy — trading names, suffixes, abbreviations. That's why Verification of Payee lets you verify legal persons by an organisation identifier, not just a name.
How Name Matching Works in Verification of Payee
VoP doesn't do exact-string comparison — if it did, every initial and accent would be a no match. Here's what actually happens between the name you send and the outcome you get.
How Fast Is Verification of Payee? Latency and Timeouts
VoP runs at the moment of payment, so speed matters. Here's what latency to expect, what happens on a timeout, and how to keep the experience responsive.
Reducing False Positives in Verification of Payee
If every payment returns a close match, users stop trusting the warning. Here's how to cut false positives in VoP without weakening the real fraud signal.
One VoP Connection vs Integrating Bank by Bank
You could integrate every responding bank yourself. Or you could connect once to the SEPA VoP scheme and reach them all. Here's why coverage, not code, is the real challenge.
Verification of Payee API Response and Error Codes, Explained
MTCH, CMTC, NMTC, NOAP — and the difference between a 'no match' result and an actual error. A developer's reference for handling Verification of Payee API responses cleanly.
Being a Responding PSP in the Verification of Payee Scheme
Most VoP content covers the requesting side — asking 'does this name match this IBAN?'. But compliance often means answering those requests too. Here's what a responding PSP must do.
Integrating the Verification of Payee API: A Developer's Guide
From authentication to handling the four scheme outcomes, here's how to integrate a real-time Verification of Payee API and branch your UI cleanly.
Ready to add Verification of Payee?
From the EPC scheme to a single REST call, RoxPay helps banks, PSPs and businesses go live with VoP before their deadline.