User Journey

PSUs can setup, through PISPs, an instruction to their ASPSPs to make a one-off payment for a specific amount to a specific payee on a specific future date.

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 scenario, 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 Future Dated Payments 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: As per Single Domestic Payments – a/c selection @ PISP, item #1.

CEG Checklist Requirements 2

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

CEG Checklist Requirements 3

Execution Date: PISPs must either enable PSUs to select the expected execution date or populate and display the expected execution date for the payment order.

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

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 and any supplementary information about difference in actual execution date.

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 message to PSUs to inform that amendment or cancellation of the payment 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

22

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

24

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

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

ASPSPs must display the payment details and any supplementary information about difference in actual execution date.

    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 message to PSUs to inform that amendment or cancellation of the payment 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:

    Consumer research has shown that 82% of consumers would like to see the payment schedule at least once in the journey

    Click for Customer Research