...
Version | 1.2 |
|---|---|
Publication Date | 09 |
Classification | Public |
1. Introduction
...
conduct appropriate testing and obtain the relevant certifications (as set out below) prior to ‘go-live’ for each version of the Standards they implement;
when testing and obtaining certifications in a Pre-Production Environment, warrant that their Pre-Production Environment mirrors their Production Environment, having the same architecture, network elements, software versions and customer experience elements.;
conduct this testing and obtain a separate complete set of certifications for each brand/application, e.g.
for LFIs, in cases where the LFI has a number of brands and/or customer segments, each with separate web or mobile apps; or
for TPPs, in cases where the TPP has more than one end customer facing web or mobile application;
conduct penetration testing (as required below) using a reputable independent third party company.
LFIs and TPPs may conduct stress testing (as required below) using their own internal resources and tools.
LFIs must:
conduct Functional Testing (using Ozone Connect Test Suite and Postman Collection) in their Pre-Production Environment prior to promotion to Production Environment and again prior to go-live;
submit and obtain CX Certification for their web and/or mobile applications prior to prior to promotion to Production Environment;
perform penetration and stress testing (to meet all NFRs in the Standards) before go-live; and
engage with TPPs to conduct Live Proving immediately after promotion to Production Environment before go-live.
...
Prior to updating their Production Environment in the API Hub, LFIs must run two sets of tests in their Pre-Production and Production Environments:
Using the API Hub Testing Tool to test their integration with the API Hub.
Using the API Hub Sandbox Postman Collection to test that a TPP can successfully call all API endpoints defined in the Standards. LFIs can either do this using their own TPP credential from the Trust Framework, or they can partner with a TPP to run these end to end tests. Tests must be executed for each API endpoint relevant to LFI deployment as set out in this template:
View file name LFI Customer-Facing API Functional Checklist V1.02.xlsx
Once all tests have been passed, the LFI must submit evidence (a test report in any format agreed between the LFI and Nebras, along with the above functional checklist) to Nebras, so that Nebras can validate.
Nebras will then confirm acceptance for the LFI to exit Pre-Production.
LFIs must rerun both sets of tests in their Production Environment and resubmit test reports to Nebras prior to go-live.
LFIs must rerun both sets of tests and resubmit results whenever they implement any new version of the Standards or whenever they make any substantive changes to their integration with the API Hub. These retests must be conducted in both their Pre-Production Environment and again in their Production Environment before go-live each time.
...
LFIs must submit a certification request using this template:
.View file name CBUAE LFI CX Certification v1.02.xlsx LFIs must use a separate copy of this template for each brand/segment (e.g. retail v sme v corporate) and for each interface (web v mobile).
For each template, LFIs must complete the required fields on the first tab and then paste in the relevant screen grabs on each subsequent tab.
All screens must be in English language.
These screens can be from the LFI’s Pre-Production Environment or their Production Environment. However, if LFIs submit screens based on their Pre-Production Environment, they must confirm and warrant that these screens are an exact match for their Production Environment.
Nebras will validate that these screens meet the stated requirements in the Standards and require the LFI to update these screens and resubmit screen grabs if required.
As soon as all screens meet the requirements, Nebras will issue a certification to the LFI.
LFI CX Certification is an exit criteria from Pre-Production.
...
TPPs must access the API Hub Sandbox and execute API calls for each API endpoint relevant to their use case as set out in this template:
.View file name CBUAE TPP Functional Certification V1.02.xlsx TPPs must then submit a certification request using this template.
If the TPP has more than one application, the TPP must use a separate copy of this template for each separate application.
For each template, the TPP must complete the required fields on each tab, i.e.
Bank Data
Bank Service Initiation
Insurance Data
However, TPPs only need to complete the tabs relevant to their use case (e.g. if the TPP does not offer insurance services then they do not need to make calls to the Insurance Data endpoints, nor complete this tab).
Nebras will validate that the TPP has made successful API calls for each relevant use case and require the TPP to retry if required.
As soon as all APIs have been called successfully, Nebras will issue a certification to the TPP.
This is an exit criteria from the API Hub Sandbox.
...
TPPs must submit a certification request using this template:
.View file name CBUAE TPP CX Certification v1.02.xlsx If the TPP has both a web and mobile application, then they must submit screens for each, otherwise they only need to submit screens for the supported application
For each template, TPPs must complete the required fields on the first tab and then paste in the relevant screen grabs on each subsequent tab.
All screens must be in English language.
Nebras will validate that these screens meet the stated requirements in the Standards and require the TPP to update these screens and resubmit screen grabs if required.
As soon as all screens meet the requirements, Nebras will issue a certification to the TPP.
This is an exit criteria from the API Hub Sandbox.
...