An authentication flow in which the PSU provides a dynamic identifier, generated by the TPP (AISP/PISP/CBPII), used by the ASPSP to identify the PSU through the ASPSP app.
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 1For this step, please refer Section 4.1.1, step 1 & step 2. 2 CX Considerations 2PISPs must present PSUs with the authentication options supported by the ASPSP which in turn can be supported by the PISP device/channel (e.g. A PISP kiosk that can only support authentication by ASPSP mobile app). 3 CX Considerations 3If PISPs and ASPSPs support Model C then PISPs must display an identifier generated from the ASPSP to the PSU (e.g. QR code) and information on how the identifier should be used within the ASPSP app (e.g scan QR code with the ASPSP app). 4 CX Considerations 4PSUs should be able to easily use the identifier presented by the PISP application (e.g. scan the code from the Kiosk in this instance) without much friction (e.g of manually entering an alphanumeric code). 5 CEG Checklist Requirements 5After the PSU the scans identifier from the PISP within the ASPSP app, then the ASPSP must display the payment request and clearly mention the amount and the payee and payment account. 6 CEG Checklist Requirements 6ASPSPs performs SCA. 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). 7 CX Considerations 7ASPSPs must make the PSU aware that they have been logged off from the ASPSP app and notify them to check back on the originating PISP 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 For this step, please refer Section Single Domestic Payments – a/c selection @ PISP), step 1 & step 2. 2 PISPs must present PSUs with the authentication options supported by the ASPSP which in turn can be supported by the PISP device/channel (e.g. A PISP kiosk that can only support authentication by ASPSP mobile app). 3 If PISPs and ASPSPs support Model C then PISPs must display an identifier generated from the TPP app to the PSU (e.g. QR code) and information on how the identifier should be used within the ASPSP app (e.g scan QR code with the ASPSP app). 4 PSUs should be able to easily use the identifier presented by the PISP application (e.g. scan the code from the Kiosk in this instance) without much friction (e.g of manually entering an alphanumeric code). 5 After the PSU scans the identifier from the PISP within the ASPSP app, then the ASPSP must display the payment request and clearly mention the amount and the payee and payment account. 28 6 ASPSPs performs SCA. 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 ASPSPs must make the PSU aware that they have been logged off from the ASPSP app and notify them to check back on the originating PISP app. 8 The PISP must confirm successful confirmation of payment initiation. 26
Decoupled Model B: ASPSP Generated Identifier Previous Related articles Please select API specifications Decoupled Model D: PSU with a TPP Account Next