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 1AISPs must initially ask the PSU to identify the ASPSP so that the consent request can be constructed in line with the ASPSP’s data clusters. 2 CX Considerations 2AISP should make the PSU aware on the inbound redirection screen that they will be taken to their ASPSP for authentication for account access. 3 CEG Checklist Requirements 3The redirection must take the PSU to the 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). 4 CX Considerations 4ASPSP should make the PSU aware that the PSU login details will not be visible to the AISP. 5 CEG Checklist Requirements 5PSUs must be able to confirm the account(s) which they would like the AISP to have access to without having to go through any further unnecessary screens. 6 CX Considerations 6SPSP 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 AISP. 7 CX Considerations 7ASPSP should inform the PSU on the outbound redirection screen that their session with the ASPSP is closed. 8 CEG Checklist Requirements 8AISPs should confirm the successful completion of an account information data request. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 AISPs must initially ask the PSU to identify the ASPSP so that the consent request can be constructed in line with the ASPSP’s data clusters. 8 2 AISP should make the PSU aware on the inbound redirection screen that they will be taken to their ASPSP for authentication for account access. 3 The redirection must take the PSU to the 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 4 ASPSP should make the PSU aware that the PSU login details will not be visible to the AISP. 5 PSUs must be able to confirm the account(s) which they would like theAISP to have access to without having to go through any further unnecessary screens. 1 6 ASPSP 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 AISP. 7 ASPSP should inform the PSU on the outbound redirection screen that their session with the ASPSP is closed. 8 AISPs should confirm the successful completion of an account information data request. 18
Authentication Methods Previous Related articles Please select API specifications Browser Based Redirection / PIS Next