Payment Initiation Services

Account Selection at ASPSP

This version is:

Published 3 years ago 21 Oct 2021

There are cases where the payment order submitted by PISPs to ASPSPs is incomplete, such as where the PSU’s account selection has not yet occurred.

Other pages in this section

User Journey

 

Main content image

 

There are cases where the payment order submitted by PISPs to ASPSPs is incomplete, such as where the PSU’s account selection has not yet occurred.

In these scenarios, OBIE considers that SCA only needs to be obtained once, as part of the initial interaction between ASPSPs and the PSU. The fact that the PSU has to then carry out account selection or provide other information does not invalidate the SCA just performed by the ASPSP.

Equally, the display of the account balance by the ASPSP as part of the account selection process in the payment initiation journey should not require an additional application of SCA. We understand the FCA is comfortable with this approach, however we note that the application of SCA (and interpretation of relevant requirements) is a matter for individual ASPSPs.

Wireframes

This content is best viewed on a desktop browser.

1

CEG Checklist Requirements 1
Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1.

2

CEG Checklist Requirements 2
PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2.

3

CEG Checklist Requirements 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.

6

CEG Checklist Requirements 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

9

CEG Checklist Requirements 9
Additional Parameters ASPSPs must allow PSUs to select the payment account to complete the payment order for execution. It is up to ASPSP to consider relevant obligations relating to the FCA’s High Cost Credit Review: Overdrafts consultation paper and policy statement (CP18/42) & (PS19/16)”

12

CEG Checklist Requirements 12
PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10.

13

CEG Checklist Requirements 13
Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12.

CEG Checklist Requirements & Customer Experience 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

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

ASPSPs could also display a message to prompt PSUs to authenticate to continue with their payment instruction.

Once 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

Additional Parameters

ASPSPs must allow PSUs to select the payment account to complete the payment order for execution.

It is up to ASPSP to consider relevant obligations relating to the FCA’s High Cost Credit Review: Overdrafts consultation paper and policy statement (CP18/42) & (PS19/16)”.

23

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“.

13

Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item 12.

27

Example cases where the payment order submitted by PISP is incomplete include: 

What the research says

“When account selection is done at the ASPSP, research amongst consumers has shown that 58% of participants prefer to be shown the balance for their selected payment account, before reviewing a payment. This was felt to assist in good personal financial management.”  

Click for customer research