An authentication flow in which the PSU provides a static identifier to the TPP (AISP/PISP/CBPII) which is then used by the ASPSP to enable the PSU to authenticate in their ASPSP app on a separate device.
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 CX Considerations 2PISPs should present the PSU with the authentication options supported by the ASPSP which in turn can be supported by the TPP device/channel (for e.g. A TPP kiosk that can only support authentication by ASPSP mobile app). 3 CX Considerations 3If PISPs and ASPSPs support Model A, then the TPP should request from the PSU the identifier which is supported by their ASPSP. 4 CX Considerations 4The PISP should make the PSU aware about how this identifier will be used. 5 CEG Checklist Requirements 5After the PSU enters the specified identifier, if the PSU has an ASPSP app then the ASPSP must notify the PSU through the ASPSP app for authentication purposes, without introducing any additional screens. The notification must clearly mention the payment request with the amount and the payee. 6 CEG Checklist Requirements 6The ASPSP app based authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP mobile app (biometric, passcode, credentials). 7 CX Considerations 7If the PSU is logged off from the ASPSP app, the ASPSP must make the PSU aware that they have been logged off and notify them to check back on the originating TPP app. 8 CEG Checklist Requirements 8The PISP must confirm successful confirmation of payment 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 should present the PSU with the authentication options supported by the ASPSP which in turn can be supported by the TPP device/channel (for e.g. A TPP kiosk that can only support authentication by ASPSP mobile app). 3 If PISPs and ASPSPs support Model A, then the TPP should request from the PSU the identifier which is supported by their ASPSP. 4 The PISP should make the PSU aware about how this identifier will be used. 5 After the PSU enters the specified identifier, if the PSU has an ASPSP app then the ASPSP must notify the PSU through the ASPSP app for authentication purposes, without introducing any additional screens. The notification must clearly mention the payment request with the amount and the payee. 1nn28 6 The ASPSP app based authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP mobile app (biometric, passcode, credentials 1 7 If the PSU is logged off from the ASPSP app, the ASPSP must make the PSU aware that they have been logged off and notify them to check back on the originating TPP app. 8 The PISP must confirm successful confirmation of payment initiation. 26
Redirection with TPP Generated QR code Previous Related articles Please select API specifications Decoupled Model B: ASPSP Generated Identifier Next