_{S. No.}

_{Requirements and Considerations}

 _Participant

_{Implementation Requirements}

₁

_{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}

• _{Destination Country}

• _{Instruction Priority (Normal or Urgent)}

• _{Payee Account Name}

• _{Payee Account Identification details (E.g. IBAN)}

• _{Payment Reference}

_{CX consideration:}

_{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}

• _{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}

 _PISP

_Required

₂

_{PSU payment Account Selection}

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

• _{Enter their Payer's payment Account Identification details}

• _{Select their Account Identification details (this assumes they have been saved previously)}

• _{Select their ASPSP in order to select their PSU payment Account from there later on in the journey}

_PISP

_Required

 ₃

_{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}

• _{Destination Country}

• _{Instruction Priority (Normal or Urgent)}

• _{Payee Account Name}

• _{Payment Reference, ifit 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)}

• _{Ifthis 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}

• _{Ifthis has been pre-populated by PISPs (e.g. in a ecommerce payment scenario) PISPs could choose whether to display this information or not}

_{CX consideration:}

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

_{Example wording: "You will be securely transferred to YOUR ASPSP to authenticate and make the payment"}

_PISP

 _Required

₄

_{CX consideration:}

• _{Generic PISP to ASPSP redirection screen and message.}

_{SCA Authentication (including dynamic linking) must be the only action required at the ASPSPs (unless supplementary information required, refer to section 1.1.3).}

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

_ASPSP

_Required

₅

_{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}

• _{Payee Account Name}

• _{Payment Reference}

• _{Payee Account Identification details (e.g. IBAN)}

• _Country

• _{Payment Currency}

• _{Payment Amount}

• _{FX currency pair and rate}

• _{Charges model (BEN/SHA/OUR)[D1]} 

• _{Payment priority (Normal or Urgent)}

_{CX consideration:}

• _{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)}

• _{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 BOBF regulatory requirements}

• _{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}

• _{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 above. The PSU can either proceed with the payment or cancel it, on the same screen using options with "equal prominence"}

• _{Generic ASPSP to PISP redirection screen and message. Please refer to Section 2.2.5}

 _ASPSP

_Required

₆

_{PISP Confirmation}

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

• _{The unique identifier assigned to the payment instruction by ASPSPs}

• _{The payment status (and status update date & time) - Confirmation of successful payment initiation}

 _{If received by ASPSPs, PISPs must display any of the following information regarding initiation and execution of the payment:}

• _{The expected payment execution date & time}

• _{The expected settlement date & time (i.e. the value date of the payment)}

• _{The ASPSP charges (where applicable)}

_{CX consideration:}

• _{If PSUs provide their payment account identification details (as per item #2 options), PISPs could save the account details for future transactions, where this is part of the payment initiation service explicitly requested by the PSU}

• _{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}

_ASPSP

_Required

₇

_{Further Payment Status Update}

_{PISPs must follow up with ASPSPs in order to check and update the PSUs with the most updated information that can be received by ASPSPs in relation to the execution of the payment. For more details on Payment Status, please also refer to section Payment Status}

_PISP

_Required