Current bank feed issues

On occasion, a bank feed can encounter an error that affects a large number of users with that bank feed - this is different to a bank feed error specific to just one user. Our bank feed provider, Yodlee, keeps us up to date with these known bank feed issues and we'll keep you posted on this page. You can also learn more about Yodlee, bank feeds and what to expect here: Expectations of our bank feed service

Note

If your bank feed is showing an error but doesn't fall under one of the following banks, check out our user guides: Troubleshooting bank feeds and Bank feeds with persistent issues. If you are still having any difficulties, please contact our support team for assistance!


There are known issues affecting the following bank feeds

Investigations in progress

Santander Bank

412 Errors

UPDATE: March 31, 2020

Yodlee thank you for your sync attempts after their last update.

They are now working on a new update which they believe will be complete on April 3rd.

UPDATE: March 24, 2020

Yodlee have made some more changes since the update on March 20th. They expect to release those changes on March 25th.

Please let us know if you continue to see an error after that date, please let us know.

UPDATE: March 17, 2020

Yodlee have identified what they need to fix and they are now working on a solution. They estimate that their next update will be on March 20th.

Please try to sync your feed after this date and let us know if you still see any errors.

March 9, 2020

We have been seeing reports from users saying they are seeing a 412 error occurring on their Santander bank feed.

Yodlee are actively looking into the cause of the issue and we will let you know once we know more.

Capital One

Bank Feed Errors

March 3, 2020

We've received reports of feed sync errors occurring for this feed, due to ongoing issue at the Capital One online banking site. This is now considered a widespread issue. Our apologies for the inconvenience caused.

Yodlee are continuing to work with Capital One for a long term solution to this issue, however, unfortunately, at this stage they do not have any ETA.

For now, Yodlee have advised syncing your feed at regular intervals (ensuring any additional information is entered in the time available) in order to get the latest details.

We'll be sure to provide you with further updates as soon as they are received from Yodlee.

American Express PSD2

Bank Feed Errors

February 25, 2020

We have been informed that Salt Edge is seeing issues with American Express PSD2 feeds due to American Express revoking the token that allows Salt Edge access to American Express.

They have been working on a fix but it is now down to American Express to implement changes on their end.

We will let you know when those changes are complete but we are unable to provide any ETA's as to how long the process will take.

For now, Salt Edge suggest that you switch to using a non-PSD2 version of the American Express feed that you use. The non-PSD2 version of your American Express feed will be those feeds that do not have PSD2 in their name.

Ally Bank

426 errors

UPDATE: March 24, 2020

Thank you all for your patience, we've received another update from Yodlee.

There have been developments following some major changes that Ally Bank have made to their online banking site.

While we are actively pursuing a solution, this isn't something we're able to resolve immediately.

For some brief context, we've identified that there were some recent updates to how Ally Bank's MFA (multi-factor authentication) is now being sent to us that are no longer compatible with some of the structures we have in place.

We are currently working on a new generation bank feed system which will absolutely support this new kind of MFA.

We can’t give an ETA on that, but rest assured we’re working hard at it.

The best option for keeping your Ally Bank transactions up to date in PocketSmith, for now, is to unlink the bank feed account from the feed, and import bank files: How to manually import files when your bank feed is down.

If you would like further updates on this issue, please see our Bank feeds with persistent issues page.

UPDATE: March 10, 2020

We have noticed an increase in errors for Ally bank where users are getting time out errors after not receiving the code needed to fulfil the MFA requirements.

We don't know if this is related to the previous error yet but we are investigating with Yodlee and we will be in touch once we know more.

UPDATE: February 25, 2020

We have some great news!

Yodlee have released an update earlier than scheduled and it appears to have fixed the overall issue. We have received multiple updates from our users saying they have been able to sync successfully and Yodlee have also confirmed that they think they've fixed the issue.

They have also let us know that they currently expect the feed to require security input with every sync, but they are continuing to improve the feed so that in the future the security prompt with only appear on the first sync, after adding the feed to your PocketSmith account.

UPDATE: February 18, 2020

Thank you for your patience. Yodlee have let us know they are on track for the next update to be released on February 28th.

We'll be in touch as soon as possible with the latest news from Yodlee.

UPDATE: February 11, 2020

As you would have seen, Ally bank continues to present an error after the update released on February 7th.

Yodlee have now informed us that Ally Bank is actively blocking Yodlee’s connection attempts but they are working with Ally to fix the issue.

They predict the next update is due to be released on February 28th.

UPDATE: February 4, 2020

After users continued to see errors, Yodlee continued to work on the issue. They now have let us know that they have an update planned for February 7th.

UPDATE: January 29, 2020

Yodlee have let us know that they plan to release an update for the Ally Bank feed on January 31st.

After that date, please try to sync the feed and let us know if anything changes.

UPDATE: January 22, 2020

Yodlee are continuing to investigate the widespread error that has been occurring for this feed.

Please continue to sync your feed in the next couple of days, to see if the changes made by Yodlee have helped.

January 20, 2020

We have been receiving reports from our customers that they are seeing a 426 error on their Ally Bank bank feeds.

We have reported the issue to Yodlee who are now investigating.

We will be in touch once we know more.

Recently resolved

ASB Bank (New Zealand)

525 Errors

UPDATE: March 18, 2020

Yodlee have confirmed this issue is now resolved.

We expect this feed to update without any error messages following the next sync attempt, however, if you are noticing further issues after triggering a sync please do get in touch.

UPDATE: March 17, 2020

We are receiving reports from our users that they are now seeing 403 errors occurring for their ASB Bank (New Zealand) bank feeds.

We are continuing to look into this issue with Yodlee, and will keep you in the loop with any further developments.

March 16, 2020

We have been seeing many reports from our users that they are seeing 525 errors occurring for their ASB Bank (New Zealand) bank feeds.

We have reported this issue to Yodlee who are now investigating.

Thank you for your patience! We will be in touch once we know more.

Fidelity Investments (Investments)

412 Errors

UPDATE: March 17, 2020

Yodlee have put out a notice that they have made some changes to the feed and they believe the issue to be resolved.

Please try to sync your Fidelity Investments feeds and let us know if you are still experiencing any issues.

March 9, 2020

We have been receiving reports from our customers that they are seeing 412 feed sync errors occurring for the Fidelity Investments bank feeds.

We have reported the issue to Yodlee who are now investigating.

We will be in touch once we know more. Thank you for your patience.

Still need help? Contact Us Contact Us