Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

1.  Overview

As part of the Open Banking module, a key element of the BOBF is to design use cases with API specifications and customer experience guidelines to provide direction and baseline implementation for all participants. Use cases has been developed by leveraging key insights from global best practices like the Open Banking Implementation Entity (OBIE) in the U.K. and the Australian Competition and Consumer Commission (ACCC) in Australia and identifying business opportunities customized for the Bahrain market. Further, it builds on the regulations of the open banking module, previously released by the Central Bank of Bahrain and also incorporates key inputs received from stakeholders so far.

The use case as part of this document broadly includes the following:

  • Customer journeys with essential requirements and mandatory requirements

  • API technical specifications encompassing open data/read-write API specifications, UML diagrams, data models, endpoints and usage examples

2.  Theme Selection

Four themes have been identified that form the backbone of categorizing and developing the Use cases for Bahrain’s open banking framework (BOBF).

3.  List of Use Cases

In consultation with the Open Banking Committee and based on the inputs received from the industry, an initial list of use cases have been finalised to be part of Bahrain’s Open Banking Framework

S. No.

Theme

Use Cases

Description

1

PISP

Single Domestic Payment

  1. Account selection @ PISP

  2. Account selection @ ASPSP

  3. Account selection @ PISP with Supplementary information

Single Domestic Payment allows the user/customer to post his/her consent to the PISPs to make a one-time payment for a specific amount to a specific payee immediately, wherein the PISP provides this instruction to the customer’s ASPSPs .

Single domestic payment use cases has been submitted for Industry feedback as working document 1

 

2

PISP

Single Future Dated Domestic Payment

  1. Single Future Dated Domestic Payment

  2. Cancellation of single future dated domestic payment @ PISP

Single Future Dated Domestic Payment allows the user/customer to post his/her consent to PISPs to make a one-time payment for a specific amount to a specific payee on a specific future date, wherein the PISP provides this instruction to the customer’s ASPSPs .

3

PISP

Single International Payment

Single International Payment allows the user/customer to post his/her consent to PISPs to make an international payment for a specific amount to a specific payee, wherein the PISP provides this instruction to the customer’s ASPSPs .

4

PISP

Bulk/Batch Payment

Bulk/Batch Payment allows the user/customer to post his/her consent to the PISPs to initiate multiple payments to one or more beneficiaries in a single transaction, wherein the PISP provides this instruction to the customer’s ASPSPs .

5

AISP

Account Information Sharing

Account Information Sharing allows the user/customer post his/her consent to the AISPs to instruct his/her ASPSPs to share the user/customers’ data. The AISPs can access the user/customers data to provide recommendations/ innovative financial products and services as per his/ her needs

6

AISP

Sharing Product Details

Sharing Product Details allows third party developers (such as AISPs) to request for ASPSPs products and services details. The ASPSPs share the requested information through standard APIs.

7

Essential

Consent Management

  1. Consent dashboard and revocation

  2. Access dashboard and revocation

  • Consent Dashboard allows the user/customer to view, refresh and revoke consent that they have given to the AISP to access User/ Customers’ data

  • Access Dashboard allows the user/customer to view, refresh and revoke access that they have given to that AISP through ASPSPs portal

8

Essential

Event Notifications

  1. Event Subscription

  2. Real Time Notification

  3. Aggregated Polling

  • Event Subscription allows an AISP and (or) PISP to register with an ASPSP to subscribe to real time and (or) aggregated polling event notifications, specify a list of event types to be notified on and optionally read, update or delete a registered event subscription

  • The Real Time Notification allows ASPSPs to notify an AISP and (or) PISP in real time, that an event has occurred

  • Aggregated Polling allows AISPs and(or) PISPs to request ASPSPs for an aggregated set of notifications related to multiple user/customer accounts during a specific period, enabling them to update their records and contact the user/customer

4.  Key Elements

  • No labels