Below we list the expected errors in the BAI API(s) response:
API |
Error |
MESSAGE TO BOOKKEEPING PARTY |
Reason (detail) |
Solution/Action |
|
ALL |
Not found |
||||
404 |
Account not found or consent user does not have the correct authorization |
Account does not exists anymore or |
Request a new consent for the account(s) |
||
ALL |
404 |
Consent user does not exist anymore |
Customer that has given consent does not exist anymore |
Request a new consent for the account(s) |
|
Balance |
Unauthorized |
||||
401 |
Consent user not authorized to view the balance |
Customer does not have the authorization to view balance in Rabo Internet Banking or Rabo Business Banking |
Request to give the user that signed the consent access to the balance information of the account in RIB/RBB |
||
Transactions |
401 |
Consent user not authorized to view the transactions |
Customer does not have authorization to view transactions in Rabo Internet Banking or Rabo Business Banking |
Request to give the user that signed the consent access to the transaction information of the account in RIB/RBB |
|
Transactions |
401 |
Consent user has no authorization for the requested period |
Scenario 1: Consent has been signed with a private card instead of business card Scenario 2: The account is closed |
Request a new consent for the account(s) |
|
ALL |
Bad request |
||||
400 |
Invalid accountId |
Scenario 1: the encrypted account ID pattern sent in the request is invalid. |
Correct the request details or request the user to sign a new consent |
||
ALL |
400 |
Given accountid does not belong to the consent |
This accountId does not match with the consent that is connected to the access token |
Sent a request to the accounts endpoint in order to retrieve the correct accountid(s) belonging to the consent |