User Journey

PSUs can setup, through PISPs, an instruction to their ASPSPs to make a series of payments of a specific amount to a specific payee on a number of specified future dates or on a regular basis.

The example reference journey illustrates account selection occurring in the PISP domain. However, please note that account selection can take place at the ASPSP domain. In this case, please follow the approach of reference journey Single Domestic Payments – a/c selection @ ASPSP

Note: OBIE Standards do not currently support the amendment or cancellation of Domestic Standing Orders via PISPs. These payments may be amended or cancelled via the ASPSP’s direct online channel (where supported). Cancellation of these payments must be consistent with available capabilities on ASPSP’s existing online platform, as well as, in accordance with the provisions of the PSRs relating to revocation of payment orders.

 

Wireframes

CEG Checklist Requirements 1

Minimum Set of Parameters
PISPs must either allow PSUs to specify the below minimum set of parameters or pre-populate them for the PSUs:
Creditor Account Name.
Creditor Account Identification (e.g. account number and sort code or roll number for UK implementations).
Reference of the payment (as per best practice).
Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP.

CEG Checklist Requirements 2

tanding Order Schedule(s)
PISPs must either allow PSUs to select at least one of following options or pre-populate them for the PSUs:
The First payment date, payment Amount and Currency (GBP for UK implementations).
The Recurring payment date, payment Amount and Currency (only if different from the first payment amount and date).
If standing order is not open ended:
Either the Final payment Date (only if different from the Recurring payment date), payment Amount and Currency (GBP for UK implementations).
Or the Number of payments to be made by the standing order.
The Frequency of the payments (for available options on standing order frequency, please refer to Appendix section 7.4.1).

CEG Checklist Requirements 3

PSU payment Account Selection: As perSingle Domestic Payments – a/c selection @ PISP, item #2.

CEG Checklist Requirements 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:
The Standing Order Schedule parameters including first payment, recurring payment, final payment and frequency as selected in item #3.
Payee Account Name.
Payment Reference and any supplementary info, if it has been entered by PSUs or prepopulated 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.

CX Considerations 5

As per Single Domestic Payments – a/c selection @ PISP, item #4.

CX Considerations 6

As per Single Domestic Payments – a/c selection @ PISP, item #5.

CEG Checklist Requirements 7

As per Single Domestic Payments – a/c selection @ PISP, item #8.

CEG Checklist Requirements 8

ASPSPs must display the payment details, schedule and any supplementary information about difference in actual execution day for each transaction.

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

CX Considerations 10

As per Single Domestic Payments – a/c selection @ PISP, item #9.

CEG Checklist Requirements 11

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

CX Considerations 12

PISPs must provide a message to PSUs to inform that modification or cancelling of the standing order must be done at their ASPSP.

CEG Checklist Requirements 13

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

Requirements and Considerations

CEG Checklist Requirements & CX Considerations

Minimum Set of Parameters

PISPs must either allow PSUs to specify the below minimum set of parameters or pre-populate them for the PSUs:

Creditor Account Name.
Creditor Account Identification (e.g. account number and sort code or roll number for UK implementations).
Reference of the payment (as per best practice).
Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP.

 

22

Standing Order Schedule(s)

PISPs must either allow PSUs to select at least one of following options or pre-populate them for the PSUs: 

The First payment date, payment Amount and Currency (GBP for UK implementations).

The Recurring payment date, payment Amount and Currency (only if different from the first payment amount and date).

If standing order is not open ended: 

Either the Final payment Date (only if different from the Recurring payment date), payment Amount and Currency (GBP for UK implementations).
Or the Number of payments to be made by the standing order.

The Frequency of the payments (for available options on standing order frequency, please refer to Appendix section PIS parameters and considerations.

21

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

24

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:

  • The Standing Order Schedule parameters including first payment, recurring payment, final payment and frequency as selected in item #3.
  • Payee Account Name.
  • Payment Reference and any supplementary info, 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: IfPSU 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.
  • Ithis has been pre-populated by PISPs (e.g. in a eCommerce payment scenario) PISPs could choose whether to display this information or not.

8

ASPSPs must display the payment details, schedule andany supplementary information about difference in actual execution day for each transaction.

20

28

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

PISPs must provide a message to PSUs to inform that modification or cancelling of the standing order must be done at their ASPSP.

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

27

Note:

If the payment account identifier used by PSUs to setup a future dated payment order, via PISPs, is no longer valid (e.g. expired/reported lost stolen PAN) ASPSPs should still allow the execution of the payment, on the scheduled date for which were setup.

What the research says:

Research amongst consumers has shown that they consider it important to be able to schedule a recurring payment to be paid on the same date every month. There is currently some frustration with providers who do not take payments on set dates but rather indicate a window when payment will be taken

Click for Customer Research