A decoupled authentication flow in which the TPP (AISP/PISP/CBPII) provides the ASPSP a stored PSU identifier from a previous PSU transaction. This is used by the ASPSP to enable the PSU to authenticate using thier 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 CX Considerations 1PISP IoT device through voice enabled commands asks if they would like to checkout for the requested payment using their stored ASPSP account. After the PSU confirms, the PISP uses the stored PSU identity with the ASPSP to request for payment. 2 CEG Checklist Requirements 2The ASPSP must notify the PSU through the ASPSP app for authentication purposes only without introducing any additional screens. The notification must clearly mention the payment request with the amount and the payee. 3 CEG Checklist Requirements 3The 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). 4 CX Considerations 4The ASPSP 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. 5 CEG Checklist Requirements 5The PISP must confirm successful confirmation of payment initiation. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 PISP IoT device through voice enabled commands asks if they would like to checkout for the requested payment using their stored ASPSP account. After the PSU confirms, the PISP uses the stored PSU identity with the ASPSP to request for payment. 2 The ASPSP must notify the PSU through the ASPSP app for authentication purposes only without introducing any additional screens. The notification must clearly mention the payment request with the amount and the payee. 1 28 3 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 4 The ASPSP 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. 5 The PISP must confirm successful confirmation of payment initiation. 26
Decoupled Model C: TPP Generated Identifier Previous Related articles Please select API specifications ASPSP applies an available exemption Next