Developer 5 min read

Verification of Payee: Error Handling and Fallback UX

The happy path is easy: a match, a green tick, on you go. The real design work is what happens when a check times out, errors, or comes back 'not available' — and getting that right keeps payments both safe and usable.

By Verification of Payee EU · powered by RoxPay

Verification of Payee: Error Handling and Fallback UX

Key takeaways

  • Plan for 'not available', timeouts and errors, not just clean matches.
  • Degrade gracefully: never silently pass or hard-block by default.
  • Tell the payer what happened in plain language so they can decide.

A well-designed Verification of Payee flow spends most of its effort on the non-happy paths. A check might time out, the responding bank might be unreachable, or the outcome might legitimately be 'not available'. How your app handles those moments determines whether VoP protects users or frustrates them.

The cases to design for

  • Not available: the bank cannot return a result. This is a defined outcome, not an error.
  • Timeout: the check did not respond in time.
  • Transport error: the call itself failed.
  • Close match and no match: valid outcomes that need clear messaging.

Never silently pass

If a check fails or is unavailable, do not quietly treat it as a match. Tell the payer the check could not be completed and let them make an informed choice.

Designing the fallback

  1. 1 Distinguish 'not available' from technical failure in your UX.
  2. 2 Use a short timeout and a clear message if it is exceeded.
  3. 3 Offer a sensible next step rather than a dead end.
  4. 4 Log the outcome so support and audit can see what happened.

Outcomes you can design around

RoxPay's Verification of Payee returns clear, distinct outcomes — including 'not available' — so you can build fallback UX that degrades gracefully instead of guessing.

All articles
FAQ

Frequently asked

Use a short timeout, show a clear message that the check could not be completed, and offer a sensible next step. Never silently treat a timeout as a match.

No. It is a defined VoP outcome meaning the bank could not return a result. Your UX should distinguish it from a technical failure.

Not necessarily. Degrade gracefully: tell the payer the check could not be completed and let them make an informed decision rather than hard-blocking or silently passing.

Keep reading

Handling timeouts and retries Make VoP resilient under failure. Accessible VoP results Clear messaging for every user.

Design VoP that fails safely

Talk to RoxPay about Verification of Payee outcomes built for clean fallback UX.

Talk to an expert Read about timeouts