Browser Based Redirection – PIS
User Journey
Wireframes
To demonstrate web based redirection we have used one variation of PIS journey (Sec Single Domestic Payments – a/c selection @ PISP) as an example, where the ASPSP receives all the details of the payment order from the PISP. This redirection flow applies to other variations of PIS journeys covered in detail under section Payment Initiation Services (PIS).
CEG Checklist Requirements 1
PSU payment Account Selection PISPs must provide PSUs at least one of the following options: Enter their Payer's payment Account Identification details. Select their Account Identification details (this assumes they have been saved previously).
CEG Checklist Requirements 2
PISPs must communicate information clearly to the PSU when obtaining consent in order to initiate the payment order.
CX Considerations 3
PISPs should make the PSU aware through an inbound redirection screen that they are being taken to their ASPSP for authentication to complete the payment. PISP should display in the Redirection screen the Payment Amount, Currency and the Payee Account Name to make the PSU aware of these details.
CEG Checklist Requirements 4
The redirection must take the PSU to an ASPSP web page (desktop/mobile) for authentication purposes only without introducing any additional screens. The web based authentication must have no more than the number of steps that the PSU would experience when directly accessing the web based ASPSP channel (desktop/mobile).
CEG Checklist Requirements 5
ASPSPs must display, as minimum, the Payment Amount, Currency and the Payee Account Name to make the PSU aware of these details (unless an SCA exemption is being applied). These details must be displayed as part of the authentication journey on at least one of the following screens without introducing additional confirmation screens (unless supplementary information is required, refer to section Single Domestic Payments – Supplementary info): 1. Authentication screen (recommended). 2. ASPSP to PISP redirection screen.
CEG Checklist Requirements 5
ASPSPs must display, as minimum, the Payment Amount, Currency and the Payee Account Name to make the PSU aware of these details (unless an SCA exemption is being applied). These details must be displayed as part of the authentication journey on at least one of the following screens without introducing additional confirmation screens (unless supplementary information is required, refer to section 4.1.2): 1. Authentication screen (recommended). 2. ASPSP to PISP redirection screen.
CEG Checklist Requirements 6
ASPSPs web based authentication must have no more than the number of steps that the PSU would experience when making a payment directly through the ASPSP web based channel (desktop/mobile).
CX Considerations 7
ASPSPs should have an outbound redirection screen which indicates the status of the request and informs the PSU that they will be automatically taken back to the PISP.
CX Considerations 8
ASPSPs should inform the PSU on the outbound redirection screen that their session with the ASPSP is closed.
CEG Checklist Requirements 9
PSUs must be redirected straight back to the PISP website/app on the same device where PISP displays confirmation of successful initiation.
CEG Checklist Requirements & CX Considerations
- Enter their Payer’s payment Account Identification details.
- Select their Account Identification details (this assumes they have been saved previously).
- Authentication screen (recommended).
- ASPSP to PISP redirection screen.
