Initiation – Customer present-NOT USED-

User Journey

This core journey will enable the PISP to initiate variable recurring payments within the agreed set of parameters which will result in a single domestic payment being processed by the ASPSPs as a Single Immediate Payment (SIP) via Faster Payments where the customer is required to be in session.

This journey demonstrates VRP payment initiation by the PISP where the PSU is required to be in session for each payment and undergo SCA at the PISP.

However, delegated SCA can be performed 

a) either at the PISP or third party as a delegated SCA or

b) SCA at the ASPSP.

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 enabling the PSU to amend:

Payee Account Name.
Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN).
Payment Reference - This is optional but it is good practice to be populated for a payment.
Maximum amount per payment and Currency (GBP for UK implementations).
Maximum amount per month.
Expiry Date (Ongoing or a Specific Date).
Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP.

CEG Checklist Requirements 2

PSU payment Account Selection

PISPs must provide PSUs at least one of the following options:

• Enter their Payer's payment Account Identification details.
•PISPs must allow PSUs to enter their payment Account Identification details in at least one of the ways specified in the OBIE V3 Read/Write API Specifications (e.g. account number and sort code - with additional roll number if required, IBAN, PAN, Paym and other formats).
• Select their Account Identification details (this assumes they have been saved previously).
• Select their ASPSP in order to select their PSU payment Account from there later on in the journey.

Note1: In some of the above cases, PISPs may also need PSUs to provide their ASPSP name so that PISPs can check whether ASPSPs will be able to match the account identifier to the underlying PSU payment account.

Note 2: The use of IBAN as an identification of the payer account for UK ASPSPs is not expected to be heavily used as account and sortcode are the main account identifiers used in the UK. IBAN however will be used by non UK ASPSPs implementing OBIE standards and offering their services in the UK.

CEG Checklist Requirements 3

Use of clear language to the PSU that they will be consenting to give the PISP the ability to make payment on a (sporadically or periodically) recurring basis.

PISPs must display the company’s trading name/brand name (i.e. the Client Name) to the PSU during the setup and revocation of consent. If the PISP is only trading with its registered company name then it must display that name to the PSU.

If the PISP is not the customer-facing entity and there is an Agent who is acting on behalf of the PISP, then the Agent must make the PSU aware that they are acting as an agent on behalf of the PISP and must also, display the PISP’s full trading name/brand name or registered company name whichever is the customer-facing brand of the PISP.

PISPs must also, populate the Agent company name in the ‘On behalf of’ field of the software statement, in order to inform the ASPSP about the agency relationship and allow the ASPSP to be able to display this information to the PSU (please refer to item #5). Only in instances where there is an Agent acting on behalf of the PISP, the ‘On Behalf of’ name must be displayed to the PSU. PISPs must not populate the ‘ On behalf of’ field with the details of their TSP.

CEG Checklist Requirements 4

PSU Consent to PISP

PISPs must display the following information in the consent screen:

Control Parameters

Payment Reference, and any supplementary info, if it has been entered by PSUs or pre-populated by PISPs in item #1.
Maximum amount per payment and Currency.
Maximum amount per month.
Expiry Date as selected by the PSU.
Payee Information

Payee Account Name.
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 an eCommerce payment scenario) PISPs could choose whether to display this information or not.
Payer Information

PSU payment Account Identification and/or the selected ASPSP (based on item #2 options).
Note: 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.

CEG Checklist Requirements & Customer Experience Considerations

PISPs must enable the PSU to provide the below: 

  • Payee Account Name.
  • Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN).

22

PISPs must display the following information in the consent screen:

  • Payment Reference, and any supplementary info, if it has been entered by PSUs or pre-populated by PISPs in item #1.

Payee Information

  • Payee Account Name.
  • 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 an eCommerce payment scenario) PISPs could choose whether to display this information or not.

Payer Information

  • 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. PSU already provided as part of VRP consent) PISPs could choose whether to display this information or not.
24

SCA Authentication must be the only action required by the PSU.

19b

PISP Confirmation 

PISPs must display the information received from the ASPSP. This information may include:

The unique identifier assigned to the VRP setup by ASPSPs.
25

26

 

What the research says

Consumer research for Single Immediate Payment has shown that 64% of customers prefer to be shown confirmation that the payment has been received at the TPP. This would provide reassurance that the process has worked.”

Click for Customer Research 

v3.1.8