1. Summary

The following diagram shows the different environments available in the Open Finance Platform (OFP) and summarises their role and relationship to each other.

1. Trust Framework Sandbox

   1. Can be accessed by TPPs and LFIs (once registered and all KYC checks passed).

   2. TPPs (and LFIs acting as TPPs) get credentials (digital certs and test accounts) to access to API Hub Sandbox only.

   3. LFIs get credentials (digital certs) and can publish and manage access to their own API Hub Pre-Prod environments to do their own UAT.

2. API Hub Sandbox

   1. This is a single sandbox which can be accessed via all TPPs (and LFIs acting as TPPs) and which contains synthetic data only and does not connect to any LFI systems (pre-prod or prod).

   2. Its purpose is to provide a fully standardised end-to-end testing facility for all TPPs and LFIs, without exposing access to any actual user data or accounts.

3. API Hub Pre-Prod

   1. Each LFI will get their own Pre-Prod environment in the API Hub, which should be connected to their own Pre-Prod systems.

   2. Its purpose is to enable each LFI to conduct end-to-end testing (including) UAT prior to connecting/accessing their production APIs (e.g. when implementing any new APIs, or when updating to a new version).

4. Trust Framework Production

   1. Can be accessed by TPPs and LFIs (once authorized by CBUAE).

   2. TPPs (and LFIs acting as TPPs) get credentials (digital certs) to access to API Hub Production APIs for each LFI.

   3. LFIs get credentials (digital certs) and can publish and manage access to their own API Hub Prod environments.

5. API Hub Production

   1. Each LFI will get their own Prod environment in the API Hub, which should be connected to their own Prod systems.

   2. Its purpose is to enable TPPs to access actual end customer data and accounts.

2. Sandbox and Pre-Production

The following section shows the onboarding workflow for the OFP Sandbox and Pre-Production Environments.

The latest version of the Trust Framework and API Hub documentations can be found here - Open Finance Platform

2.1 KYC/KYB Prerequisites

The onboarding process in Nebras will work in tandem with the licensing processes and controls inside the CBUAE

2.1.1 Requirements for LFIs

• All LFIs have completed the KYC/KYB process through CBUAE licensing, so no further such checks are needed in Nebras

• C-suite executives of LFIs should sign off on the primary business contacts to be responsible for Open Finance related operations directly with Nebras, as part of their onboarding process

2.1.2 Requirements for TPPs

• CBUAE will conduct KYB and KYC for TPPs as part of the licensing process, including:

  • KYB of the entity

  • KYC of the management and owners

• For testing in the sandbox environment the CBUAE does not have to have finished their KYC / KYB processes

• The nominated primary business contacts will be defined in the license application, which is a mandate from the organisation’s executives in respect of Open Finance

2.2 Onboarding to the Trust Framework (LFIs and TPPs)

For onboarding reference Session 4 (for LFIs) and Session 5 (for TPPs), also User Journey Onboarding Diagrams for the Sandbox.

2.3 Onboarding to the API Hub (TPPs)

For onboarding reference the following page - TPP Onboarding

2.4 Onboarding to the API Hub (LFIs)

For onboarding reference the following page - LFI Integration

3. Production

The following diagrams show the onboarding workflow for the OFP Production Environments.

Production onboarding is a refined version of Sandbox and Pre-production onboarding, please refer to sections 2.2, 2.3, 2.4 above for documentation if required.

3.1 Onboarding to Trust Framework (TPPs and LFIs)

3.2. Onboarding to API Hub (TPPs)

3.3 Onboarding to API Hub (LFIs)

4. Lifecycle Management

The following diagrams show the lifecycle management workflows for the OFP Production Environments

4.1 Lifecyle Management - Trust Framework (TPPs and LFIs)

4.2 Lifecycle Management - General and API Hub (TPPs and LFIs)