Testing & Certification · CX Evidence

User Experience Evidence 6 min read

CX Certification confirms that the screens your customers see in an Open Finance journey — authentication, authorization and your consent management interface — meet the user experience requirements in the Standards and are consistent with your existing digital channels. It is one of the two Gate 1 certifications that unlock production onboarding, and it is managed through the Nebras Service Desk.

01 How CX Certification Works

Submit screen designs in the template; Nebras assesses them

01

Download the template

Download the LFI CX certification template (v2.1). It contains a Summary sheet and one tab for each screen in the consent journey and consent management interface.

02

Complete one workbook per brand or segment

Paste your screen designs into each applicable tab, for both your web browser and mobile app channels, and self-assess each screen against the requirements.

03

Raise a CX Certification ticket

Attach the completed workbook to a CX Certification ticket on the Service Desk. Raise one ticket per brand or segment.

04

Nebras assesses your screens

Nebras assesses each screen against the requirements in the Standards and for consistency with your current customer experience. Each tab has a CBUAE / Nebras Assessment section for the result.

02 What Nebras Assesses

Every screen is assessed against the Standards and against your own experience

Conformance with the Standards

Each screen MUST meet the user experience requirements the Standards define for it: the authentication requirements, the authorization page principles (including AlTareq branding), the user journeys for each consent type, and the consent management interface requirements. The screen table below gives the reference for each tab.

Consistency with your current experience

Open Finance screens MUST look and read like the rest of your digital channels. Nebras checks that the following are consistent with your existing web and mobile experience:

  • Language — wording, tone and terminology.
  • Colour scheme — the same palette your customers already see.
  • Typography — the same typefaces, sizes and weights.
  • Other visual elements — for example iconography, buttons and layout conventions.

This applies the Parity of experience principle: the authorization experience MUST be consistent with the quality of the LFI's own digital channels.

Submit high-fidelity designs

Because language, colour and typography are assessed, your designs MUST show each screen as customers will see it, with final copy, colours, typefaces and branding. Nebras cannot assess low-fidelity wireframes.

Assessment outcomes

Nebras records one of the following outcomes against each screen:

OutcomeMeaning
PassThe screen meets the CX requirements.
FailA mandatory (MUST) requirement is not met.
WarningA non-mandatory (SHOULD) requirement is not met.
N/AThe screen does not apply to your institution.
03 Completing the Template

One workbook per brand or segment, covering every channel

Complete a separate workbook for each brand or segment you are certifying, for example one for your retail brand and one for your corporate brand. Each workbook covers both your web browser and mobile app channels.

Summary sheet

FieldWhat to enter
LFI Legal NameYour legal entity name.
LFI Brand / SegmentThe brand or segment this workbook covers.
InterfaceYour primary interface: Web browser or Mobile app. Each screen tab still includes designs for every channel you support.
Submitter nameYour first and last name.
Job TitleYour position.
Date SubmittedThe date you raise the ticket.

Then filter the Applicability column of the screen list to the screens that apply to your institution:

InstitutionApplicability values to include
BankAll, Bank, Bank/FX-house
FX houseAll, Bank/FX-house
InsuranceAll, Insurance

Each screen tab

  • Evidence — paste your screen designs for both your desktop browser and mobile app interfaces, in English. Cover every variant the tab's Instructions ask for.
  • Compliant — in the LFI Submission section, select Yes, No or N/A.
  • Notes — add any supplementary comments or justification. If you have adjusted a consent management interface requirement, document the adjustment here. The CMI requirements only permit adjustments that are documented in your CX certification submission.
  • N/A — mark a screen N/A when it covers a capability you do not offer.
  • Leave the CBUAE / Nebras Assessment section blank. Nebras completes it.
Phased delivery

If you are delivering a capability later, for example Service Initiation after Data Sharing, mark its screens N/A for now. Those screens go through CX certification when the capability is delivered, before it enters TPP Buddying. See The Path to Live.

04 Screens in the Template

21 screens, filtered by institution type

Every tab asks for the screen's variants across all your digital channels (mobile and desktop). The table lists the additional evidence each tab asks for and where its requirements are defined. Where no page is listed, use the Reference URL in the tab.

TabScreenApplies toAlso includeRequirements
1Centralized Authentication ScreenAll
  • Confirm whether your organisation will use CAAP.
2LFI to TPP Redirection ScreenAll—
3LFI Authentication Screen (1st factor / biometrics)All
  • Every first-factor method you apply, e.g. UAE Pass, Face ID, EFR, password.
4LFI Authentication Screen (2nd factor)All
  • Every second-factor method you apply, e.g. one-time password, push notification, token.
5LFI Authorization Screen (Single Immediate Payment)Bank
  • Exception handling and error message scenarios.
  • Confirmation of Payee outcomes: match, partial match and no match.
  • Customer-facing payment notifications (push, SMS, email, in-app).
6LFI Authorization Screen (Single Immediate Payment, with Shari’ah compliance message)Bank
  • Both the Shari’ah-compliant and non-compliant variants.
7LFI Authorization Screen (Single Future Dated Payment)Bank
  • Customer-facing payment notifications (push, SMS, email, in-app).
Reference URL in tab
8LFI Authorization Screen (Multi-Payment)Bank
  • Each of the seven VRP variations.
  • At least one journey with account selection at the TPP and one with account selection at the LFI.
  • For combined payments, payments to different creditors.
  • Customer-facing payment notifications (push, SMS, email, in-app).
9LFI Authorization Screen (International Payment)Bank
  • Customer-facing payment notifications (push, SMS, email, in-app).
Reference URL in tab
10LFI Authorization Screen (FX & Remittance Quote and Service Initiation)Bank / FX house
  • Customer-facing transaction notifications (push, SMS, email, in-app).
Reference URL in tab
11LFI Account Opening Screens (Dynamic Account Opening)Bank / FX house—Reference URL in tab
12LFI Authorization Screen (Refund)Bank
  • A refund of a Single Immediate Payment and of at least one multi-payment variation.
  • Customer-facing transaction notifications (push, SMS, email, in-app).
13LFI Authorization Screen (Payments with Open Beneficiaries and optional Delegated Authentication)Bank
  • Customer-facing payment notifications (push, SMS, email, in-app).
14LFI Authorization Screen (Bulk / Batch Payment)Bank
  • Customer-facing payment notifications (push, SMS, email, in-app).
Reference URL in tab
15LFI Authorization Screen (Bank Data Sharing — ongoing)Bank / FX house
  • The encrypted product finance rates variant.
16Supplementary InformationBank
  • One example, e.g. for a multi-payment or a future-dated payment.
Reference URL in tab
17LFI Insurance Data Sharing (ongoing)Insurance
  • The expanded data sharing clusters, and both active and expired policies.
  • The authorization screen for each insurance type you offer: home, renters, motor, travel, health, life.
  • The authorization screen with multiple insurance types selected, where applicable.
18LFI Insurance Quote Initiation (details screen)Insurance—
19LFI Consent Dashboard (list)All
  • Both data sharing and service initiation consents.
20LFI Consent Dashboard (details)All
  • Both data sharing and service initiation consents.
21LFI Consent Dashboard (revocation confirmation)All
  • Both data sharing and service initiation consents.
05 Raising the Ticket

What to include in your CX Certification ticket

Raise your submission through the CX Certification request type, in the Certification group of the Service Desk portal. Raise one ticket per brand or segment, each carrying that brand or segment's workbook.

FieldRequiredWhat to include
SummaryYesThe LFI and the brand or segment the workbook covers, for example CX Certification – <LFI legal name> – <brand or segment>.
AttachmentYesThe completed CX certification workbook (.xlsx) for that brand or segment.

The request has no organisation, environment, certification type or description fields. Nebras identifies your submission from the ticket Summary and the workbook's Summary sheet, so both MUST be complete.

Before you submit

  • The Summary sheet is complete: legal name, brand or segment, interface, submitter, job title and date.
  • Every applicable tab has designs for both your web browser and mobile app channels, and a Compliant value.
  • Every tab that does not apply is marked N/A.
  • The CBUAE / Nebras Assessment sections are blank.
  • Colleagues who need updates are added to the ticket as request participants (optional).
Not the Certification Evidence request

Do not submit CX evidence through the Certification Evidence request type used for functional, performance and penetration test evidence. Use the CX Certification request. The Service Desk is gated by Sandbox Trust Framework SSO; see Support & Service Desk for access prerequisites and alternative channels.

06 After Certification

Material changes to certified screens are resubmitted

Any material change to a production authorization page MUST be resubmitted for review and approval, as set out in the authorization page principles. Your consent journey and consent management interface MUST also continue to meet the CX requirements as those requirements are updated. See Ongoing Conformance.