Versions Compared

Version Old Version 1 New Version Current
Changes made by

Chris Michael

Isla Humphreys

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

This form is for information only. The information will be gathered using the API Hub Service Desk at the start of the integration process.

Expand
titleMENU
Table of Contents
stylenone

1. Introduction

This questionnaire will need to be completed by LFIs. We discuss this during the final technical engagement session and also during the first bilateral session with each LFIThe following information is required by Ozone at the start of the integration process.

2. Questionnaire

OFTF Org Name

Pre Requisites

Section

Question

Answer

Additional Information to be Supplied to Ozone

Provided by

Pre Requisites

Licences obtained from CBUAE

  •  Yes
  •  No

LFI

Pre Requisites

LFI Mercury KYC/KYB Process Complete

  •  Yes
  •  No

LFILFI Name

LFI

Pre Requisites

Are you onboarded onto the OFTF Sandbox Directory Onboarding?

  •  Yes
  •  No

OFTF Org ID

Code Block
Code Block

LFI

Context

Key contacts and any other technical contacts that should be included on the bilateral sessions as well as any communications for the duration of the implementation.

  • Contact 1 Name

  • Contact 1 Email

  • Contact 1 Role

  • Contact 2 Name:

  • Contact 2 Email:

  • Contact 2 Role:

Please provide the email ID of the PTC

Code Block
LFI
Context
Where will Ozone Connect be hosted?
  •  Azure
  •  AWS
  •  OCI
  •  GCP
  •  On Prem
LFI
Context
Which digital channels does the LFI currently support
  •  Web
  •  Mobile
LFI
Context
How many production instances are required?
e.g. different core banking for products (retail/corporate/wholesale) or different auth To be discussed in bilateral sessions.authorisation.
Enter brands e.g. retail/corporate/wholesale
Ozone will provide the LFI inputs on how best to deploy instances during bilateral sessionsJoint
LFI
Pre Requisites
LFI Code/s
This will form part of the URL for the TPP and LFI facing domain name
Enter codes for each brand when confirmed
Ozone will suggest codes for retail/corporate/wholesale, etc. 
LFI
Context
Will the LFI be using CAAP
  •  Yes
  •  No
TBC
LFI
LFIs BIC Code/s
LFI
Scope
Supported APIs
Which of the APIs in the CBUAE standard will the LFI support?
  •  Bank Service Initiation
  •  Bank Data Sharing
  •  Motor Insurance Data SharingConsent
  •  Event & Actions OpenAPI
This will be discussed during the bi-lateral sessions with each LFI.
LFI
Scope
Ozone Connect APIs Implemented
Which of the optional Ozone Connect APIs will you implement ?Select Health Check API endpoints
  •  GET /hello
  •  GET /hello-mtls
  •  GET /echo-cert
This will be discussed during the bi-lateral sessions with each LFI.
JointLFI
ScopeOzone Connect Event Notifications Supported
Optional Features
Which of the optional event notifications are going to be in operationfeatures will you be implementing?
  •  Consent Pre-Validation 
  •  Consent Augmentation
  •  Consent Event Notification
This will be discussed during the bi-lateral sessions with each LFI.
Functional Configuration
API Functional Configuration
This section will consist of configuration details that are functional in nature.
The set of questions will be determined as API implementation progresses
e.g. daily payment limit, supported currencies, supported working days etc., supported account number addressing schemes etc.
Ozone will provide the LFI inputs on how best to deploy instances during bilateral sessionsJoint