Design rationale: payment receive code (FX app)
Synopsis
#UX, #IA, #UI,
An example communicating designs and the rationale for those design decisions.
This was part of a standalone native app for FX (foreign exchange) payments and focusses on a feature/function allowing the bank’s customers to share a code with the recipient who can then securely ‘receive’ the payment – something competitors were already doing and a gap in our product offering that needed filling.
The USP here is it’s fee free when done through this method for both sender and receiver (something many competitors were not in a position to do).
Team
Lead Designer UX/UI (myself)
Designer UX/UI (mid weight)
Designer – illustration specialist
PO
Digital Analyst
Dev pod
My role in this project
Design / CX strategy, Design approach & decisions, stakeholder mgmt, reviews & sign offs, IA/UX
+ Hands on Design
(UX – 65% / UI 35%)
The challenge
#IA, #UX, #Content, #UI
Communicating to customers how this feature works and that a customer does need to take further action (sharing the code), required careful thought – it would be very easy to miss this and mistake the ‘confirmation screen’ as the end of the process (we knew this already through a user concept test we ran via Foolproof).
The Design
Excerpt examples
Excerpts
Below are excerpts from my documentation of design rationale & early concept screens, ahead of further exploration / user validation
