Follow a step-by-step journey to securely integrate with SingleView Open Banking APIs
This guide provides a structured overview of the integration process required to connect to SingleView Open Banking APIs. By following the steps outlined below, you will be able to establish a secure connection, authenticate requests, and access Open Banking data and services.
The integration process consists of five key stages:
The SingleView Console serves as the primary interface for managing your Open Banking integration. Before accessing any APIs, you must create and configure a console account.
Through the Console, you can:
A configured Console account with an application ready for integration.
SingleView APIs are accessible only through secure communication channels. Prior to making API requests, you must configure the required connectivity and security settings.
This includes:
A secure communication channel established between your application and the SingleView platform.
All API requests must be authenticated and authorized in accordance with SingleView security requirements.
Depending on the API and environment, authentication may involve:
The ability to successfully authenticate and authorize API requests.
Once connectivity and authentication have been configured, you can validate your integration by accessing Open Banking data through the Raw Data APIs.
A typical workflow includes:
Raw Data APIs provide access to:
Successful retrieval of customer-permissioned banking data under Open Banking Raw Data API services.
Following successful validation of the Raw Data APIs, you may begin utilizing SingleView's data products and business use case APIs.
These services transform raw banking data into actionable insights that can support onboarding, verification, risk assessment, lending, and personal finance use cases.
A typical workflow includes:
Available use cases include:
Successful retrieval of customer-permissioned banking data under Open Banking Data API Use Cases services.
After completing the integration journey outlined above, you may proceed with:
For detailed implementation instructions, refer to the relevant sections of this documentation.