This space is deprecated and no longer supported. Please use the latest available version here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Please complete as much of the requisites questionnaire as possible prior to the bilateral engagement sessions commencing .

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

LFI

Pre Requisites

OFTF Sandbox Directory Onboarding

  • Yes
  • No

OFTF Org ID

 

OFTF Org Name

 

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:

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 or different auth

To be discussed in bilateral sessions.

Ozone will provide the LFI inputs on how best to deploy instances during bilateral sessions

Joint

Context

Will the LFI be using CAAP

  • Yes
  • No

TBC

LFI

Pre Requisites

LFIs BIC Code/s

LFI

Scope

Supported APIs

Which of the APIs in the CBUAE standard will the LFI support ?

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 ?

This will be discussed during the bi-lateral sessions with each LFI.

Joint

Scope

Ozone Connect Event Notifications Supported

Which of the optional event notifications are going to be in operation

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 sessions

Joint

  • No labels