Other pages in this section Browser Based Redirection / AIS Browser Based Redirection / PIS App Based Redirection / AIS App Based Redirection / PIS App-to-browser redirection Redirection with TPP Generated QR code Decoupled Model A: Static PSU Identifier Decoupled Model B: ASPSP Generated Identifier Decoupled Model C: TPP Generated Identifier Decoupled Model D: PSU with a TPP Account ASPSP applies an available exemption Using an Available Exemption with a Customer Identifier
This content is best viewed on a desktop browser. 1 CEG Checklist Requirements 1PSU 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). 2 CEG Checklist Requirements 2PISPs must communicate information clearly to the PSU when obtaining consent in order to initiate the payment order. 3 CX Considerations 3PISPs 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. 4 CEG Checklist Requirements 4The 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). 5 CEG Checklist Requirements 5ASPSPs 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. 6 CEG Checklist Requirements 5ASPSPs 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. 7 CEG Checklist Requirements 6ASPSPs 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). 8 CX Considerations 7ASPSPs 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. 9 CX Considerations 8ASPSPs should inform the PSU on the outbound redirection screen that their session with the ASPSP is closed. 10 CEG Checklist Requirements 9PSUs must be redirected straight back to the PISP website/app on the same device where PISP displays confirmation of successful initiation. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 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). 24 2 PISPs must communicate information clearly to the PSU when obtaining consent in order to initiate the payment order. 8 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. 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). 1 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): Authentication screen (recommended). ASPSP to PISP redirection screen. 28 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). 1 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. 8 PSUs must be redirected straight back to the PISP website/app on the same device where PISP displays confirmation of successful initiation. 9 PSU must be redirected straight back to the PISP website/app on the same device where PISP displays confirmation of successful initiation. 26
Browser Based Redirection / AIS Previous Related articles Please select API specifications App Based Redirection / AIS Next