After almost 20 hours over the last 4 weeks spent trying to solve the Chase Bank Feeds issues created with the recent change to a "more secure transfer" method, I am rather fed up with both QuickBooks and Chase Bank.

QuickBooks Teams and other helpful sorts, please do not post any suggested fixes or solutions as I've been through them all including:

   1-creating a new company folder to test bank feed setups,

   2-adding user rights,

   3-deleting existing user bank feed rights,

   4-recreating existing user bank feed rights,

   5-creating new users with bank feed rights, 

   6-disconnecting bank feeds and reconnecting (multiple times),

   7-installing updates (multiple times) and

   8-upgrading from v22 to v23 (a "guaranteed fix" according to that QB support person).

I also don't want any sympathy or empathy.  I want lost features and functionalities restored.

I've spent more time training untrained Quickbooks' support folks and beta testing than I care to remember.  TO INTUIT:  I AM NOT A BETA TESTER and PLEASE, TRAIN YOUR SUPPORT FOLKS!

Yesterday and today, I have spent over 6 hours (yes, I can document this) with QB support and Chase support, only to have both organizations repeatedly point to the other as the problem!

Here my company is, stuck in the middle with no, repeat, no resolution to lost features.

Before this change, all was working wonderfully.  In fact, 3 years ago I moved our credit card business to Chase specifically due to bank feeds availability.  The problem arising from this recent change  is that now the only user that can download Chase Bank credit card data is the primary card holder, and in our case, this is the Admin account registration at Intuit...me.  I have staff that are assigned this responsibility and they have been granted access to Chase online so they can complete their work, yet they are unable to complete bank feeds!  What is "more secure" about this?

If QB cared about me as a customer, none of the problems should exist!