User Journey

Business PSUs can initiate, through PISPs, bulk/batch payments allowing them to make multiple payments from their payment accounts.

The authentication approach used in this journey replicates journey Domestic Payments – Supplementary info, where there is supplementary information to be displayed. If the payment order is incomplete, then the principles of journey Single Domestic Payments – a/c selection @ ASPSP apply. This is due to the fact that there are certain cases where one of the parameters required for the bulk/batch payments may not have been specified or not included in the submitted file, or specific charges may apply.

 

Wireframes

CEG Checklist Requirements 1

PISPs should either allow PSUs to specify any of the below information or pre-populate this information on their behalf for the bulk & batch payments:
Total amount of all payments in the bulk/batch and currency.
Number of payments included in the bulk/batch.
Reference for the file (as per best practice).
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: If PISPs allow PSUs to import/upload a batch/bulk file of payments, then the file may contain one PSU payment Account (for bulk) or multiple PSU payment Accounts (for batch). In this case, PISPs should not allow the customer to define a PSU payment Account for the bulk or batch. PISPs could read the file and pre-populate the PSU payment Account in the case of bulk payments. Moreover, PISPs could use the PSU payment Account sort code(s) to identify and pre-populate the PSU's ASPSP that the bulk/batch needs to be submitted for processing.
Otherwise, if no external file upload or PSU payment Account(s) in the file, PISPs should allow PSUs to either:
Enter the PSU payment Account details.
Select their account details (assumes they have been saved previously).
Select their ASPSP in order to select their PSU payment Account from there.

CEG Checklist Requirements 3

Minimum Set of Parameters: If PISPs allows PSUs to import/upload a batch/bulk file of payments, then the file may contain the payment scheme(s) and the requested execution date(s) for the bulk/batch of payments. In this case, PISPs should not allow the customer to define the payment scheme and the requested execution date. PISPs could read the file and pre-populate the payment scheme and the requested execution date in the case of bulk payments and also for the batch payments if the same throughout the file.
Otherwise, if no external file upload or payment scheme and the requested execution date in the file, PISPs should allow PSUs to specify the below information:
Instruction instrument (payment scheme).
Requested Execution date.
Note: For batch payments this will only hold if these parameters will need to apply to all the transactions within the batch.

CEG Checklist Requirements 4

PSU Consent to PISP: PISPs must request for the PSU's consent to the payment clearly displaying any of the following information if specified by PSUs or pre-populated by PISPs:
Total amount of all payments in the bulk/batch and currency (subject to item #2 options).
Number of payments included in the bulk/batch (subject to item #2 options).
Reference for the file (as per best practice) (subject to item #2 options).
Instruction instrument (payment scheme) (subject to item #1 options).
Requested Execution date (subject to item #1 options).
PSU payment Account or selected ASPSP (subject to item #3 options).
Note 1: if PSU payment Account is selected in previous screen, PISPs should mask the account details.
Note 2: if PSU payment Account details are provided, PISPs could use the account sort-code to derive and display the ASPSP.

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

Supplementary/ Missing Payment Information:
Although the payee details and total amount are known to the ASPSP before the PSU is authenticated,
ASPSPs must introduce a step after authentication to allow PSUs to provide additional information associated with the bulk/batch payment in order to complete the payment instructions, if the payment order is incomplete. This information may include:
PSU payment Account Identification details (for bulk payments only)
Instruction instrument (payment scheme) (for bulk payments and for batch only if it applies to all payments in the batch)
Requested Execution date (for bulk payments and for batch only if it applies to all payments in the batch)
ASPSPs should be able to introduce a step after authentication to display additional /supplementary information in relation to the bulk batch payment instructions such as expected execution date, specific terms related to this payment type, charges etc.

CX Considerations 9

ASPSPs should also display to PSUs all the payment instruction information received from PISPs.

CX Considerations 10

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 11

ASPSPs must allow PSUs to review the information described in items #8, #9 & #10. The PSU can either proceed with the payment or cancel it, on the same screen using options with "equal prominence".

CX Considerations 12

As per Single Domestic Payments – a/c selection @ PISP, item #9.

CEG Checklist Requirements 13

PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10.

CEG Checklist Requirements 14

Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12.

Requirements and Considerations

CEG Checklist Requirements & CX Considerations

PISPs should either allow PSUs to specify any of the below information or pre-populate this information on their behalf for the bulk & batch payments:

  • Total amount of all payments in the bulk/batch and currency.
  • Number of payments included in the bulk/batch.
  • Reference for the file (as per best practice).
  • Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP.

21

PSU payment Account Selection: If PISPs allow PSUs to import/upload a batch/bulk file of payments, then the file may contain one PSU payment Account (for bulk) or multiple PSU payment Accounts (for batch). In this case, PISPs should not allow the customer to define a PSU payment Account for the bulk or batch. PISPs could read the file and pre-populate the PSU payment Account in the case of bulk payments. Moreover, PISPs could use the PSU payment Account sort code(s) to identify and pre-populate the PSU’s ASPSP that the bulk/batch needs to be submitted for processing. 

Otherwise, if no external file upload or PSU payment Account(s) in the file, PISPs should allow PSUs to either:

  • Enter the PSU payment Account details.
  • Select their account details (assumes they have been saved previously).

Select their ASPSP in order to select their PSU payment Account from there.

23

24

Minimum Set of Parameters: If PISPs allows PSUs to import/upload a batch/bulk file of payments, then the file may contain the payment scheme(s) and the requested execution date(s) for the bulk/batch of payments. In this case, PISPs should not allow the customer to define the payment scheme and the requested execution date. PISPs could read the file and pre-populate the payment scheme and the requested execution date in the case of bulk payments and also for the batch payments if the same throughout the file. 

Otherwise, if no external file upload or payment scheme and the requested execution date in the file, PISPs should allow PSUs to specify the below information: 

  • Instruction instrument (payment scheme).
  • Requested Execution date.

Note: For batch payments this will only hold if these parameters will need to apply to all the transactions within the batch.

22

PSU Consent to PISP: PISPs must request for the PSU’s consent to the payment clearly displaying any of the following information if specified by PSUs or pre-populated by PISPs:

  • Total amount of all payments in the bulk/batch and currency (subject to item #2 options).
  • Number of payments included in the bulk/batch (subject to item #2 options).
  • Reference for the file (as per best practice) (subject to item #2 options).
  • Instruction instrument (payment scheme) (subject to item #1 options).
  • Requested Execution date (subject to item #1 options).
  • PSU payment Account or selected ASPSP (subject to item #3 options).
  • Note 1: if PSU payment Account is selected in previous screen, PISPs shouldmask the account details.

Note 2: if PSU payment Account details are provided, PISPs could use the account sort-code to derive and display the ASPSP.

8

Supplementary/ Missing Payment Information:

Although the payee details and total amount are known to the ASPSP before the PSU is authenticated, 

  • ASPSPs mustintroduce a step after authentication to allow PSUs to provide additional information associated with the bulk/batch payment in order to complete the payment instructions, if the payment order is incomplete. This information may include:
  • PSU payment Account Identification details (for bulk payments only) 
  • Instruction instrument (payment scheme) (for bulk payments and for batch only if it applies to all payments in the batch)
  • Requested Execution date (for bulk payments and for batch only if it applies to all payments in the batch)
  • ASPSPs shouldbe able to introduce a step after authentication to display additional /supplementary information in relation to the bulk \\batch payment instructions such as expected execution date, specific terms related to this payment type, charges etc.

20

ASPSPs should also display to PSUs all the payment instruction information received from PISPs.

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

ASPSPs must allow PSUs to review the information described in items #8, #9 & #10. The PSU can either proceed with the payment or cancel it, on the same screen using options with “equal prominence”.

Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12.

27

Additional Information

OBIE Bulk/Batch payments proposition

For the purposes of this paper, the following definitions of bulk and batch payments are used:

  • Bulk = A group of payments (e.g. in a file) to be paid to multiple creditor accounts from the same debtor account, on the same date, with the same currency and through the same payment scheme.
  • Batch = A group of payments (e.g. in a file) to be paid to multiple creditor accounts from multiple debtor accounts. These may involved different payment execution dates, currencies and payment schemes.

Please also note the following working assumptions:

  • For bulk payments, the PSU maybe able to select the PSU payment Account and other parameters of the bulk payment instruction at the ASPSP, if they are not included in file submitted by the PISP.
  • For batch payments, the PSU may not be able to select the PSU payment Account and other parameters of the bulk payment instruction at the ASPSP, if they are not included in the file submitted by the PISP.

What the research says:

“Research indicates that SMEs value having a summary information step page as part of the bulk / batch payment process to act as a check, including a ‘cancel’ option to minimise the chance of errors.”

Click for Customer Research