Verification of Payee ends in a human decision: the payer reads the outcome and chooses whether to proceed. If that outcome is ambiguous, buried, or invisible to someone using a screen reader or with low vision, the check has done its technical job but failed its actual purpose. Accessible result design is therefore part of the fraud control, not a nice-to-have.
Principles for clear outcomes
- Use plain language: 'The name does not match this account' beats a status code.
- Never signal with colour alone — pair green or red with an icon and text.
- Make the warning prominent and placed before the authorise action, not after.
Patterns by outcome
Each standardised outcome deserves a deliberate treatment so the payer knows exactly what to do.
- 1 Match — quiet reassurance; confirm and continue.
- 2 Close match — show the suggested name and let the payer compare and decide.
- 3 No match — a clear, hard-to-miss warning that invites the payer to stop and check.
- 4 Not available — a neutral message explaining the check could not complete, with guidance.
Accessible is also more effective
Designing for screen readers, low vision and plain comprehension does not just meet accessibility standards — it makes the warning clearer for everyone, which is exactly what stops a misdirected payment.
RoxPay returns standardised, structured outcomes that map cleanly to accessible UI patterns, so you can present a result every payer can understand and act on.