Account Access Consents

Version 3.1.2 (Current Version)

What this API does

When using our Sandbox, we have a predefined, pre-authorised set of consents to be used within the environment. The predefined authorisation code is provided in the test data

This API lets you create, remove and check customer consent status.

Before calling the API, you must have an access token issued by CYBG using a 'Client Credentials' grant.

This API does not support Readoffers or Readproducts permissions. 

This API lets you ask CYBG to create a new account-access-consent resource:

  • It lets you send a copy of the consent to CYBG to authorise access to account and transaction information
  • You can’t pre-select a set of accounts for account-access-consent authorisation
  • CYBG will create the account-access-consent resource and provide a unique ConsentID
  • Before calling the API, you must have an access token issued by CYBG using a client credentials grant

We have a predefined, pre-authorised set of consents to be used within the Sandbox environment. The predefined authorisation code is provided in the test data.

Using the authorisation code, create request for a new token using grant type = authorization_code. 

The token will return the consent ID as part of ID Token in the token response. 

You can retrieve an account-access-consent resource that you’ve created to check its status.

Before calling the API, you must have an access token issued by CYBG using a client credentials grant.

If a customer revokes consent to data access you must delete the account-access-consent resource with CYBG before you confirm consent revocation with the customer.

Having trouble?

Contact our dedicated team members via our ticketing system or via our support mailbox, OpenBankingResponse@cybg.com

Opens in a new window Contact