New Transfer Recipient Verification
Design a bank transfer setup that helps customers verify a new recipient, recognize uncertainty, and resist payment pressure.
The brief
Understand the problem
Background
A transfer to a new recipient is often irreversible once sent. Name checks, account details, saved contacts, and risk questions can reduce mistakes, but a match is not proof that a payment request is legitimate.
User context
Sofia is paying a builder for a kitchen deposit. The invoice arrived from a familiar email thread, but the account details differ from those used for an earlier payment.
Product problem
Sofia needs to verify who controls the destination account and understand conflicting signals without being overwhelmed or falsely reassured.
Objective
Create recipient entry, verification, risk review, and final confirmation states that support an informed transfer decision.
What to design
Define the experience
Required experience
- Enter or scan new recipient details
- Interpret the recipient name-check result
- Resolve a conflict with previously saved information
- Review the final destination and authorize the payment
Screens and states
- Recipient details
- Verification result
- Payment safety review
- Transfer confirmation
Core user flow
Follow the critical path
- 01
Sofia scans the invoice account details
- 02
The bank reports a partial name match and surfaces the older saved account
- 03
She pauses the transfer and calls the builder using a previously verified number
- 04
After correcting the details, she reviews and authorizes the payment
Product rules
Requirements and constraints
Requirements
- Display entered details in a format that supports careful comparison
- Explain exact, partial, unavailable, and failed name checks
- Keep warnings specific to the observed conflict
- Offer a safe pause path without losing entered data
- Repeat recipient, amount, timing, and reference at authorization
Constraints
- A successful name check cannot guarantee that the payment purpose is legitimate
- The interface must not reveal private recipient account information
- High-risk transfers may require an additional review period
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens covering a partial-match recovery
- Content variants for exact, partial, unavailable, and failed verification
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
lawMiller’s LawImmediate-memory performance is limited and can improve through meaningful recoding, but Miller’s ‘seven plus or minus two’ is not a universal UI item limit.
phenomenonInattentional BlindnessPeople focused on a demanding task can fail to notice an unexpected, fully visible event outside their current attentional goal.
modelShort-Term MemoryShort-term memory refers to limited retention of information over a brief interval when it has not yet become durable long-term knowledge.