Service Provider model
Describing the optional Service Provider model to provide a single integration for multi-client setup.
There are two main connection schemes, how clients can connect and use Connect services:
Single clients - one customer with a dedicated connection certificate using our banking services
Service provider model - grants access to multiple customers or legal entities with a single connection certificate. This model is suitable corporations with several legal entities operating in different countries or technical service providers.
Single clients
The client exclusively holds the authentication certificate and connection software, which authorizes access for only one customer or legal entity.
Service provider model
The service provider model facilitates access for multiple customers or legal entities using a single connection certificate, making it versatile for a range of business situations and corporate connections.
Typical cases where such model is useful:
Corporations that operate multiple legal entities across various countries or for distinct objectives, and all utilize LHV's services and accounts.
Technical service providers offering their integrations to LHV customers, possibly in combination with other services,
In this model there are two kinds of clients:
Service provider itself (software owner, technical aggregator) - they are directly connected to Connect API
End user clients, who use Connect via service providers - not directly connected to Connect
For all requests to Connect API we also need to know the end user - the actual client that uses the service providers services. For this we require two HTTP headers in addition to regular expected input:
Client-Code - this is typically end customers Registration Code, UK Company House Number or similar code in any national company register.
Client-Country - ISO country code of the Code issuing country
Last updated
Was this helpful?