Here is information on where our implementation of AIS (Account Information Service) APIs differ from the Open Banking specifications.
Payment accounts
Fields
Transactions data
Consent
Step up
Permissions
General specifications
We support current accounts, savings accounts and credit cards for AIS APIs.
We can return transactions data from the previous 13 months. The transaction date (From and To date) should be a date prior to today's date.
The account transaction details you have requested will be provided, based on the transaction date range specified during consent creation. If the request falls outside the consent transaction date range, it will be ignored.
For credit card accounts:
Please note: we do not send the current amount owed by the customer, we only share what they have available to spend and their credit limit.
For current accounts:
For saving accounts:
As part of the AIS consent process, you will redirect the PSU (customer) to the Co-operative Bank or smile login page. They can then authenticate themselves using our online banking services or mobile app, then provide their consent for your service. We will then redirect them back to your application.
Then the PSU will see screens showing:
As per regulatory requirements, when using the AIS, if the PSU would like access to the following 'sensitive' information, then you will need to re-direct the PSU to our Co-operative Bank or smile login page for authentication using our online banking services or mobile app:
No further consent will be sought, so once successfully authenticated the PSU will be re-directed back to the AISP who can then request the 'sensitive' information.
In our general specifications page, you can found out how to construct an AISP step up Universal Link in the parameters section. You can also see the error messages you will receive when calling the APIs.
The permissions we allow for AIS include:
To read about settings and specifications which apply to all of our APIs, see our general specifications.