Overview
The AISP APIs have been built in line with v3.1 of the Open Banking API Specification and are accessible by any regulated third party. It is advised that any third party wishing to utilise these APIs familiarizes themselves with the Open Banking specification.
You will receive a response with the relevant information requested, only if the following conditions pertaining to the user are met.
- The company to which the user belongs must be an active SVB client and must be eligible to access account information through an CBPII
- The service will confirm that the client associated with the user has been configured for API Services
- The user must be in an active status that allows the user to logon to Online Banking or Mobile Banking
- The service will confirm that the user is a valid user on online banking, and that they are not in frozen, disabled, locked, modified pending, deleted pending, pending or partially set up
- The user must be eligible to access account information through an CBPII
- The service will confirm that the user associated with the client has been configured for API (CBPII) services
- The user must be eligible to view information for the specific account over the Online banking / Mobile banking channels
- The service will confirm, specific to an account or all accounts, whether the user has access to account information
- The consent provided by the user must be active
- Refresh Token is valid only for 90 days
CBPII Consents
SVB has implemented the following endpoints to allow TPPs to generate, get and delete a funds confirmation consent.
Endpoints:
-
POST /funds-confirmation-consents
-
GET /funds-confirmation-consents/{ConsentId}
- Delete /funds-confirmation-consents/{ConsentId}
Create Funds Confirmations
This endpoints allows CBPIIs to create a funds-confirmation resource request to check whether funds are available in the specific account established during consent creation and authorization.
Endpoints:
- POST /funds-confirmations