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

1. Introduction

The following information is required by Ozone at the start of the integration process.

2. Questionnaire

Section	Question	Answer	Additional Information to be Supplied to Ozone	Provided by

Section	Question	Answer	Additional Information to be Supplied to Ozone	Provided by
Pre Requisites	LFI Name			`LFI`
Pre Requisites	Are you onboarded onto the OFTF Sandbox Directory?	Yes No	Please provide the email ID of the PTC	`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 authorisation.	Enter brands e.g. retail/corporate/wholesale	Ozone will provide the LFI inputs on how best to deploy instances during bilateral sessions	`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`
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	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.	`LFI`
Scope	Optional Features Which of the optional features will you be implementing?		This will be discussed during the bi-lateral sessions with each LFI.	`LFI`