Page Comparison

...

In summary:

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.

...

3.2. Onboarding to API Hub (TPPs)

3.3 Onboarding to API Hub (LFIs)

3.4 Lifecyle Management on Trust Framework (TPPs and LFIs)

...