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 3Execution Date: PISPs must either enable PSUs to select the expected execution date or populate and display the expected execution date for the payment order. 4 CEG Checklist Requirements 4PSU Consent to PISP PISPs must request for the PSUs’ consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen: Payment Execution Date. Payment Amount and Currency (GBP for UK implementations). Payee Account Name. Payment Reference, if it has been entered by PSUs or pre-populated by PISPs in item #1. PSU payment Account Identification and/or the selected ASPSP (based on item #2 options). Note 1: If PSU payment Account identification is selected in item #2, PISPs should mask the PSU payment Account details on the consent screen. Otherwise, if the PSU payment Account identification has been input by PSUs in item #2, PISPs should not mask these details to allow PSUs to check and verify correctness. Note 2: If PSU payment Account identification is provided by PSUs in item #2, PISPs could use this to identify and display the ASPSP without having to ask PSUs. 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 . 5 CX Considerations 5As per Single Domestic Payments – a/c selection @ PISP, item #4. 6 CX Considerations 6As per Single Domestic Payments – a/c selection @ PISP, item #5. 7 CEG Checklist Requirements 7As per Single Domestic Payments – a/c selection @ PISP, item #8. 8 CEG Checklist Requirements 8ASPSPs must display the payment details and any supplementary information about difference in actual execution date. 9 CX Considerations 9ASPSPs 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“. 10 CX Considerations 10As per Single Domestic Payments – a/c selection @ PISP, item #9. 11 CEG Checklist Requirements 11PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10. 12 CX Considerations 12PISPs must provide message to PSUs to inform that amendment or cancellation of the payment must be done at their ASPSP. 13 CEG Checklist Requirements 13Further 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 Execution Date: PISPs must either enable PSUsto select the expected execution date or populate and display the expected execution date for the payment order. 21 4 PSU Consent to PISP PISPs must request for the PSUs’ consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen: •Payment Execution Date. •Payment Amount and Currency (GBP for UK implementations). •Payee Account Name. •Payment Reference, if it has been entered by PSUs or pre-populated by PISPs in item #1. •PSU payment Account Identification and/or the selected ASPSP (based on item #2 options). •Note 1: If PSU payment Account identification is selected in item #2, PISPs should mask the PSU payment Account details on the consent screen. Otherwise, if the PSU payment Account identification has been input by PSUs in item #2, PISPs should not mask these details to allow PSUs to check and verify correctness. •Note 2: IfPSU payment Account identification is provided by PSUs in item #2, PISPs could use this to identify and display the ASPSP without having to ask PSUs. 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 5 As per Single Domestic Payments – a/c selection @ PISP, item #4. 6 As per Single Domestic Payments – a/c selection @ PISP, item #5. 7 As per Single Domestic Payments – a/c selection @ PISP, item #8. 19 1 8 ASPSPs must display the payment details and any supplementary information about difference in actual execution date. 20 28 9 ASPSPs 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“. 10 As per Single Domestic Payments – a/c selection @ PISP, item #9. 11 PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10. 25 26 12 PISPs must provide message to PSUs to inform that amendment or cancellation of the payment must be done at their ASPSP 13 Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. 27
Account Selection at ASPSP Previous Related articles Please select API specifications Standing Orders Next