Component | Provider | Consumer | Interface | Description | Connection | Usage |
|---|
Authorisation Server | API Hub | LFI | API | | 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:
| 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 | LFI | API HUB | API | Swagger specification will be made available. These APIs should be implemented by the LFI so that the API Hub can ensure that the institution's Ozone Connect implementation is up and running. Integration testing and verifications. Health checks.
| MTLS | Service Availability Health Checks Integration QA |
Consent Event & Action APIs | LFI | API HUB | API | Swagger specification will be made available. Optional. Used by financial institution to get a notification for updated consent. Optional. Consent augmentation for LFIs to add additional information for some use cases. Optional. Consent validation for LFI to apply additional validation before the consent is created.
| MTLS | Event notifications Action calls |