_{S. No.}

_{Requirements and Considerations}

 _Participant

_{Implementation Requirements}

₁

_{Minimum Set of Parameters:}

_{PISPs must either allow}

_user/

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

_{may display an indicative FX rate for the payment currency pair if:}

• _User/

• _{Customer selected a user/customer payment Account or provided user/customer payment Account details}

• _User/

• _{Customer provided the currency of the selected user/customer payment Account}

_{In that case, PISPs must clearly indicate to}

_user/

_{customer that the FX rate displayed is indicative and may be different to the FX rate to be provided by their ASPSPs (Banks)}

_{If the PISP has the ability to provide any actual FX rate quote to the user/customer 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

₂

_{User/Customer payment Account Selection}

_{PISPs must provide users/customers 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 (Bank) in order to select their user/customer payment Account from there later on in the journey}

_PISP

_Required

 ₃

_{User/Customer Consent to PISP:}

_{PISPs must request for the users'user/customerscustomer' 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, if it has been entered by usersuser/customers customer or pre-populated by PISPs in item #1}

• _{User/Customer payment Account Identification and/or the selected ASPSP (Bank) (based on item #2 options)}

  • _{Note 1: if user/customer payment Account identification is selected in item #2, PISPs should mask the user/customer payment Account details on the consent screen. Otherwise, if the user/customer payment Account identification has been input by} users_user/customers _{customer in item #2, PISPs should not mask these details to allow} users_user/customers _{customer to check and verify correctness}

  • _{Note 2: if user/customer payment Account identification is provided by} users_user/customers _{customer in item #2, PISPs could may use this to identify and display the ASPSP (Bank) without having to ask} users_user/customers _customer

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

• _{If this has been provided by usersuser/customers customer in item #1, then PISPs must also display this in the consent screen to allow usersuser/customers customer to check and verify correctness}

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

_{CX consideration:}

• _{PISPs should provide messaging to inform users/customers that they will be taken to their ASPSPs (Banks) to complete the payment}

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

_PISP

 _Required

₄

_{CX consideration:}

_{SCA- Strong Customer Authentication}

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

_{The ASPSP (Bank) authentication must have no more than the number of steps that the user/customer would experience when directly accessing the ASPSP (Banks)channel.}

_{ASPSP (Bank)}

_Required

₅

_{Additional Supplementary Information / Additional Payment Order Details}

_{ASPSPs (Banks) 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 (Banks) must allow the user/customer 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:}

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

_{ASPSPs (Banks) must display to the user/customer the FX currency conversion rate to be used for the payment order. This FX rate can be:}

• _{Indicative - In this case ASPSPs (Banks) must clearly inform users/customers that the FX rate is indicative and may be different than the actual rate that will be used for the payment order}

• _{Actual - ASPSPs (Banks) must clearly inform users/customers 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 users/customers confirm the payment but the payment order submitted by PISPs is not submitted within validity period, ASPSPs (Banks) could choose to either reject the payment or process it at the agreed FX rate}

• _{ASPSPs (Banks) could display the payment amount in the user/customer payment Account currency (from applying the FX rate}

  )

_{CX consideration:}

• _{ASPSPs (Banks) must should ensure that charges related to international payments are provided to users/customers as agreed in the framework contract}

  • _{Note1: Any provision of charges can only be those of the ASPSP (Bank) as the Beneficiary's bank charges are not known in many cases}

  • _{Note 2: Where the final charges are not known to the ASPSP (Bank), the responsibility should remain with the ASPSP for notifying the customer of the charges as per the BOBF regulatory requirements}

• _{Other Options:}

  • _{ASPSPs (Banks) should display the Final Debit Amount (including charges) in user/customer payment Account currency}

  • _{ASPSPs (Banks) could may display the expected Value Date for the international payment}

• _{ASPSPs (Banks) should inform users/customers 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 (Banks) must allow users/customers to review the information described above. The user/customer can either proceed with the payment or cancel it, on the same screen using options with "equal prominence"}

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

 _{ASPSP (Bank)}

_Required

₆

_{PISP Confirmation}

_{If received from ASPSPs (Banks), PISPs must display the information received from the ASPSP (Bank). This information may include:}

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

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

 _{If received by ASPSPs (Banks), 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 (Bank) charges (where applicable)}

• _{Actual FX rate used for the international payment transaction}

_{CX consideration:}

• _{If users/customers 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 user/customerIn addition, PISPs must display to users/customers the actual FX rate used for the international payment transaction if this information has been provided by the ASPSP (Bank)}

_{ASPSP (Bank)}

_Required

₇

_{Further Payment Status Update}

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

_PISP

_Required