The Authorisation Server and Consent Manager is built, deployed and maintained by Ozone. The consumer of these APIs are the LFIs.
The LFI is expected to build, deploy and maintain screens on their mobile and/or web app to support the Consent Authorisation flow.
The LFI is expected to build, deploy and maintain the Ozone Connect API for Data Sharing and Service Initiation.

Component	Provider	Consumer	Interface	Description	Connection	Usage
Authorisation Server	API Hub	LFI	API	Swagger specification will be made available Exposes endpoints to the LFI to support: Consent Authorisation Access token issuing	MTLS	Authorisation Flow
Consent Manager	API Hub	LFI	API	Swagger specification will be made available TPPs do not connect to the consent manager directly Exposes endpoints to the LFI to support: Consent Authorisation Consent management and reporting	MTLS	Authorisation Flow Consent Dashboard
Ozone Connect	LFI	API Hub	API	Swagger specification will be made available for Data Sharing, Service Initiation and Insurance TPPs do not connect to the Ozone Connect API directly The Ozone Connect API is an interface on top of the LFI core banking system. LFIs will be responsible for the mapping between their core banking system and the Ozone Connect API specification LFIs only implement the Ozone Connect API endpoints to support their existing offering i.e Data Sharing: Accounts, Balance, Transactions etc Service Initiation: Domestic payment, Standing Orders, International Payments etc Insurance: Motor insurance quotes	MTLS	Data Sharing Service Initiation Insurance
Health Check API APIs
Consent Event & Action APIs

4. LFI Integration Guide

4.1 LFI Responsibilities

...