Verification of Payee is conceptually simple: you ask whether a name matches an IBAN, and you get back a standardised outcome. But a robust integration depends on understanding each part of that exchange and feeding it clean data.
The request side
- Payee name: the name as you expect it, ideally structured and clean.
- IBAN: the account being verified.
- Account type: whether the payee is a person or an organisation, which affects matching.
- A request reference or idempotency key to tie the call to your records.
The response side
- Outcome: match, close match, no match, or not available.
- For a close match, the name actually held, so you can show the payer.
- A reason or status code giving context for the outcome.
- An identifier to correlate with your logs and reconciliation.
Garbage in, weak match out
Match accuracy depends on input quality. Sending clean, well-structured names and the right account type meaningfully improves results.
Designing around the model
RoxPay's Verification of Payee API exposes a clear request/response model with standardised outcomes and supporting detail, so your integration can act on results confidently.