| Table of Contents | ||||
|---|---|---|---|---|
|
1. Introduction Introduction
Open Banking API specifications support Payment Initiation Services (PIS) that enable a PISP to initiate a payment order, with the PSU's explicit consent, from their online payment account held at their ASPSP. The PISP is then further able to retrieve the status of a payment order. This section describes how each of the Participants (PISPs and ASPSPs) in the delivery of these services can optimise the customer experience for these services. Furthermore, it provides clarifications to participants on the usage of the APIs, and best practice guidelines for implementation of the customer journeys. We have illustrated three variations for the single domestic payment use case. These variations are applicable to the other payment use cases as well.
Please note that ASPSPs do not need to support the initiation of certain payment methods described in this section by a PISP, where the ASPSP does not support such transactions through their own channels (such as international transactions and bulk payment files).
End to End User flow:
...
2. CX Guidelines
2.1 Single Domestic Payments – a/c selection @PISP
...
Where fees, charges or Forex apply
Where interest rates apply
To facilitate confirmation of payee (for Bahrain implementations, where ASPSPs applied COP validation and found inconsistency between payee account name and payee account details)
To display a PSU warning that the relevant payment account will become overdrawn / exceed an overdraft limit as a result of the intended payment
If the relevant payment submission cut-off time has elapsed and the ASPSP wishes to offer an execution date/time
Where the PSU has been identified by the ASPSPs as a vulnerable customer (who therefore receives tailored journeys and messages in ASPSP’s own online platforms)
To show value-add information based on functionality implemented by ASPSPs in competitive space which provides positive customer outcome (e.g. cash flow prediction engine)
For high value transactions using a different payment scheme
Where the payments may be duplicated by the customer in a short period (e.g. ASPSP may display a warning that payment appears to be duplicated)
3. API specification: Brief description
...