Verification of Payee is a synchronous check that runs while the payer waits to confirm. That makes latency part of the product: a check that takes too long hurts the experience as much as one that fails. The good news is that VoP is designed to be fast.
What to expect
A typical verification returns synchronously, usually in well under a second, and the response includes the responding PSP's processing time so you can monitor performance. Most of the latency is the round trip to the payee's bank, not your own processing.
Slow is not failed
If the responding bank is slow or unreachable, you'll get a not-applicable (NOAP) outcome rather than a hard error. Treat NOAP as 'couldn't verify right now' and let the payer decide with extra caution.
Designing for the slow path
- 1 Set a sensible client timeout and show a brief 'verifying…' state so the wait feels intentional.
- 2 On timeout or NOAP, fall back to a clear 'we couldn't verify this payee' message — not a scary error.
- 3 Log the processing time per call so you can spot slow responding banks and trends.
Reliability matters as much as speed
For a check that sits in the payment path, availability is as important as raw latency. Operating on a provider already connected across the SEPA scheme spreads that reliability across many responding banks. RoxPay returns the responding BIC and processing time with each result, so you can monitor both speed and coverage.