Due to service stability considerations, GoCardless Bank Account Data automatically suspends an account if there were 10 consecutive failed attempts to access it.
The logic around account suspension is described in this article:
account suspension.
However, the key underlying issue is what errors caused the account to be suspended and what to do about them.
Note that in the table below not all errors increase the error count.
Error types, codes, and recommended steps to handle:
Errors that stem from malformed requests and similar issues are omitted from this table but can be looked up either in our documentation or in the swagger.
Type | Code | Detail | Explanation | Increases error count? | Action to take |
UnknownRequestError | 500 | Request to Institution returned an error | Unknown error while requesting data | Yes | Try reconnecting the account (once); if the error occurs more than once, report it to the GoCardless Bank Account Data support team. While these errors always get flagged to us automatically, your input will help resolve them faster |
RateLimitError | 429 | Daily request limit set by the Institution has been exceeded | You have hit the rate limit for requests/day for the account. Not to be confused with the API-level limit as explained here | No |
Wait, then try again when the limit resets. Information on scope and reset in headers can be found here. Handling these will depend on which limit you have hit - API-level, or Account-level |
ServiceError | 503 | Institution service unavailable | Temporary issues with the bank handling the request, such as: downtime or random server errors | No | Wait, then try again. Check the bank's status page whether they are experiencing downtime |
AccessExpiredError | 401 | Access has expired or it has been revoked |
Cases where the bank's response indicates accounts need to be reconnected, e.g.: - revoked consent by the user; - expired consent |
Yes | Reconnect the account |
AccountInactiveError | 401 | Account has been deactivated or it no longer exists | The user's bank account is no longer active | Yes | Ask the user to connect a valid account or ignore this account if other valid accounts are present. This error is rare |
AccountAccessForbidden | 403 | Access to the account is forbidden. The user might not have the necessary permissions | Applies to situations where something is blocking the user from accessing their account information. In such cases, the user should contact their bank directly | Yes | Try reconnecting the account (once) and if the error occurs more than once, report it to the bank's support team and ask whether this has occurred because specific permissions that allow the user to establish PSD2 connections are not enabled. These cases often occur for accounts that have multiple owners, and, therefore, require multiple persons to authorise access. Or, alternatively, the user might need to enable some settings in the bank's portal. A key resource to know and prevent many of these errors and other edge cases is our public coverage sheet - column K contains known limitations for banks |
AccountProcessing | 409 | Your account data is currently being processed. Please try again shortly, or poll /accounts/{account_id}/ endpoint and retry when status is READY | Your account data is currently being processed. Please try again shortly, or poll /accounts/{account_id}/ endpoint and retry when status is READY | No | Wait until the account is ready |
Account suspended | 409 | This account or its requisition was suspended due to numerous errors that occurred while accessing it | This account or its requisition was suspended due to numerous errors that occurred while accessing it | Not applicable | Reconnect the account |
Comments
0 comments
Article is closed for comments.