| Table of Contents | ||
|---|---|---|
|
1. Version Control
Version | Date | Description of Changes |
Bahrain OBF v1.0.0 | 25th Aug 2020 | Initial Release |
2. Overview
As part of the Open Banking module, a key element of the BOBF Bahrain OBF is to design use cases with API specifications and customer experience guidelines and technical API specifications to provide direction and baseline implementation standards for all participants. Use cases has have 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 and evaluating business opportunities relevant for Bahrain market.
Each use case broadly includes the following:
Customer journeys with essential requirements and mandatory experience standards encompassing customer journey, mandatory, conditional and optional CX requirements
API technical specifications encompassing open data/read-write API specifications, UML diagrams, data models, endpoints and usage examples
...
3. Theme Selection
Four Three themes have been identified that form the backbone of categorizing and developing the Use use cases for Bahrain’s open banking framework (BOBF)Bahrain OBF.
...
...
4. List of Use Cases
In consultation with the Open Banking Committee and based on the inputs received from the industry, an initial participants, a list of use cases have been finalised finalized to be part of Bahrain’s Open Banking Framework
...
S. No.
...
Theme
...
Bahrain OBF v1.0.0:
# | Category | Use cases | Description | |
1PISP | Payment Initiation Services | Single Domestic Payment
| Single Domestic Payment allows the user/customer to , post his/her consent to the PISPs PISP 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 (Banks). Single domestic payment use cases has been submitted for Industry feedback as working document 1 ASPSP. | |
2PISP | Payment Initiation Services | Single Future Dated Domestic Payment
| Single Future Dated Domestic Payment allows the user/customer to , post his/her consent to PISPs the PISP 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 (Banks)ASPSP. | |
3PISP | Payment Initiation Services | Single International Payment | Single International Payment allows the user/customer to , post his/her consent to PISPs the PISP to make an international payment for a specific amount to a specific payee, wherein the PISP provides this instruction to the customer’s ASPSPs (Banks)ASPSP. | |
4PISP | Payment Initiation Services | 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 (Banks)ASPSP. | |
5 | AISP | Account Information Services | Sharing Transaction History/ Account Information Sharing | AccountInformationSharing allows the user/customer, post his/her consent to the AISPsAISPto instruct his/her ASPSPs (Banks)ASPSP to share the userusers'/customers’ data. The AISPs AISP can access the user/customers customer data to provide recommendations/ innovative financial products and services as per his/ her needs. |
6AISP | Account Information Services | Sharing Product Details | Sharing Product Details allows third party developers (such as AISPs) to request for the ASPSPs (Banks) products and services details. The ASPSPs (Banks) accordingly share the requested information through standard APIs. | |
7Essential | Essentials Services | Consent Management
|
| |
8Essential | Essentials Services | Event Notifications Notification
|
|
4. Key Elements
...
5. Key Elements
Detailed Customer Journey
A customer journey is a visual representation of every experience the customers will go through for a use case. Bahrain OBF covers all the necessary and important elements of the Open Banking customer journey to be followed by the Open Banking participants
Variations of the Use Cases
Multiple variations are covered within a use case based on customer journeys, user interfaces and technical API specifications
Additional Supplementary Information
Supplementary Information should be displayed to the user/customer, having regard to the principle that parity should be maintained between Open Banking journeys and the ASPSPs direct online channel journeys. Additional Information may include fees, charges, warning signs, transaction summary, vulnerable transaction, etc. The ASPSP will decide on this field/information based on the applicability
Sequence Flow
A sequence flow is the connector between two elements of a process. After an element is visited during process execution, all outgoing sequence flows should be followed
Security and Access Control
Access control is a security technique that regulates who or what can view or use resources in an open banking ecosystem. Access control systems perform identification, authentication and authorization of the AISP/PISP and the user/customer by evaluating required login credentials
Reusable Components
APIs are built on principle of reusability where an API can be functionally reused for different applications and provide the filtering according to the requirements of the party involved. This will lead to reduction in development cost and time to market
Endpoints
When an API interacts with another system, the touchpoints of this communication are considered endpoints. Each endpoint is the location from which APIs can access the resources they need to carry out their function. API performance relies on its ability to communicate effectively with API Endpoints
Data Model, Object Model and Data Dictionary
Data Model is a logical structure of database which describes its design to reflect entities, attributes, relationship among data, constraints, etc.
An object model is a logical interface, software or system that is modeled through the use of object-oriented techniques. It enables the creation of an architectural software or system model prior to development or programming
A data dictionary is a list of key terms and metrics with definitions, a business glossary. Data Model and Data Dictionary facilitates better understanding of APIs and related endpoints
Usage Examples
Each use case has been provided with multiple JSON examples to make the API specification easily understandable for all the stakeholders
CENTRAL BANK OF BAHRAIN © 2020