Customer Experience Guidelines
One of the primary ambitions of the Customer Experience Guidelines is to provide simplification and consistency throughout each stage of the Open Banking implementation. As such, we have defined a core set of payment initiation journeys.
Other pages in this section
Open Banking API specifications support Payment Initiation Services (PIS) that enable a PISP to initiate a payment order, with the PSU’s explicit consent, from their online payment account held at their ASPSP. The PISP is then further able to retrieve the status of a payment order. This section describes how each of the Participants (PISPs and ASPSPs) in the delivery of these services can optimise the customer experience for these services. Furthermore, it provides some clarifications to these Participants on the usage of the APIs which are not covered by the technical specifications, and some best practice guidelines for implementation of the customer journeys.
1FCA consultation on updated Approach to RTS and EBA guidelines under revised PSD2 and CEG Checklist Reference
Please note that ASPSPs do not need to support the initiation of certain payment methods described in this section by a PISP, where the ASPSP does not support such transactions through any of their own online channels (such as future dated foreign transactions and bulk payment files).
If the customer is able to initiate, for example, international payments, recurring transactions or a batch file of payments online, they should also be able to do so via a PISP, irrespective of the channel the customer has used to access the PISP1.
Single Domestic Payments
PSUs can initiate, by providing their consent to PISPs, an instruction to their ASPSPs to make a one-off payment for a specific amount to a specific payee.
This version was published 2 Years & 4 Months ago
21 Oct 2021
In some scenarios, an additional step in ASPSPs' journeys may be required to display supplementary information to PSUs. ASPSPs should determine the situations where this supplementary information is required, having regard to the principle that parity should be maintained between Open Banking journeys and ASPSPs’ online channel journeys.
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.
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.
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.
PSUs can initiate, through PISPs, single international payments from their GBP or foreign currency payment accounts. Payments can be made in any currency and to any country, using a number of routing options in order to meet the priority required, provided that functionality is available to PSUs when making international payments directly from their online payment account.
Business PSUs can initiate, through PISPs, bulk/batch payments allowing them to make multiple payments from their payment accounts.
PSUs can setup, through PISPs, payments which require multiple parties with delegated user authority to authorise a payment order. This functionality can be used by ASPSPs for any payment initiation that requires multiple authorities (including consumers, SMEs and Corporates).
PISPs can request confirmation of funds on a PSU's payment account for the amount necessary for the execution of the payment transaction initiated through the PISP. ASPSPs must respond to such request from a PISP with an immediate ‘Yes’ or ‘No’ confirmation and should take into account the same information.
In cases where the PSU selects their account at the ASPSP as shown in the journey Single Domestic Payments – a/c selection @ ASPSP, the PISP may not be able to obtain the PSU's account details (sort code and account number) from the PSU directly within their consent journey.
Variable Recurring Payments
VRPs with an SCA exemption is defined as “VRP Payments instructed under a VRP Consent with Consent Parameters that qualify for an SCA Exemption such that, following successful VRP Consent Setup, subsequent individual VRP Payments can be made without further authorisation from the PSU.”
For the purpose of simplicity, we have defined the term 'Sweeping Consents' and 'Sweeping Payments' to refer to 'VRP Consents' & 'VRP Payments' respectively when they are dealt with under sweeping access.
VRPs with delegated SCA is defined as “VRP Payments that are initiated by the PISP and do not rely on the application of an SCA exemption by the ASPSP, but rather the application of delegated SCA to each individual VRP Payment.”
Permissions & Data Clusters for AIS journeys Previous
Account Selection at ASPSP Next