The story
This story is fictional. The failure in it is common.
Jonah owed Lila £42.50 for a shared Zoom licence. He opened his banking app, entered her account number and pressed Confirm.
A second later he saw that two digits were the wrong way round.
He looked for a cancel button. There wasn’t one. The help pages said that mistaken payments were the sender’s responsibility.
On the walk home he passed a construction site: red tape, yellow markers, warning signs before every hazard.
At his desk he wrote that a mistake should slow you down, not lock you out.
The principle
Principle 5 of Universal Design (Center for Universal Design, NC State, 1997): the design minimises hazards and the adverse consequences of accidental or unintended actions.
| Guideline | What it asks | Held by this app? |
|---|---|---|
| 5a | Arrange elements to minimise hazards and errors | No. Confirm sent the payment straight away |
| 5b | Provide warnings of hazards and errors | No. Nothing checked the account number against the payee |
| 5c | Provide fail-safe features | No. No review, no pause, no undo |
| 5d | Discourage unconscious action in tasks that require vigilance | No. Confirm was one more tap in a familiar sequence |
Service blueprint: current state
The payment breaks at Confirm: the app executes before anything checks the payee. Rows marked (inferred) are deduced from the story, not observed.
| Layer | 1. Decides to pay | 2. Enters details | 3. Confirms | 4. Spots the error | 5. Looks for a way back |
|---|---|---|---|---|---|
| Evidence | £42.50 owed for a shared licence | Account number field | Confirm button | Two digits reversed | Help: mistakes are the sender’s responsibility |
| Customer actions | Opens the app | Types Lila’s account number | Presses Confirm | Notices one second later | Looks for cancel |
| Line of interaction | |||||
| Frontstage | Banking app | No check of name against account. F1 | No review screen; payment sent. F2 | None | No cancel; help text assigns blame. F3 |
| Line of visibility | |||||
| Backstage | None | Payee not verified (inferred) | Payment executed immediately (inferred) | None | No recall request offered (inferred) |
| Line of internal interaction | |||||
| Support processes | None | No verification-of-payee service (inferred) | Immediate execution by default (inferred) | None | Policy: mistaken payments are the customer’s problem |
1. Decides to pay
- Evidence £42.50 owed for a shared licence
- Customer actions Opens the app
- Line of interaction
- Frontstage Banking app
2. Enters details
- Evidence Account number field
- Customer actions Types Lila’s account number
- Line of interaction
- Frontstage No check of name against account. F1
- Line of visibility
- Backstage Payee not verified (inferred)
- Line of internal interaction
- Support processes No verification-of-payee service (inferred)
3. Confirms
- Evidence Confirm button
- Customer actions Presses Confirm
- Line of interaction
- Frontstage No review screen; payment sent. F2
- Line of visibility
- Backstage Payment executed immediately (inferred)
- Line of internal interaction
- Support processes Immediate execution by default (inferred)
4. Spots the error
- Evidence Two digits reversed
- Customer actions Notices one second later
5. Looks for a way back
- Evidence Help: mistakes are the sender’s responsibility
- Customer actions Looks for cancel
- Line of interaction
- Frontstage No cancel; help text assigns blame. F3
- Line of visibility
- Backstage No recall request offered (inferred)
- Line of internal interaction
- Support processes Policy: mistaken payments are the customer’s problem
F1 Critical: money can go to the wrong account with no warning. F2 Major: nothing to catch the error before it becomes real. F3 Major: no recovery path, and help content that closes the door.
Where it broke
The app asked Jonah whether he meant it. Nothing asked whether it was right.
F1: Confirm checks intention, not data. A confirm button verifies that the person wanted to press it. Reversed digits pass that test every time. The check that matters compares the name with the account.
F2: the construction site had what the app lacked. Tape, markers and warnings slow people down where the risk is. The app put its fastest path through its most dangerous step.
F3: help content stood in for a recovery route. Telling the customer the mistake is theirs is a policy, not help. EU law already expects a bank to try to recover funds sent with a wrong account number.
The people this hurts most are those for whom reversed digits are more likely: people with dyslexia or dyscalculia, low vision, tremor, or anyone using a phone on the move. What the principle asks for is a pause before the hazard, not an apology after it.
Standards and duties
These references show where the idea already appears in EU law and European standards. They illustrate the concept; they are not a compliance assessment.
| Instrument | Type | What it asks that this app missed |
|---|---|---|
| European Accessibility Act, Directive (EU) 2019/882 | Law | Consumer banking services, including their apps, must be accessible |
| Instant Payments Regulation (EU) 2024/886 | Law | Euro-area payment providers must offer a free check of the payee’s name against the account before a transfer is authorised, for all credit transfers, not only instant ones |
| Payment Services Directive (EU) 2015/2366, Article 88 | Law | The bank is not liable for a payment sent with a wrong account identifier, but must make reasonable efforts to recover the funds |
| EN 301 549 and WCAG 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Harmonised standard | A financial transaction is reversible, checked for errors, or confirmed after a review step |
| WCAG 3.3.1 Error Identification and 3.3.3 Error Suggestion | W3C standard | When an error is detected, say what it is and how to fix it |
What good looks like
Move the check before the money. The other fixes make the check readable and the mistake recoverable.
| Fix | Fail point | Layer | Type | Likely owner |
|---|---|---|---|---|
| A payee check before Confirm: match, close match or no match, in plain words | F1 | Support processes | Structural | Bank, payments team |
| A review screen showing the payee’s name and the account number in readable groups | F2 | Frontstage | Quick | Digital team |
| For standard transfers, a short window to cancel; for instant ones, the check must come first | F2, F3 | Backstage | Structural | Bank, product owner |
| Help content that opens with the recall route: what to do, when, what happens next | F3 | Frontstage | Quick | Content, operations |
How to test for it
- Error injection. In a usability test with test accounts, give participants a payee with two digits reversed. Measure how many notice it at the review step.
- Review screen with assistive technology. Check that screen readers read account numbers in groups, not as one large number.
- Recall data. Track recall requests and complaints about mistaken payments before and after the payee check goes live.
- Content test. Ask participants what they would do after a mistaken payment, using only the help pages.
A confirm button asks whether you meant it. A check asks whether it is right.
Sources
- Center for Universal Design, NC State University, The Principles of Universal Design, version 2.0 (1997)
- Directive (EU) 2019/882, European Accessibility Act
- Regulation (EU) 2024/886, Instant Payments Regulation
- Mason Hayes & Curran, Instant Payments Regulation update
- Directive (EU) 2015/2366 on payment services, Article 88
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, criteria 3.3.1, 3.3.3 and 3.3.4
- W3C WAI, European Union accessibility policies