The User Journey for Nexus Payments
This section gives a non-technical description of the process a Sender would take to setup and make a cross-border payment via Nexus.
Based on the requirements above, we mapped out a prototype user flow for setting up a cross-border payment. Designing this “user journey” at the start is useful because it reveals the functionality that would need to be provided by the IPSs and member banks.
The steps shown in these example screens are in a particular order for (a) usability and (b) to support a logical and efficient flow of communication between the different participants in a cross-border payment (explained in detail in An End-to-End Payment Through Nexus).
Depending on functionality in the Destination IPS and its member banks, not all the steps and features will be available. Nexus is designed to accommodate limitations and the absence of certain functionality.
The following screens are examples only. Usability testing with real users would be essential to improve these before using them in production. To define a minimum (good) standard of usability and user experience across the network, Nexus could provide these screens as a kit to banks and PSPs, along with the necessary validation scripts. This would also reduce the amount of work required by banks and PSPs to become Nexus enabled.
Of course, banks and PSPs would be able to apply their own branding, styling and change the explanatory text to the bank’s own style and tone. The intention here is not to force banks to use identical screens, but to ensure a basic standard of usability, given the varying quality of usability design between different bank’s digital services.