Other pages in this section Account Selection at PISP Account Selection at PISP – Supplementary info Account Selection at ASPSP Scheduled Payments – Future Dated Standing Orders International Payments Bulk / Batch Payments Multi-authorisation Payments Confirmation of Funds for PISP – Yes / No Response
This content is best viewed on a desktop browser. 1 CEG Checklist Requirements 1Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1. 2 CEG Checklist Requirements 2PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 3 CEG Checklist Requirements 3PSU Consent to PISP PISPs must request for the PSUs’ consent to the payment initiation in a clear and specific manner. PISPs must display the following information in the consent screen: Payment Amount and Currency (GBP for UK implementations). Payee Account Name. Payment Reference, if it has been entered by PSUs or prepopulated by PISPs in item #1. Selected ASPSP (based on item #2 options). For Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN): If this has been provided by PSUs in item #1, then PISPs must also display this in the consent screen to allow PSUs to check and verify correctness. If this has been pre-populated by PISPs (e.g. in a eCommerce payment scenario) PISPs could choose whether to display this information or not. 4 CX Considerations 4As per Single Domestic Payments – a/c selection @ PISP, item #4. 5 CX Considerations 5As per Single Domestic Payments – a/c selection @ PISP, item #5. 6 CEG Checklist Requirements 6ASPSPs must apply SCA including dynamic linking, unless an exemption applies. The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel 7 CX Considerations 7ASPSPs could also display a message to prompt PSUs to authenticate to continue with their payment instruction. 8 CX Considerations 8Once the PSU has selected their account, ASPSPs should display the following information to the PSU: Payment Amount and Currency (GBP for UK implementations). Payee Account Name. Payment Reference, if it has been entered by PSUs or prepopulated by PISPs in item #1. The account selected by the PSU for payment. Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN). 9 CEG Checklist Requirements 9Additional Parameters ASPSPs must allow PSUs to select the payment account to complete the payment order for execution. 10 CX Considerations 10ASPSPs should inform PSUs about their “point of no return” for making the payment and that their payment will be made after pressing the Proceed button. Example wording: “Press Proceed to make payment“. 11 CX Considerations 11ASPSPs should inform PSUs about their “point of no return” for making the payment and that their payment will be made after pressing the Proceed button. Example wording: “Press Proceed to make payment“. 12 CX Considerations 12As per 4.1.1, item #9. 13 CEG Checklist Requirements 13PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10. 14 CEG Checklist Requirements 14Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1. 22 2 PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 24 3 PSU Consent to PISP PISPs must request for the PSUs’ consent to the payment initiation in a clear and specific manner. PISPs must display the following information in the consent screen: Payment Amount and Currency (GBP for UK implementations). Payee Account Name. Payment Reference, if it has been entered by PSUs or prepopulated by PISPs in item #1. Selected ASPSP (based on item #2 options). For Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN): If this has been provided by PSUs in item #1, then PISPs must also display this in the consent screen to allow PSUs to check and verify correctness. If this has been pre-populated by PISPs (e.g. in a eCommerce payment scenario) PISPs could choose whether to display this information or not. 8 4 As per Single Domestic Payments – a/c selection @ PISP, item #4. 5 As per Single Domestic Payments – a/c selection @ PISP, item #5. 6 ASPSPs must apply SCA including dynamic linking, unless an exemption applies. The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel 19 1 7 ASPSPs could also display a message to prompt PSUs to authenticate to continue with their payment instruction. 8 ASPSPs should inform PSUs about their “point of no return” for making the payment and that their payment will be made after authentication occurs. Example wording: “Authenticate to make payment”. For recognition based biometrics (e.g. Face ID) which can be more immediate the biometric authentication should be invoked after a delay or through a call to action to allow the PSU the ability to view the details. ASPSPs could display the balance of PSUs payment account(not shown on user journey)as part of the authentication journey on any of the following screens: ASPSPs’ Authentication screen. ASPSP to PISP redirection screen. Displaying the balance in this instance need not require any additional strong customer authentication 9 Additional Parameters ASPSPs must allow PSUs to select the payment account to complete the payment order for execution. 23 10 Generic ASPSP to PISP redirection screen and message. Please refer to section Effective use of redirection screens. 11 Generic ASPSP to PISP redirection screen and message. Please refer to section Effective use of redirection screens. 12 If PSUs provide their payment account identification details (as per item #2 options), the PISP could, with the consent of the PSU, save the account details for future transactions (such as making further payments or initiating refunds back to PSUs) where this is part of the payment initiation service explicitly requested by the PSU. For example, a merchant, upon request from the PSU, may initiate a refund back to the PSU, by instructing the same PISP that initiated the initial PSU transaction to use the saved PSU payment account identification details as the beneficiary details for the refund. This will be dependant on the same PISP being used by both the PSU and the merchant, their specific contractual terms and relevant regulatory obligations under GDPR/PSRs. Moreover, PISPs can use this consent to provide a hint of the PSU’s identity using the customer identifier as part of the payment request to enable the subsequent payment journey contemplated in section Authentication methods . 13 PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10. 25 26 14 Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. 27
Account Selection at PISP – Supplementary info Previous Related articles Please select API specifications Scheduled Payments – Future Dated Next