Bank feeds with persistent issues

Due to the nature of using bank feeds rather than direct feeds to sync your transactions into PocketSmith, some bank feeds have persistent issues that are unable to be resolved in the foreseeable future.
We are aware of the following long-term behaviors on several bank feeds.
Note

If you are still having any difficulties, please check our user guide: Current bank feed issues or contact PocketSmith support for assistance.


Affected bank feeds

New Zealand banks

Bank of New Zealand BNZ (New Zealand)

Transactions on BNZ bank feeds are set to Pending status for at least four days before being moved into Posted status. We do this to avoid duplicate transactions on these feeds as BNZ often changes transaction details in the first few days after a transaction is made.

Most transactions made on the weekend will not be synced into PocketSmith until the following Tuesday due to restrictions at BNZ.

NetGuard

Users with NetGuard authentication may occasionally notice that the coordinates for the NetGuard prompt do not display. Wait for the authentication request to expire and try to re-sync the bank feed - this is usually temporary.

NetGuard users may also experience an occasional 429 Feed sync error, caused by a NetGuard settings prompt. To resolve this, log in to your BNZ online banking and disable NetGuard in your settings. Save the change and then re-enable NetGuard and save the change again.

Westpac (New Zealand)

Merchant information displayed in PocketSmith is subject to change for a few days after being synced into PocketSmith. We also regularly see that the merchant name is concatenated with additional information about the transaction, for example the date and time of the transaction.

Westpac NZ bank feeds occasionally display false "No accounts found (414)" errors which are often fixed by refreshing the bank feed.

Credential (402) errors are common when first setting up your credentials on Westpac (New Zealand). If you're seeing this, it may be due to using the UserID rather than your Customer Number when entering your credentials:

Westpac (New Zealand) allows customers to alias a Customer Number with their UserID. If you use the UserID in your bank feed credentials, then you may encounter a Credentials (402) error. However, if you use your Customer Number rather than your UserID, you should be able to make a successful connection.

ASB Bank (New Zealand)

402 feed sync errors

When Yodlee executes a sync for ASB feeds, they try to sync each type (bank, credits, loans etc) in quick succession. This quick consecutive sync triggers a warning on ASB’s system locking the bank feed out, causing the 402 feed sync error to occur.

We can see what is required to most effectively resolve this, however, it will take some time to implement, as it requires an overall upgrade of our entire bank feeds platform. We are unable to provide an ETA on when this will be done, but rest assured we’re working hard at it. 

For now, we've seen a number of users report successful syncs of their ASB feeds after changing to manual sync. We've also seen some successful automatic syncs as a result of a change made by our engineers, to increase wait-time between account types. Please feel free to try disabling the Manual-only setting and try automatic syncing for this feed again.
If you are continuing to see a 402 feed sync error occur after updating your credentials once, please refer to the steps below for changing your feed to manual sync only, as this is highly likely to resolve the issue for you.

Once you've changed your feed to manual syncing, please then trigger a sync on one account type, wait a few minutes and then trigger another sync for the next account type.

For example, triggering a sync on the ASB bank type feed and then after a few minutes triggering a sync on the ASB credit type feed.

To change the ASB bank feed to manual sync only, just follow the instructions in our Learn Centre: Change bank feed syncing to be only manually triggered.

505 feed sync errors

ASB Bank is intermittently affected by Google re-CAPTCHA. Google reCAPTCHA is a security measure that some banks use for extra security. It is usually triggered when you log into your bank using the incognito tab or using a different computer.

Unfortunately, this particular security process blocks Yodlee from accessing the data required for bank feeds and results in a 505 error on your bank feed.

Yodlee report that re-CAPTCHA is only sometimes triggered which means that you should be able to sync your feed without any problem.

If you do encounter a 505 error, we recommend that you try to sync a few times. If the 505 error persists, we recommend that you wait a few days and it should be able to sync after that.

Pending transactions for Credit Card account types

ASB Bank NZ does not support Pending transactions for Credit Card account types even when this feature is enabled on the bank feed.

Weekend transactions

Most transactions made on the weekend will not be synced into PocketSmith until the following Tuesday due to restrictions at ASB.

Kiwibank (New Zealand)

Kiwibank users frequently see a 429 error on their bank feeds. This occurs when Kiwibank asks their customers to view new promotions or Terms & Conditions agreements. To resolve these, log in to your Kiwibank online banking and click through to all your account transaction listings and respond to any messages from Kiwibank. Once this is complete, return to PocketSmith and sync your bank feed - the error should clear.

The Kiwibank bank feed does not yet support Investments account types.

Kiwibank occasionally audits their security, which results in warnings or phone calls to their customers about possible third party access to their accounts. Our bank feed provider, Yodlee has servers in India which run the bank feed technology that retrieves your transactions.

This system has been in place for years, and the alert reflects Kiwibank's recent proactive approach towards informing users about third-party bank feed solutions. Nothing has changed from our end, and we continue to focus on providing our customers with the most secure method of automatically aggregating account information

As an alternative to Bank Feeds, PocketSmith has an easy-to-use file import system which will accept exports from your bank without requiring your online banking credentials. You can learn more about importing bank files here: Bank files.

ANZ (New Zealand)

Most transactions made on the weekend will not be synced into PocketSmith until the following Tuesday due to restrictions at ANZ.

NZHL - New Zealand Home Loans (New Zealand)

Due to limitations on the NZHL bank feed, we are unable to provide the Available Balance of NZHL accounts in PocketSmith. The current balance options for NZHL accounts are:

  • Principal Balance: the amount left owing on the floating component of the loan
  • Original Loan Amount: the total loan amount

We are working with our bank feed provider, Yodlee, to have the Available Balance as an option for NZHL accounts, but in the meantime the best way to see the correct balance within PocketSmith is to use a 'Calculated closing balance'. This allows you to set a balance at a specific date; subsequent balances are calculated from this balance as transactions are imported.

Find out more about changing your balances here: Balance options.


Australian banks

Acorns (Australia)

The Acorns (Australia) feed will return a 414 no accounts found error if there are no statements available for the account. This is due to how the feed gathers the information, and we've see that new Acorns (Australia) feeds for new accounts will fail until the first statement is available. We've let Yodlee know about this odd behaviour for their team to investigate.

NAB (Australia)

If you are seeing a credential (402) error on your NAB (Australia) bank feed, a user has informed us that adding a leading zero before entering the username may solve the problem. They say that this was previously required for the mobile phone application and appears to work in these situations too.

The NAB (Australia) online banking occasionally generates duplicate transactions. NAB are aware of the issue and are working to resolve it. Please contact support if you need any help removing unexpected duplicates from your NAB accounts.

Commonwealth Bank CBA (Australia)

Transactions on CBA bank feeds are set to Pending status for at least three days before being moved into Posted status. Yodlee do this to avoid duplicate transactions on these feeds as CBA often changes transaction details in the first few days after a transaction is made.

We recommend having pending transactions turned on for CBA bank feeds.

BankWest (Australia)

BankWest feeds can sometimes import duplicate transactions due to an issue with the BankWest website. If you notice duplicate transactions on your Bankwest feeds, please contact PocketSmith support with either a screenshot or an exported transaction listing showing the correct transactions.

Coles MasterCard (Australia)

Coles MasterCard feeds can sometimes import duplicate transactions due to an issue with the Coles MasterCard website transactions display. Yodlee are aware of this issue but are not able to resolve it. If you notice duplicate transactions for Coles MasterCard bank feeds, you will need to remove the duplicated transactions manually in PocketSmith.

Police Bank (Australia)

The Police Bank website occasionally displays a CAPTCHA image ( Wikipedia) for security purposes. Since the CAPTCHA is only intermittently displayed, the bank feed is not able to handle this situation which means that if there is a CAPTCHA displayed when the bank feed attempts to connect then the connection will fail. Alternately, if there is no CAPTCHA displayed when the bank feed attempts to connect then the connection will succeed.

We are currently bound by the limitations of the bank feed in this instance. What this means is that Police Bank users will likely continue to have random Connection errors (403) on this bank feed for the foreseeable future. In the meantime, triggering a sync of the feed will - in most cases - resolve the error.

Citibank (Australia)

Citibank (Australia) feeds can sometimes import duplicate transactions due to an issue with the Citibank (Australia) website transactions display. Yodlee are aware of this issue but are not able to resolve it. If you notice duplicate transactions for Citibank (Australia) bank feeds, you will need to remove the duplicated transactions manually in PocketSmith.

ANZ (Australia)

Yodlee are not able to provide pending transactions for ANZ (Australia) on Credit Card type accounts due to restrictions at the bank.

Westpac (Australia)

Transactions on Westpac Australis bank feeds are set to Pending status for up to five days before being moved into Posted status. This is to avoid duplicate transactions on these feeds as the bank often changes transaction details in the first few days after a transaction is made.


USA banks

Wells Fargo (US)

US-based phone numbers
Some Wells Fargo accounts require a mobile phone number entered to receive a code by SMS. Wells Fargo will only accept US mobile phone numbers to receive this message. If you do not have a US mobile phone that can be used to receive this code, you'll need to switch to using bank files to import any accounts at this bank until Wells Fargo are able to support non-US phone numbers.

518 or 519 feed sync errors
We are actively working on a permanent solution for this issue, however, we have a workaround for you in the meantime. We've identified that there were some updates to how Wells Fargo's MFA (Multi-Factor Authentication) was sent to us that are no longer compatible with some of the structures we have in place.

To get around this, our bank feed provider, Yodlee have suggested a workaround, which has resolved the issue for some of our customers. The workaround is to try entering only the last 4 digits of your phone number into the MFA prompt, rather than the full phone number.

For example, if your registered phone number is XXX XXX 1234, please try entering only 1234 into the phone number field. You should then receive a second prompt for the security token to be filled.

Check out our Learn Centre documentation to find out more: Trigger a sync of a bank feed.

Capital One 360 (US)

You may need to enable third party access before you will be able to receive your transactions from the bank feed. To enable third party access, follow the steps below:

  1. Sign in to capitalone360.com with your Customer Number/Saver ID (Username) and PIN.
  2. Select the My Info tab.
  3. Go to Preferences and choose the Access Code section.
  4. Click on the Create Access Code button. An Access Code will be generated which you can use as your password along with your Customer Number/Saver ID (Username) as your username to sign in to the tool.

Once you have enabled third party access, return to PocketSmith and sync your Capital One 360 bank feed.

Additional instructions are available directly from Capital One 360.

Capital One (includes Capital One 360) does not support Pending transactions for any account types even when this feature is enabled on the bank feed.

Chase (US)

Yodlee are not able to provide pending transactions for Chase Bank due to restrictions at the bank.

This causes an issue with historical balances because the balance that is shown in PocketSmith will take into account the transactions which are pending - and not shown in PocketSmith.

As a workaround, you can change the balance settings to use a Calculated Closing Balance as described in this user guide: The balance options for an account. This will then base the current balance of the currently-imported transactions and not take into account the pending transactions that have not yet been imported.

Chase bank feeds are subject to stricter security restrictions than other bank feeds. For this reason, PocketSmith limits the number of possible attempts to enter credentials on the Chase bank feed to three attempts per week. After reaching this limit, you will be blocked from trying to enter your Chase credentials and will need to contact PocketSmith support to have this block removed.

Bank of America (US)

Yodlee are not able to provide pending transactions for Bank of America (BOA) due to restrictions at the bank.

This causes an issue with historical balances because the balance that is shown in PocketSmith will take into account the transactions which are pending - and not shown in PocketSmith.

As a workaround, you can change the balance settings to use a Calculated Closing Balance as described in this user guide: The balance options for an account. This will then base the current balance of the currently-imported transactions and not take into account the pending transactions that have not yet been imported.

American Express

Yodlee are not able to provide pending transactions for American Express (amex) due to restrictions at the bank.

This causes an issue with historical balances because the balance that is shown in PocketSmith will take into account the transactions which are pending - and not shown in PocketSmith.

As a workaround, you can change the balance settings to use a Calculated Closing Balance as described in this user guide: The balance options for an account. This will then base the current balance of the currently-imported transactions and not take into account the pending transactions that have not yet been imported.

Keybank (US)

You may need to enable third party access before you will be able to receive your transactions from the Keybank bank feed. To enable third party access, follow the steps below:

  1. Login to the bank site
  2. Click on Self-Service
  3. Click on Security Center
  4. Click on Third Party Access tab
  5. Click where it says Authorize Access

Once you have enabled third party access, return to PocketSmith and sync your Keybank bank feed.


UK banks

PSD2

From September 13, 2019 there will be an interruption to the bank feed service of any financial institution in the UK and/or EU region. This is because of new Open Banking requirements that will come into effect and stop these feeds from importing transactions.  

We're very disappointed to have to share this news with you, as we’ve explored every option available to keep your feeds going. This may well change in the near future as more information is still coming to light, however in the interim, it's best we prepare for the September 14 deadline. 

You can keep your accounts up-to-date by importing your bank transactions into PocketSmith. We're also working on making uploads quicker, more fun and motivating, as well as an FAQ and guides for how to transition to importing your bank files into PocketSmith. 

We're very much on this journey with our friends from the UK and EU, so trust that we're engaged as Open Banking comes into effect. 

If you’d like to learn more, please click through to read this post, and please don’t hesitate to contact us at [email protected] if you have any questions. 

We'll be in touch with more information soon!  

PayPal

Unfortunately due to the changes relating to PSD2 and Open Banking in the UK/EU, PayPal (UK) is no longer a bank feed that our bank feed provider, Yodlee can support.

The provider we have brought on in order to support UK/EU bank feeds, Salt Edge, is also unable to provide us access to a PayPal feed. This is down to the fact that PayPal is an international site and our agreement with them only applies to banks that are exclusively for UK/EU countries


Other banks

DBS (Singapore)

Due to changes in the MFA at DBS, Yodlee is now only able to support this site as a bank feed for accounts that make use of the Physical Token security option provided by DBS.

If you would like to use the DBS (Physical Token Only) (Singapore) bank feed, we recommend reaching out to DBS to let them know you no longer wish to use the  Digital Token. You can then select to use either SMS or a Physical Token for security. Please select the Physical Token, and you should then be able to sync this feed in your PocketSmith account.

PayPal

If you are not able to find PayPal when searching to add this bank feed connection, click the Show results from other countries link.

This will then show the results for PayPal in the United States. Selecting the US PayPal bank feed will also work with PayPal accounts outside the US.

PayPal feeds will produce duplicate transactions if both the PayPal Credit and PayPal Balance feeds are connected. Transactions on a Paypal Credit Card accounts also appear on the PayPal Balance accounts.

This is due to the how data is presented on the feed. Unfortunately the Yodlee isn't able to prevent these extra transactions from syncing at the moment.

MFA triggered after initial login

Yodlee have noticed that some sites have extra security which triggers MFA to be entered after the initial login. This is usually triggered when viewing the transaction page.
They are currently unable to support MFA being entered after the initial login so sites that have this may not be fully functional.
Bank feeds that we know have this issue are:
UOB (Singapore) - only balances sync, no transactions

Bank feeds affected by Google reCAPTCHA

Google reCAPTCHA is a security measure that some banks use for extra security. It is usually triggered when you log into your bank using the incognito tab or using a different computer.

Unfortunately, this particular security process blocks Yodlee from accessing the data required for bank feeds. This results in a 505 error on your bank feed and sometimes, if a work around isn't found, bank feed support is removed from that site.

If your Bank feed has had support removed because of the user of Google reCAPTCHA, we recommend contacting your bank directly to ask that they remove the use of reCAPTCHA or adjust it to allow Yodlee access.

Here are a list of bank feeds that no longer have support or are currently trying to find a work around for Google reCAPTCHA.

GLS Bank (Germany)
HSBC Bank (Australia) - support removed
HSBC Bank (Canada) - support removed       
HSBC Singapore (Singapore) - support removed
CareSuper (Australia) - support removed
Optum Bank - support removed
FairFX (UK) - support removed
HSBC (New Zealand)
Axis Mutual Fund (India) - support removed 
Travis CU - support removed
PayPal (Australia) - 50% affected
HSBC Credit Cards Online (Australia)
HSBC Bank Business Banking (Australia)


HSBC (Mexico) - Recently had reCAPTCHA removed and is now supported 

Bank feeds with upgraded MFA

We've identified that there were some updates to how MFA was sent to us that were no longer compatible with some of the structures we had 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 when this will be completed, but rest assured we’re working hard at it. 

Not all bank feeds from each bank are affected so it is sometimes possible to have a successful connection. 

Bank feeds that we know have this issue are:
USAA - all affected
City & Country CU - all affected, no longer available as a feed
Venmo - all affected, no longer available as a feed
California Coast CU - all affected
Barclays USA - majority affected
Goldman Sachs Bank - 50%
PurePoint Financial - all affected
ABN AMRO (Netherlands) - majority affected
Navy Federal CU - less than 50%
Bank of America - less than 50%
CIBC (Canada) - less than 50%
CIMB Bank (Malaysia) - all affected
Technology CU - all affected
Bank of Texas - all affected
Coastal Community Bank - all affected
ConnectYourCare - all affected
Ally Bank - all affected
Merrimack Valley FCU - 50%
Genisys CU - 50%
PayPal - less than 50%
Capital One (includes Capital One 360) - 50%
NASA FCU -  less than 50%
CP FCU - 50%
Deere Employees CU - less than 50%
University FCU - less than 50%

Sites that are actively blocking Yodlee's connection attempts.

United Nations FCU
Presidents Choice Financial Credit Card (Canada)

Sites that are actively blocking Yodlee's connection attempts at certain times.

Fidelity Investments - Yodlee have confirmed that the online banking site is blocking Yodlee refresh request IPs in peak hours of refreshes, due to US market volatility. The timestamp of blocking: 5:00 am and 8:00 am PST and 12:00 midday and 2:00 pm PST. Syncs outside of this timeframe are expected to be successful.


Vanguard Investments - Yodlee have confirmed that Vanguard blocks Yodlee IPs between 6 am and 1 pm PST, due to US market volatility, so unfortunately any sync triggered during that time frame is expected to fail. Syncs outside of this timeframe are expected to be successful.

Still need help? Contact Us Contact Us