User Journey PSUs can initiate, through PISPs, single international payments from their GBP or foreign…
Other pages in this section Account selection at PISP Account Selection at PISP – Supplementary Info Account Selection at ASPSP Scheduled Payments – Future Dated Standing Orders International Payments Bulk / Batch Payments Multi-authorisation Payments Confirmation of Funds for PISP – Yes / No Response Payment Refunds
This content is best viewed on a desktop browser. 1 CEG Checklist Requirements 1Minimum Set of Parameters: PISPs must either allow PSUs to specify the below minimum set of parameters or pre-populate them (e.g. in cases of supplier invoice payments or eCommerce journeys): Payment Amount and Currency. Destination Country. Instruction Priority (Normal or Urgent). Payee Account Name. Payee Account Identification details (e.g.. IBAN) 1. Payment Reference – This is optional filed but it is good practice to be populated for a payment. Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP. 2 CX Considerations 2PISPs could display an indicative FX rate for the payment currency pair if: PSUs selected a PSU payment Account or provided PSU payment Account details in item #4. PSUs provided the currency of the selected PSU payment Account. In that case, PISPs must clearly indicate to PSUs that the FX rate displayed is indicative and may be different to the FX rate to be provided by their ASPSPs. If the PISP has the ability to provide any actual FX rate quote to the PSU at this stage (e.g. having implemented a quoting mechanism with the ASPSP) then the PISP should be able to display the actual FX rate to be used for the transaction. 3 CEG Checklist Requirements 3If PISPs want to offer PSUs the ability to make an International Scheduled Payment (Future Dated),then PISPs must allow PSUs to select the requested execution date for the payment, or pre-populate this information as part of the payment order request. 4 CEG Checklist Requirements 4PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 5 CEG Checklist Requirements 5PSU Consent to PISP: PISPs must request for the PSUs’ consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen: Payment Amount and Currency. Destination Country. Instruction Priority (Normal or Urgent). Payee Account Name. Requested Payment Execution Date (same day processing or future date). Payment Reference and any supplementary info, if it has been entered by PSUs or pre-populated by PISPs in item #1. PSU payment Account Identification and/or the selected ASPSP (based on item #2 options). Note 1: If PSU payment Account identification is selected in item #2, PISPs should mask the PSU payment Account details on the consent screen. Otherwise, if the PSU payment Account identification has been input by PSUs in item #2, PISPs should not mask these details to allow PSUs to check and verify correctness Note 2: 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 For Payee Account Identification details (e.g. IBAN) 1. 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 a eCommerce payment scenario) PISPs could choose whether to display this information or not . 6 CX Considerations 6As per Single Domestic Payments – a/c selection @ PISP, item #4. 7 CX Considerations 7As per Single Domestic Payments – a/c selection @ PISP, item #5. 8 CEG Checklist Requirements 8As per Single Domestic Payments – a/c selection @ PISP, item #8. 9 CEG Checklist Requirements 9Supplementary Information / Additional Payment Order Details ASPSPs must be able to introduce a step as part of the authentication journey to display supplementary information associated with that payment, if required. Moreover, ASPSPs must allow the PSU to provide additional details related to the payment order during the authentication journey (authentication and supplementary information screens) such as for example, the account for the payment. The information to be provided in the supplementary information / additional payment order details screen may include: PSU payment Account Identification. Payee Account Name. Payment Reference. Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN). Country. Payment Currency. Payment Amount. FX currency pair and rate. Charges model (BEN/SHA/OUR) (for definitions please refer to appendix section PIS parameters and considerations). Payment priority (Normal or Urgent). Payment Execution Date (same day processing or future date). 10 CX Considerations 10ASPSPs must display to the PSU the FX currency conversion rate to be used for the payment order. This FX rate can be: Indicative – In this case ASPSPs must clearly inform PSUs that the FX rate is indicative and may be different than the actual rate that will be used for the payment order. Actual – ASPSPs must clearly inform PSUs for the validity period of this actual FX rate. If the payment order is not submitted within the validity window of the FX, then a new actual FX quote must be displayed. If PSUs confirm the payment but the payment order submitted by PISPs is not submitted within validity period, ASPSPs could choose to either reject the payment or process it at the agreed FX rate. ASPSPs could display the payment amount in the PSU payment Account currency (from applying the FX rate). 11 CX Considerations 11ASPSPs must ensure that charges related to international payments are provided to PSUs as agreed in the framework contract. Note1: Any provision of charges can only be those of the ASPSP as the Beneficiary’s bank charges are not known in many cases. Note 2: Where the final charges are not known to the ASPSP, the responsibility should remain with the ASPSP for notifying the customer of the charges as per the PSD2 regulatory requirements. 12 CX Considerations 12Other Options: ASPSPs should display the Final Debit Amount (including charges) in PSU payment Account currency. ASPSPs could display the expected Value Date for the international payment. 13 CX Considerations 13ASPSPs 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“. Note: In cases of future dated payments, PSUs are able to cancel the payments as described in section Scheduled International Payments (Future Dated). 14 CX Considerations 14ASPSPs must allow PSUs to review the information described in items #9, #10, #11 & #12. The PSU can either proceed with the payment or cancel it, on the same screen using options with %22equal prominence%22. 15 CX Considerations 15As per Single Domestic Payments – a/c selection @ PISP, item #9. 16 CEG Checklist Requirements 16PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10. In addition, PISPs must display to PSUs the actual FX rate used for the international payment transaction if this information has been provided by the ASPSP. 17 CX Considerations 17As per Single Domestic Payments – a/c selection @ PISP, item #11.. 18 CEG Checklist Requirements 18Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 Minimum Set of Parameters: PISPs must either allow PSUs to specify the below minimum set of parameters or pre-populate them (e.g. in cases of supplier invoice payments or eCommerce journeys): •Payment Amount and Currency. •DestinationCountry. •Instruction Priority (Normal or Urgent). •Payee Account Name. •Payee Account Identification details (e.g.. IBAN) 1. •Payment Reference – This is optional filed but it is good practice to be populated for a payment. •Any supplementary information required which the ASPSP has published as required and is specific to that ASPSP. 22 2 PISPs could display an indicative FX rate for the payment currency pair if: PSUs selected a PSU payment Account or provided PSU payment Account details in item #4. PSUs provided the currency of the selected PSU payment Account. In that case, PISPs must clearly indicate to PSUs that the FX rate displayed is indicative and may be different to the FX rate to be provided by their ASPSPs. If the PISP has the ability to provide any actual FX rate quote to the PSU at this stage (e.g. having implemented a quoting mechanism with the ASPSP) then the PISP should be able to display the actual FX rate to be used for the transaction. 3 If PISPs want to offer PSUs the ability to make an International Scheduled Payment (Future Dated),then PISPs must allow PSUs to select the requested execution date for the payment,or pre-populate this information as part of the payment order request. 21 4 PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 24 5 PSU Consent to PISP: PISPs must request for the PSUs’ consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen: Payment Amount and Currency. DestinationCountry. Instruction Priority (Normal or Urgent). Payee Account Name. RequestedPaymentExecution Date (same day processing or future date). Payment Reference and any supplementary info, if it has been entered by PSUs or pre-populated by PISPs in item #1. PSU payment Account Identification and/or the selected ASPSP (based on item #2 options). Note 1: If PSU payment Account identification is selected in item #2, PISPs should mask the PSU payment Account details on the consent screen. Otherwise, if the PSU payment Account identification has been input by PSUs in item #2, PISPs should not mask these details to allow PSUs to check and verify correctness Note 2: 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 For Payee Account Identification details (e.g. IBAN) 1. 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 a eCommerce payment scenario) PISPs could choose whether to display this information or not. 8 6 As per Single Domestic Payments – a/c selection @ PISP, item #4. 7 As per Single Domestic Payments – a/c selection @ PISP, item #5. 8 As per Single Domestic Payments – a/c selection @ PISP, item #8. 19 1 9 Supplementary Information/ Additional Payment Order Details ASPSPs must be able to introduce a step as part of the authentication journey to display supplementary information associated with that payment, if required. Moreover, ASPSPs must allow the PSU to provide additional details related to the payment order during the authentication journey (authentication and supplementary information screens) such as for example, the account for the payment. The information to be provided in the supplementary information / additional payment order details screen may include: PSU payment Account Identification. PayeeAccountName. PaymentReference. Payee Account Identificationdetails (e.g. account number and sort code or additionally roll number or full IBAN). Country. PaymentCurrency. PaymentAmount. FXcurrency pair and rate. Charges model (BEN/SHA/OUR) (for definitions please refer to appendix section PIS parameters and considerations. Payment priority (Normal or Urgent). Payment Execution Date (same day processing or future date). 20 23 10 ASPSPs must display to the PSU the FX currency conversion rate to be used for the payment order. This FX rate can be: Indicative – In this case ASPSPs must clearly inform PSUs that the FX rate is indicative and may be different than the actual rate that will be used for the payment order. Actual – ASPSPs must clearly inform PSUs for the validity period of this actual FX rate. If the payment order is not submitted within the validity window of the FX, then a new actual FX quote must be displayed. If PSUs confirm the payment but the payment order submitted by PISPs is not submitted within validity period, ASPSPs could choose to either reject the payment or process it at the agreed FX rate. ASPSPs could display the payment amount in the PSU payment Account currency (from applying the FX rate). 11 ASPSPs must ensure that charges related to international payments are provided to PSUs as agreed in the framework contract. Note1: Any provision of charges can only be those of the ASPSP as the Beneficiary’s bank charges are not known in many cases. Note 2: Where the final charges are not known to the ASPSP, the responsibility should remain with the ASPSP for notifying the customer of the charges as per the PSD2 regulatory requirements. 12 Other Options: ASPSPs should display the Final Debit Amount (including charges) in PSU payment Account currency. ASPSPs could display the expected Value Date for the international payment. 13 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“. Note: In cases of future dated payments, PSUs are able to cancel the payments as described in section Scheduled International Payments (Future Dated). 14 ASPSPs must allow PSUs to review the information described in items #9, #10, #11 & #12. The PSU can either proceed with the payment or cancel it, on the same screen using options with “equal prominence”. 15 As per Single Domestic Payments – a/c selection @ PISP, item #9. 16 PISP Confirmation: As per Single Domestic Payments – a/c selection @ PISP, item #10 In addition, PISPs must display to PSUs the actual FX rate used for the international payment transaction if this information has been provided by the ASPSP. 25 26 17 As per Single Domestic Payments – a/c selection @ PISP, item #11. 18 Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. 27
Standing Orders Previous Related articles Please select API specifications International Payment Consents International Payments International Scheduled Payment Consents International Scheduled Payments International Standing Order Consents International Standing Orders International Payment Usage Examples International Scheduled Payment Usage Examples Bulk / Batch Payments Next