Update - CAJALMENDRALEJO_BCOEESMM is available again
Sep 16, 2024 - 15:27 EEST
Sep 16, 2024 - 15:27 EEST
Update - ALPHABANK_BUCUROBU is available again
Sep 05, 2024 - 15:47 EEST
Sep 05, 2024 - 15:47 EEST
Update - The following 2 banks are available again:
MKB_BANK_MKKBHUHB
BANCA_PUEYO_BAPUES22XXX
Sep 04, 2024 - 13:26 EEST
MKB_BANK_MKKBHUHB
BANCA_PUEYO_BAPUES22XXX
Sep 04, 2024 - 13:26 EEST
Update - PAYSAFE_NETEGB21 is availabe again
Sep 03, 2024 - 16:37 EEST
Sep 03, 2024 - 16:37 EEST
Update - As of midday 2 September the following bank connections are unavailable due to the migration issues.
PEKAO_PKOPPLPW
BANK_OF_IRELAND_B365_BOFIIE2D
BANK_OF_IRELAND_BUSINESS_ONLINE_BOFIIE2D
PODRAVSKA_PDKCHR2X
ISTARSKA_KREDITNA_BANKA_ISKBHR2X
AGRAM_BANKA_KREZHR2X
SLATINSKA_SBSLHR2XXXX
ALPHABANK_BUCUROBU - Disabled
VOLVOFINANS_VLVOSE00X01
BANCA_PUEYO_BAPUES22XXX
CAJALMENDRALEJO_BCOEESMM
CONNEXIS_CASH_IMGBFR00X33
BNP_DE_BNPADEFFXXX
PAYSAFE_NETEGB21
MKB_BANK_MKKBHUHB
We will update here when any of these banks become available again.
We do not expect any more banks to become affected by this.
Sep 02, 2024 - 14:12 EEST
PEKAO_PKOPPLPW
BANK_OF_IRELAND_B365_BOFIIE2D
BANK_OF_IRELAND_BUSINESS_ONLINE_BOFIIE2D
PODRAVSKA_PDKCHR2X
ISTARSKA_KREDITNA_BANKA_ISKBHR2X
AGRAM_BANKA_KREZHR2X
SLATINSKA_SBSLHR2XXXX
ALPHABANK_BUCUROBU - Disabled
VOLVOFINANS_VLVOSE00X01
BANCA_PUEYO_BAPUES22XXX
CAJALMENDRALEJO_BCOEESMM
CONNEXIS_CASH_IMGBFR00X33
BNP_DE_BNPADEFFXXX
PAYSAFE_NETEGB21
MKB_BANK_MKKBHUHB
We will update here when any of these banks become available again.
We do not expect any more banks to become affected by this.
Sep 02, 2024 - 14:12 EEST
Update - Dear users,
The bi-annual certificate change migration is in its final stages.
2404 institutions are migrated and fully functional. ✅
17 institutions are likely to experience disruptions starting today:
PEKAO_PKOPPLPW
BNP_PARIBAS_BNPAFRPPXXX
BANK_OF_IRELAND_B365_BOFIIE2D
BNP_PARIBAS_ENTREPRISE_BNPAFRPPXXX
HELLO_BANK_BNPAFRPPXXX
BANK_OF_IRELAND_BUSINESS_ONLINE_BOFIIE2D
TRIODOS_ES_TRIOESMM
CAJADEINGENIEROS_CDENESBB
CAIXA_GUISSONA_CAXIES21XXX
BANCA_PUEYO_BAPUES22XXX
PODRAVSKA_PDKCHR2X
CAJALMENDRALEJO_BCOEESMM
ISTARSKA_KREDITNA_BANKA_ISKBHR2X
AGRAM_BANKA_KREZHR2X
SLATINSKA_SBSLHR2XXXX
CONNEXIS_CASH_IMGBFR00X33
BNP_DE_BNPADEFFXXX
We apologise for the inconvenience. Despite our best efforts, some banks have not been cooperative in ensuring an a continuous service. There is a risk these banks will become unusable(not available on the API) or accounts will need to be reconnected. There is however a chance that they will continue to work or recover in the coming hour/days.
Kind regards,
GoCardless Bank Account Data team.
Aug 30, 2024 - 15:34 EEST
The bi-annual certificate change migration is in its final stages.
2404 institutions are migrated and fully functional. ✅
17 institutions are likely to experience disruptions starting today:
PEKAO_PKOPPLPW
BNP_PARIBAS_BNPAFRPPXXX
BANK_OF_IRELAND_B365_BOFIIE2D
BNP_PARIBAS_ENTREPRISE_BNPAFRPPXXX
HELLO_BANK_BNPAFRPPXXX
BANK_OF_IRELAND_BUSINESS_ONLINE_BOFIIE2D
TRIODOS_ES_TRIOESMM
CAJADEINGENIEROS_CDENESBB
CAIXA_GUISSONA_CAXIES21XXX
BANCA_PUEYO_BAPUES22XXX
PODRAVSKA_PDKCHR2X
CAJALMENDRALEJO_BCOEESMM
ISTARSKA_KREDITNA_BANKA_ISKBHR2X
AGRAM_BANKA_KREZHR2X
SLATINSKA_SBSLHR2XXXX
CONNEXIS_CASH_IMGBFR00X33
BNP_DE_BNPADEFFXXX
We apologise for the inconvenience. Despite our best efforts, some banks have not been cooperative in ensuring an a continuous service. There is a risk these banks will become unusable(not available on the API) or accounts will need to be reconnected. There is however a chance that they will continue to work or recover in the coming hour/days.
Kind regards,
GoCardless Bank Account Data team.
Aug 30, 2024 - 15:34 EEST
Update - The migration is preceding as planned with limited disruption.
Later today one bank will need to have accounts reconnected:
ALPHA_FX_APAHGB2L
Additionally, the AMERICAN_EXPRESS_AESUGB21 connection might experience a disruption later this week. The connection might become unavailable for some time. We are working with the bank to keep this to a minimum. Additional updates about this will be posted here.
While we expect no other banks to experience any disruptions, we will post an update here, should any occur
Aug 14, 2024 - 11:13 EEST
Later today one bank will need to have accounts reconnected:
ALPHA_FX_APAHGB2L
Additionally, the AMERICAN_EXPRESS_AESUGB21 connection might experience a disruption later this week. The connection might become unavailable for some time. We are working with the bank to keep this to a minimum. Additional updates about this will be posted here.
While we expect no other banks to experience any disruptions, we will post an update here, should any occur
Aug 14, 2024 - 11:13 EEST
Update - The migration is in progress. There are changes to expected outcomes at several banks:
Despite previous assurances by a group of Danish banks, accounts will have to be reconnected at the following institutions:
SYDBANK_SYBKDK22
JYSKEBANK_JYBADKKK
LANDBOBANK_RINGDK22
SPAREKASSEN_SWESDK22
DJURSLANDS_DJURDK22
SKJERN_BANK_SKJBDK22
NORDFYNS_NSBKDK21
KREDITBANKEN_AAKRDK22
(the sheet with banks is updated to reflect this)
The change of certificates will happen shortly after 14:00 EEST (11:00 UTC)
We apologise for the inconvenience.
Jul 31, 2024 - 13:02 EEST
Despite previous assurances by a group of Danish banks, accounts will have to be reconnected at the following institutions:
SYDBANK_SYBKDK22
JYSKEBANK_JYBADKKK
LANDBOBANK_RINGDK22
SPAREKASSEN_SWESDK22
DJURSLANDS_DJURDK22
SKJERN_BANK_SKJBDK22
NORDFYNS_NSBKDK21
KREDITBANKEN_AAKRDK22
(the sheet with banks is updated to reflect this)
The change of certificates will happen shortly after 14:00 EEST (11:00 UTC)
We apologise for the inconvenience.
Jul 31, 2024 - 13:02 EEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 31, 2024 - 12:30 EEST
Jul 31, 2024 - 12:30 EEST
Scheduled - Dear customer,
As outlined in our communications dated July 4th (recap below), we will be commencing our eIDAS certificate migration process tomorrow, July 30th 12:30 EEST
While 90% of banks will not be impacted, there are some where users will need to reconnect accounts to continue accessing data.
What will happen and what to do:
For bank groups 1 (No Impact) and 2 (Handled change) no action is necessary.
For bank groups 3 (Reconnect 1 Aug) and 4 (Uncertain), when you see that all accounts for the bank have stopped working, you can direct your users to re-authorise in the same way as when the account has expired or been suspended. We urge you not to reconnect accounts before you see that they have stopped working so as not to end up going through the process twice.
UK banks are not affected.
List of banks and scenarios:
https://docs.google.com/spreadsheets/d/1dyB17GZYitisFjDTs4VZOptj-wYh9zK4yizeULAjTPo/ (the changes since the sheet was published have been marginal)
The scenarios:
1) “No Impact”
Previously connected accounts continue working after certificate change, no action necessary.
2) “Handled change”
On the 30-31 August accounts connected before late May/early June need to be reconnected; younger accounts continue working and require no action. These are the banks where we run certificates in parallel.
3) "Reconnect 1 Aug"
For this group of banks existing accounts will start to disconnect during the afternoon of 31 July 2024. If you notice all existing accounts for a bank return http-4xx, reconnect them starting 1 August. We will follow up on the status of banks on the 1st of August. Do not reconnect accounts before you see them disconnected.
4) “Uncertain”
These are banks which have ignored our requests to cooperate with certificate change. We therefore assume that accounts will need to be reconnected. An update on these banks will be included in the 1 August comms. Do not reconnect accounts before you see them disconnected.
Impact on billing:
We have designed the process so that the impact is minimal. As the change will take place at the very end of the billing cycle, you will not be double-billed for connections, because you will be (re)connecting new requisitions in the new billing period. Whether you will reconnect accounts on the afternoon of July 31st or in August will not impact your billing either.
Reach out to support if you have any questions.
Best regards,
Team GoCardless
Jul 31, 2024 12:30 - Sep 9, 2024 12:30 EEST
As outlined in our communications dated July 4th (recap below), we will be commencing our eIDAS certificate migration process tomorrow, July 30th 12:30 EEST
While 90% of banks will not be impacted, there are some where users will need to reconnect accounts to continue accessing data.
What will happen and what to do:
For bank groups 1 (No Impact) and 2 (Handled change) no action is necessary.
For bank groups 3 (Reconnect 1 Aug) and 4 (Uncertain), when you see that all accounts for the bank have stopped working, you can direct your users to re-authorise in the same way as when the account has expired or been suspended. We urge you not to reconnect accounts before you see that they have stopped working so as not to end up going through the process twice.
UK banks are not affected.
List of banks and scenarios:
https://docs.google.com/spreadsheets/d/1dyB17GZYitisFjDTs4VZOptj-wYh9zK4yizeULAjTPo/ (the changes since the sheet was published have been marginal)
The scenarios:
1) “No Impact”
Previously connected accounts continue working after certificate change, no action necessary.
2) “Handled change”
On the 30-31 August accounts connected before late May/early June need to be reconnected; younger accounts continue working and require no action. These are the banks where we run certificates in parallel.
3) "Reconnect 1 Aug"
For this group of banks existing accounts will start to disconnect during the afternoon of 31 July 2024. If you notice all existing accounts for a bank return http-4xx, reconnect them starting 1 August. We will follow up on the status of banks on the 1st of August. Do not reconnect accounts before you see them disconnected.
4) “Uncertain”
These are banks which have ignored our requests to cooperate with certificate change. We therefore assume that accounts will need to be reconnected. An update on these banks will be included in the 1 August comms. Do not reconnect accounts before you see them disconnected.
Impact on billing:
We have designed the process so that the impact is minimal. As the change will take place at the very end of the billing cycle, you will not be double-billed for connections, because you will be (re)connecting new requisitions in the new billing period. Whether you will reconnect accounts on the afternoon of July 31st or in August will not impact your billing either.
Reach out to support if you have any questions.
Best regards,
Team GoCardless
Jul 31, 2024 12:30 - Sep 9, 2024 12:30 EEST
About This Site
GoCardless Bank Account Data status page.
This is the status of GoCardless Bank Account Data API and Portal (https://bankaccountdata.gocardless.com)
The service, previously known as Nordigen, provides you secure regulated access to 2500+ bank's data across Europe and the UK - Account Information Service (AIS) within the PSD2 framework.
Authorise your accounts, then access account details, balances, and transactions via the API.
Documentation: https://developer.gocardless.com/bank-account-data/quick-start-guide
Support & FAQs: https://bankaccountdata.zendesk.com/hc/en-gb
If you are looking for the status page for GoCardless Payments, visit https://www.gocardless-status.com/
GoCardless Bank Account Data API
?
Operational
GoCardless Bank Account Data Portal
?
Operational
Banks Coverage - AIS APIs of 2300+ upstream institutions
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.