Consent overview
Manage customer authorization for secure access to financial data through Data APIs
Access to financial data through Data APIs is governed by a secure, consent-based authorization process. Before an application can retrieve any customer financial data, the customer must explicitly grant permission for the requested access.
Consent management ensures that customers remain in control of how their financial information is shared and used. Through the SingleView Open Banking platform, applications can create, retrieve, and revoke consent for accessing account information.
Consent Lifecycle
A consent follows a defined lifecycle within the Data API integration process.
This process ensures that financial data access remains transparent, secure, and user-controlled.
Security and Compliance
Consent management is designed to align with Open Banking security and regulatory requirements. Key principles include:
- Explicit customer authorization before accessing financial data
- Secure authentication through the customer’s bank
- Time-bound consent validity
- Ability for customers or applications to revoke consent
These safeguards ensure that data access remains secure, transparent, and compliant with Open Banking standards.
Consent Management Options
Consent management in Data APIs typically involves three core operations:
Together, these operations allow applications to securely request, verify, and terminate access to customer financial data.
Consent Scope and Permissions
When creating a consent, the application must specify the scope and permissions that define the type of financial data it intends to access. These permissions determine which API services can be used after the customer authorizes the consent.
During consent creation, the request should include the appropriate permission values corresponding to the required services, such as accessing account details, balances, or transaction information. Only the APIs associated with the approved permissions will be accessible using the generated Consent ID.
Ensure that the correct permissions are included in the consent request based on the API services your application needs to access.
Scope | useCaseType | Permissions |
|---|---|---|
To access all Raw Data API services:
|
|
|
To access Account Aggregation service under Data Use Case APIs |
|
|
To access Account Check service under Data Use Case APIs |
|
|
To access Account Aggregation service under Data Use Case APIs |
|
|
To access Credit Check service under Data Use Case APIs |
|
|
To access Customer Verification service under Data Use Case APIs |
|
|
To access Data Enrichment service under Data Use Case APIs |
|
|
To access E-Statement service under Data Use Case APIs |
|
|
To access Expense Check service under Data Use Case APIs |
|
|
To access IBAN Validation service under Data Use Case APIs |
|
|
To access Income Check service under Data Use Case APIs |
|
|
To access KYC service under Data Use Case APIs |
|
|
Updated July 2, 2026
Was this helpful?