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 Get Started Authentication Methods Account Information Services Payment Initiation Services Card Based Payment Instrument Issuers – CBPIIs Dashboards Customer Experience Checklist Appendices Change Log
Single Domestic Payments Account Selection at PISP Where all information for a complete payment order is passed from PISPs to ASPSPs, once authenticated, PSUs must be directed back to the PISP domain without any further steps taking place in the ASPSP domain. View journey Account Selection at PISP – Supplementary Info 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. View journey BACS and CHAPS 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. View journey Account Selection at ASPSP Open Banking Ltd (OBL) 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. View journey Scheduled Payments – Future Dated Through a PISP the PSUs can setup an instruction to their ASPSP to make a one-off payment for a specified amount to a specified payee – on a specified future date. View journey
Account Selection at PISP Where all information for a complete payment order is passed from PISPs to ASPSPs, once authenticated, PSUs must be directed back to the PISP domain without any further steps taking place in the ASPSP domain. View journey
Account Selection at PISP – Supplementary Info 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. View journey
BACS and CHAPS 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. View journey
Account Selection at ASPSP Open Banking Ltd (OBL) 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. View journey
Scheduled Payments – Future Dated Through a PISP the PSUs can setup an instruction to their ASPSP to make a one-off payment for a specified amount to a specified payee – on a specified future date. View journey
Other Payments Standing Orders Through a PISP, PSUs can setup an instruction to their ASPSPs to make a series of payments of a specified amount to a specified payee on a number of specified future dates or on a regular basis. View journey International Payments From a PISP, PSUs can initiate single international payments from their GBP or foreign currency payment accounts. Payments can be made in any currency and to any country. View journey Bulk / Batch Payments Business PSUs can initiate, through PISPs, bulk/batch payments allowing them to make multiple payments from their payment accounts. View journey Multi-authorisation Payments Through PISPs, PSUs can setup payments which require multiple parties with delegated user authority to authorise payment orders. This functionality can be used by ASPSPs for any payment initiation that requires multiple authorities View journey Confirmation of Funds for PISPs 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. View journey Payment Refunds When the PSU provides their explicit consent to the PISP to initiate a payment order; the PSU also provides permission for the PISP to request their account details from their ASPSP for the purposes of providing a future refund. View journey
Standing Orders Through a PISP, PSUs can setup an instruction to their ASPSPs to make a series of payments of a specified amount to a specified payee on a number of specified future dates or on a regular basis. View journey
International Payments From a PISP, PSUs can initiate single international payments from their GBP or foreign currency payment accounts. Payments can be made in any currency and to any country. View journey
Bulk / Batch Payments Business PSUs can initiate, through PISPs, bulk/batch payments allowing them to make multiple payments from their payment accounts. View journey
Multi-authorisation Payments Through PISPs, PSUs can setup payments which require multiple parties with delegated user authority to authorise payment orders. This functionality can be used by ASPSPs for any payment initiation that requires multiple authorities View journey
Confirmation of Funds for PISPs 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. View journey
Payment Refunds When the PSU provides their explicit consent to the PISP to initiate a payment order; the PSU also provides permission for the PISP to request their account details from their ASPSP for the purposes of providing a future refund. View journey
Variable Recurring Payments VRP Payments with SCA exemption 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. View journey VRP Payments under Sweeping Access VRP Payments under sweeping access are a subset of VRP payments with SCA exemption that also has additional constraints. View journey VRP Payments with delegated SCA VRP Payments initiated by a PISP that 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. This provides explicit consent for each payment instruction, dynamically linking the amount and a payee, allowing for flexibility on the VRP Consent Parameters. View journey
VRP Payments with SCA exemption 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. View journey
VRP Payments under Sweeping Access VRP Payments under sweeping access are a subset of VRP payments with SCA exemption that also has additional constraints. View journey
VRP Payments with delegated SCA VRP Payments initiated by a PISP that 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. This provides explicit consent for each payment instruction, dynamically linking the amount and a payee, allowing for flexibility on the VRP Consent Parameters. View journey