The DSOP Control Information Common Standard is the foundation that enables the development of DSOP solutions where the financial institutions digitally deliver account information to the public agencies via a machine-to-machine integration. The common standard consists of two APIs:
- The Customer Relations & Account Servicer Overview API consisting of two endpoints which provide either information about customer relations regarding a person or organisation (control object) or information about the financial institution servicing a specific account.
- The DSOP Control API consisting of six endpoints which provide either account information regarding a control object or information about who owns an account.
The common standard makes it easy for financial institutions to implement new services based on the common standard in the future.
Throughout the documentation the public agencies will be called ‘data consumer’ and the financial institutions ‘data providers’. See the Glossary for more information about terms used in this documentation and their definition.
The documentation is divided into two separate parts:
- The documentation of the Common Standard containing necessary technical documents which are common to all the various DSOP solutions using the Common Standard. This documentation is in English.
- The documentation related to the various DSOP solutions which is specific to a solution. The documentation of the DSOP Solutions may be in Norwegian or in English.
There are several benefits using the common standard both for the data providers and for the data consumers:
- The data provided by the data providers is standardised and structured across the industry.
- The overall data quality provided by the data providers is better than in the analogue world.
- The data consumers can streamline their data capture and build better solutions on top of the integration.
- The data consumers will potentially be able to send more requests and get qualitatively better account information faster than doing it analog.
- The data providers can implement DSOP solutions delivering account information to various agencies faster, as the common standard lays the foundation for several solutions.
- The operational processes defined for the DSOP Control Common Standard can be reused across all services that use the DSOP Control solution.
Data flow in DSOP Control Common Standard Solutions
The requests from the data consumers will be similar for all the data providers using the Common Standard, but the purpose from each data consumer (with reference to the legal basis), the validation of the requests and the filtered delivery of the account information delivered to the data consumers, will be different per DSOP Service.
1. The request from the data consumers first goes to the solution DSOP Customer Relations & Account provider Overview (DSOP Oversikt over kundeforhold og kontofører) that will return either:
- a list of financial institutions that have - or had - a customer relationship with the “control object” (organization number/personal identification number/d-number) in a given time period, or
- the financial institution that is servicing a specific account number at the request date.
This solution is serviced by Bits for the Financial Industry.
Overview of current endpoints in Customer Relations & Account Servicer Overview
| Endpoint | Description | Link to data model |
|---|---|---|
| a) customerRelationships | Returns the financial institutions where the given customer has or had relations in a given time period. | Description of customerRelationships |
| b) accountServicingProvider | Returns the financial institution that is servicing the account provided in the request at the request date. Returns if the account is a collection account (see Glossary). | Description of accountServicingProvider |
2. DSOP Control. This is serviced by each financial institution. There are two starting points for the DSOP Control API:
- Control object based request: Based on the list of financial institutions provided in step 1a) the data consumer sends an account-list request (2a) to each of these data providers (the financial institutions). The data consumer then asks for more account information for each of these accounts, such as+ account details with, balance (2b), transaction history (2c), payment cards (2d) and roles (2e) associated with the account in a given time period.
- Account number based request: Based on the financial institution provided in step 1b) the data consumer sends an accountOwner request (2f) the data provider (the financial institutions) for an account number in a given time period.
The DSOP Control API is serviced by each bank.
Content of DSOP Control (serviced by financial institutions, the data providers)
The DSOP Control API delivers a unique set of information via five endpoints. How many of these endpoints each individual DSOP service consists of may vary depending on the need and legal basis of the data consumer entitled to receive the information. For all DSOP services using the DSOP Control API, the data consumer will have to start the requests first with either the endpoint Accounts (Account List) or the endpoint Owners. For more information about what kind of data is included in the different endpoints we refer to the data model page. Note that each service might filter out some of the information provided in the endpoint. For a complete overview of what data is shared in each individual solution we invite you to look at the services’ respective data model page.
Overview of current endpoints
First request to Account List (2a) or Owners (2f)
The first request to be done by the Data Consumers is to the following endpoints.
| Endpoint | Description | Link to data model |
|---|---|---|
| a) Accounts | List of the accounts associated to a control object and owners of all the returned accounts | Description of Accounts |
| f) Owners | Returns a list of account owners for a specified time period, including the period during which wach owner held the role and the accounts type per account owner. | Description of Owners |
Overview of available endpoints after Account List (2a)
After a successful response from Accounts, the Data Consumers can make requests to the following endpoints per account (according to the specific service):
| Endpoint | Description | Link to data model |
|---|---|---|
| b) Account details | Returns the balance, credit line, type, start and end date, and owner of an account | Description of Account details |
| c) Transactions | Returns transactions on an account in a given time period. | Description of Transactions |
| d) Cards | Returns an overview of the different cards associated with an account in a given time period. | Description of Cards |
| e) Roles | Returns an overview of the different roles associated with an account in a given time period. | Description of Roles |
Change Log
| Date | Version | Change |
|---|---|---|
| xx.xx.26 | 2.1 | Changes in the documentation related to the introduction of the new endpoint Owners in the DSOP Control API. |
| 20.03.24 | 2.0 | New version of the DSOP Control API generating extensive changes throughout all documentation. |
| 12.04.23 | 1.0 | Translated to English |