VRP Payments under Sweeping Access

 PISPs must either allow PSUs to specify consent parameters or pre-populate them for the PSUs enabling the PSU to amend any of them as required. 

In order for the PSU to provide their explicit consent to setup a Sweeping Payment, the PISP must present the  required consent parameters listed below:

Required set of Sweeping Consent Parameters^[1]Setting the appropriate consent parameters https://standards.openbanking.org.uk/tpp-guidelines/vrp-guidelines/latest/#setting_cp

• Payee Account Name.
• Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN).
• Maximum amount per payment and Currency (GBP for UK implementations).
• Maximum amount per time window* and Currency (GBP for UK implementations).
• Expiry Date (Ongoing or a Specific Date).

*time window – Day/Week/Fortnight/Month/Half Year/ Year

Note: Max amount per time window can be aligned to start from the date of consent creation or lined up with a calendar period.

If the max amount per time window is aligned to the calendar period, the calculation of the limit is pro-rated in the first period to the remaining number of days. For example, refer to the link in the API specifications section below.

PSU payment Account Selection

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

Note 1: 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 Open Banking Standard and offering their services in the UK. 

PSU Consent to PISP 

PISPs must display the following information in the consent screen:

Consent Parameters (as provided in item 1.)

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.

Terms 

PISPs must enable the PSUs to view their Terms on the consent screen.

PISPs should provide messaging to inform PSUs that they will be taken to their ASPSPs to complete the payment.

Example wording: ‘We will securely transfer to YOUR ASPSP to authenticate“.

Generic PISP to ASPSP redirection screen and message. Please refer to sections Browser based redirection – PIS, App based redirection – PIS and Effective use of redirection screens.

Additional Parameters

ASPSPs must allow PSUs to select payment account to complete the Sweeping setup only if the PSU has not provided it to the PISP in item 1.

It is up to ASPSP to consider relevant obligations relating to the FCA’s High Cost Credit Review: Overdrafts consultation paper and policy statement (CP18/42) & (PS19/16)”.

ASPSPs must display all the consent parameter(s) provided by the PISP.

These details must be displayed as part of the authentication journey on at least one of the following screens without introducing additional confirmation screens (unless supplementary information is required, refer to section Single Domestic Payments – Supplementary info.

1. ASPSPs’ Authentication screen (recommended).
2. ASPSP to PISP redirection screen

ASPSPs must support all the periodic limits and be capable to handle multiple periodic limits in a single consent.

The ASPSPs may restrict to one-period alignment (i.e. consent or calendar) for a single periodic limit in a single consent.

Note – e.g.: Max cumulative amount per calendar year and Max cumulative amount per consent year may not be an acceptable combination in one VRP consent, however, Max cumulative amount per calendar year and Max cumulative amount per consent month is acceptable.

The ASPSP should not put restrictions when the consent is set up but can apply restrictions if the amount(s) in the individual payment orders submitted exceed the limits in the direct, online channels.

ASPSPs must inform the PSU that the payee will be added to their Trusted Beneficiary list and must also add the payee to the PSU’s Trusted Beneficiary List.

OR

ASPSPs may choose to apply ‘Transfer to Self’ SCA exemption over ‘Trusted Beneficiary’ if it is more appropriate.

For recognition based biometrics (e.g. Face ID) which can be more immediate the biometric authentication should be invoked after a delay or through a call to action to allow the PSU the ability to view the details. 

SCA Authentication must be the only action required at the ASPSPs (unless supplementary information required, refer to section Single Domestic Payments – Supplementary info.

The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel.

Generic ASPSP to PISP redirection screen and message. Please refer to section Effective use of redirection screens.

PISP Confirmation 

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

The PISP must be able to submit a CoF request prior to making Sweeping payment and must receive a response back from the ASPSP.  Please refer to section Confirmation of Funds for PISP – Y/N Response – Requirements #5 to #9

ASPSP must reject the Sweeping Payment  and provide an appropriate response back to the PISP if :

• The Sweeping payment submitted by PISP is outside the Sweeping Consent parameters.
• The Sweeping consent setup access is revoked by the PSU at the ASPSP.

ASPSP must apply for the ‘Trusted Beneficiary’ exemption when the PISP initiates a Sweeping payment within the Sweeping consent parameters.

Note: There may be instances where an ASPSP may require SCA, even if the payment is made is to a trusted beneficiary, for example, suspicion of fraud. However, the ASPSP must only do so in exceptional circumstances with an objective approach and in line with the proportionality requirements of the PSRs.

Note: The ASPSP may apply a ‘Transfer to Self’ exemption if the PISP initiates a Sweeping payment to an account held at the same ASPSP.

ASPSPs must offer the same minimum and maximum payment limits for payment types, as they offer in their direct online channels.

PISPs must provide messaging to inform PSUs that Sweeping payment has been successfully initiated with their ASPSP.

PISPs must provide the PSU with all information related to the Sweeping payment after the payment has been successfully initiated.

The PISP should provide the PSU with a notification for a failed payment initiation.

Note: PISPs may notify the PSU before initiating each Sweeping payment.