Verification of Payee looks simple from the outside — check a name against an IBAN — but a clean go-live spans three teams. Here's a checklist that keeps compliance, engineering and product aligned.
1. Compliance and scheme
- Confirm your deadline (euro-area: 9 October 2025; non-euro-area: 9 July 2027).
- Decide your roles: requesting PSP, responding PSP, or both.
- Ensure the check is offered free of charge to the payer, on all in-scope euro credit transfers.
2. Integration
- Connect to a VoP API (or scheme) and store credentials as secrets.
- Pass a stable external id per request for idempotency and reconciliation.
- Handle all four scheme codes: MTCH, CMTC, NMTC, NOAP.
UX is part of compliance
Offering VoP means surfacing a clear result to the payer before authorisation — not burying it. Design the close-match suggestion and the no-match warning carefully.
3. UX and operations
- Show the outcome clearly at the point of payment, in every channel.
- For close match, present the suggested verified name to confirm or correct.
- Log every verification id, outcome and responding BIC for audit and disputes.
4. Testing and launch
Test against sandbox first, exercising each outcome including no match and not available, plus error paths (invalid IBAN, timeouts). Then switch the base URL to production. Integrating a provider already on the SEPA scheme — like RoxPay — turns most of this checklist into configuration rather than construction, so go-live is measured in weeks.