[GH-ISSUE #4991] [Bug]: cannot link Bank via gocardless anymore #27921

Closed
opened 2026-04-18 04:31:16 -05:00 by GiteaMirror · 13 comments
Owner

Originally created by @T-Lancer on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4991

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

After recently changing banks and adding my new bank C24, everything was working. After having setup some further sub-accounts I wanted to re-add my bank to link the new accounts and now I receiver this error after going through all the gocardless authentication.

An error occurred while linking your account, sorry! The potential issue could be: Request to Institution returned an error

I tried numerous times, eventually reaching a rate limit. I tried removing all accounts from that bank, and now I cannot add any.

adding the bank to my gocardless profile directly works however. But not through Actual.

How can we reproduce the issue?

This happens when trying to add accounts from a C24 (Germany) bank.

Where are you hosting Actual?

Local Docker container. 25.5.0

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @T-Lancer on GitHub (May 15, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4991 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? After recently changing banks and adding my new bank C24, everything was working. After having setup some further sub-accounts I wanted to re-add my bank to link the new accounts and now I receiver this error after going through all the gocardless authentication. > An error occurred while linking your account, sorry! The potential issue could be: Request to Institution returned an error I tried numerous times, eventually reaching a rate limit. I tried removing all accounts from that bank, and now I cannot add any. adding the bank to my gocardless profile directly works however. But not through Actual. ### How can we reproduce the issue? This happens when trying to add accounts from a C24 (Germany) bank. ### Where are you hosting Actual? Local Docker container. 25.5.0 ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bank syncwontfixbug labels 2026-04-18 04:31:16 -05:00
Author
Owner

@Rivsoft commented on GitHub (May 15, 2025):

I have the same issue with ABN Amro from Netherlands. Stopped working a few days ago, unlinked account, tried to link again and ABN Amro is not in the bank list for the Netherlands.

EDIT: Looks like my issue is related with gocardless issue particularly with my bank. Just keeping this here for reference.

Thanks

<!-- gh-comment-id:2885183683 --> @Rivsoft commented on GitHub (May 15, 2025): I have the same issue with ABN Amro from Netherlands. Stopped working a few days ago, unlinked account, tried to link again and ABN Amro is not in the bank list for the Netherlands. EDIT: Looks like my issue is related with gocardless issue particularly with my bank. Just keeping this here for reference. Thanks
Author
Owner

@T-Lancer commented on GitHub (May 18, 2025):

I rolled back to actual-server:25.4.0 and found that after authentication, I receive a success message. however the then shown list of found accounts is then empty. So I still cannot add any accounts.

I think this may be related to #4756 Gocardless bank sync: improved error handling for initial account linking. — thanks MatissJanis

So just better error handling. the issue clearly still persists.

<!-- gh-comment-id:2888844446 --> @T-Lancer commented on GitHub (May 18, 2025): I rolled back to actual-server:25.4.0 and found that after authentication, I receive a success message. however the then shown list of found accounts is then empty. So I still cannot add any accounts. I think this may be related to [#4756](https://github.com/actualbudget/actual/pull/4756) Gocardless bank sync: improved error handling for initial account linking. — thanks [MatissJanis](https://github.com/MatissJanis) So just better error handling. the issue clearly still persists.
Author
Owner

@felixoswald commented on GitHub (May 19, 2025):

I have the same issue with C24. After authentication with gocardless and redirect to Actual an error occurs and linking the account fails.

Actual client & server version: 25.5.0
Running latest docker image

Server log: actual.log

Image

<!-- gh-comment-id:2890611425 --> @felixoswald commented on GitHub (May 19, 2025): I have the same issue with C24. After authentication with gocardless and redirect to Actual an error occurs and linking the account fails. Actual client & server version: 25.5.0 Running latest docker image Server log: [actual.log](https://github.com/user-attachments/files/20300437/actual.log) ![Image](https://github.com/user-attachments/assets/41ee8f55-f29b-4761-9e73-920282eafb09)
Author
Owner

@felixoswald commented on GitHub (May 23, 2025):

I have sent the API request to gocardless manually via Postman and the request /api/v2/accounts/{id}/details/ for the deposit account (Tagesgeld) fails. So Actual probably selects the wrong account or gocardless have a problem with these type of accounts.

I have opened a support ticket with gocardless. Their team is working with C24 to get this resolved.

Our developers are already investigating an identical case with deposit accounts for this bank and have contacted the bank.
We'll send over this example as well and we'll keep you updated.

So it seems this is an issue with gocardless and Actual. The deposit account can't be connected and maybe a warning should be displayed. However, Actual should still link the regular account.

<!-- gh-comment-id:2905400868 --> @felixoswald commented on GitHub (May 23, 2025): I have sent the API request to gocardless manually via Postman and the request `/api/v2/accounts/{id}/details/` for the deposit account (Tagesgeld) fails. So Actual probably selects the wrong account or gocardless have a problem with these type of accounts. I have opened a support ticket with gocardless. Their team is working with C24 to get this resolved. > Our developers are already investigating an identical case with deposit accounts for this bank and have contacted the bank. > We'll send over this example as well and we'll keep you updated. So it seems this is an issue with gocardless and Actual. The deposit account can't be connected and maybe a warning should be displayed. However, Actual should still link the regular account.
Author
Owner

@T-Lancer commented on GitHub (May 26, 2025):

that's good. I had contacted C24, but they said there is nothing broken on their end (that they want to admit).

And that's true with the Tagesgeld accounts. It ignored them when I previously did have it working. Though I also had this issue with my previous Bank, Commerzbank. Just sort of took it as "oh I guess Tagesgeld accounts don't work". But that's great that Cocardless is aware of the issue and a working on it. Hopefully it will be fixed ASAP. as of this morning it definitely was not working yet.

<!-- gh-comment-id:2909348393 --> @T-Lancer commented on GitHub (May 26, 2025): that's good. I had contacted C24, but they said there is nothing broken on their end (that they want to admit). And that's true with the Tagesgeld accounts. It ignored them when I previously did have it working. Though I also had this issue with my previous Bank, Commerzbank. Just sort of took it as "oh I guess Tagesgeld accounts don't work". But that's great that Cocardless is aware of the issue and a working on it. Hopefully it will be fixed ASAP. as of this morning it definitely was not working yet.
Author
Owner

@IsThisThingStillOn commented on GitHub (May 27, 2025):

Ran into the same problem while trying to reconnect after it expired. I couldn't figure out what I was doing wrong until I googled the error message and found this issue.

<!-- gh-comment-id:2912819377 --> @IsThisThingStillOn commented on GitHub (May 27, 2025): Ran into the same problem while trying to reconnect after it expired. I couldn't figure out what I was doing wrong until I googled the error message and found this issue.
Author
Owner

@pelletencate commented on GitHub (Jun 1, 2025):

I rolled back to actual-server:25.4.0 and found that after authentication, I receive a success message. however the then shown list of found accounts is then empty. So I still cannot add any accounts.

I think this may be related to #4756 Gocardless bank sync: improved error handling for initial account linking. — thanks MatissJanis

So just better error handling. the issue clearly still persists.

I just noticed I have the same issue. I read the PR and I doubt it's related to that, it doesn't seem to touch anything before an error is raised.

I do wonder if it's related to https://github.com/actualbudget/actual/pull/4667 though. (Didn't review that all the way through) That was released in 25.4.0, try the version above that.

<!-- gh-comment-id:2926904292 --> @pelletencate commented on GitHub (Jun 1, 2025): > I rolled back to actual-server:25.4.0 and found that after authentication, I receive a success message. however the then shown list of found accounts is then empty. So I still cannot add any accounts. > > I think this may be related to [#4756](https://github.com/actualbudget/actual/pull/4756) Gocardless bank sync: improved error handling for initial account linking. — thanks [MatissJanis](https://github.com/MatissJanis) > > So just better error handling. the issue clearly still persists. I just noticed I have the same issue. I read the PR and I doubt it's related to that, it doesn't seem to touch anything before an error is raised. I do wonder if it's related to https://github.com/actualbudget/actual/pull/4667 though. (Didn't review that all the way through) That was released in 25.4.0, try the version above that.
Author
Owner

@T-Lancer commented on GitHub (Jun 2, 2025):

as stated, this was my assumption that the error just wasn't handled properly in 25.4.0. and the latest version, 25.5.0 already has improved error handling and that is what we currently see here, with the "Request to Institution returned an error" Error.

<!-- gh-comment-id:2929011538 --> @T-Lancer commented on GitHub (Jun 2, 2025): as stated, this was my assumption that the error just wasn't handled properly in 25.4.0. and the latest version, 25.5.0 already has improved error handling and that is what we currently see here, with the "Request to Institution returned an error" Error.
Author
Owner

@felixoswald commented on GitHub (Jun 4, 2025):

After updating to 25.6.0 (docker) gocardless displays an account selection (#5031) for the normal account and the deposit account for C24 Bank. Deselecting the deposit account and only use the normal account still doesn't work. Actual continues to show the error message and the account cant be linked.

So apparently the deposit account is not the problem.

I have also received a new mail from gocardless support. They are still working with C24 to solve the issue.

<!-- gh-comment-id:2939253485 --> @felixoswald commented on GitHub (Jun 4, 2025): After updating to 25.6.0 (docker) gocardless displays an account selection (#5031) for the normal account and the deposit account for C24 Bank. Deselecting the deposit account and only use the normal account still doesn't work. Actual continues to show the error message and the account cant be linked. So apparently the deposit account is not the problem. I have also received a new mail from gocardless support. They are still working with C24 to solve the issue.
Author
Owner

@matt-fidd commented on GitHub (Jun 4, 2025):

Sounds like this is a problem on the GoCardless end. I'll leave this open so that responses from GoCardless can be shared there's nothing to be done on the Actual side here.

<!-- gh-comment-id:2940325901 --> @matt-fidd commented on GitHub (Jun 4, 2025): Sounds like this is a problem on the GoCardless end. I'll leave this open so that responses from GoCardless can be shared there's nothing to be done on the Actual side here.
Author
Owner

@IsThisThingStillOn commented on GitHub (Jun 5, 2025):

I was able to link and sync one C24 pocket to my Actual 25.6.1 Docker (for this budget I only need one pocket). After the selection screen of all the accounts I entered the password a second time and got an error message "Not Found" (URL was my server-ip:port/gocardless/link?ref=xyz (xyz being a 36 charatcer long hexadecimal string with -), but going back to the tab with Actual, it displayed "Success. Link your accounts" (or something like that). Clicking the button I could sync my Actual account to the C24 account and sync the transactions.

<!-- gh-comment-id:2943063727 --> @IsThisThingStillOn commented on GitHub (Jun 5, 2025): I was able to link and sync one C24 pocket to my Actual 25.6.1 Docker (for this budget I only need one pocket). After the selection screen of all the accounts I entered the password a second time and got an error message "Not Found" (URL was my server-ip:port/gocardless/link?ref=xyz (xyz being a 36 charatcer long hexadecimal string with -), but going back to the tab with Actual, it displayed "Success. Link your accounts" (or something like that). Clicking the button I could sync my Actual account to the C24 account and sync the transactions.
Author
Owner

@T-Lancer commented on GitHub (Jun 5, 2025):

I can confirm that the authentication page for gocardless has changed. Upon first login it now asks which accounts to link.

If one attempts to link a Tagesgeld account, the process fails as before. But deselecting it allows me to link my Giro and Pocket accounts again.

So it seems they have "fixed" it. as Tagesgeld accounts previously seemed to be ignored anyway. And now one must actively prevent those accounts from getting linked as the process will fail otherwise.

<!-- gh-comment-id:2946187685 --> @T-Lancer commented on GitHub (Jun 5, 2025): I can confirm that the authentication page for gocardless has changed. Upon first login it now asks which accounts to link. If one attempts to link a Tagesgeld account, the process fails as before. But deselecting it allows me to link my Giro and Pocket accounts again. So it seems they have "fixed" it. as Tagesgeld accounts previously seemed to be ignored anyway. And now one must actively prevent those accounts from getting linked as the process will fail otherwise.
Author
Owner

@felixoswald commented on GitHub (Jun 8, 2025):

@T-Lancer it works for me too (except Tagesgeld). So they probably fixed it.

I think you can close this issue as resolved by gocardlesss.

<!-- gh-comment-id:2954081489 --> @felixoswald commented on GitHub (Jun 8, 2025): @T-Lancer it works for me too (except Tagesgeld). So they probably fixed it. I think you can close this issue as resolved by gocardlesss.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#27921