nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Human Interest Listed as Supported, But Human Interest Says Third-Party Integrations Are Not-FDP-155

rodneymallari

I’m posting this to document an issue I’ve been trying to resolve with Human Interest and Quicken Simplifi.

For several weeks, I’ve been unable to connect my Human Interest 401(k) account in Simplifi. The error I consistently receive is:

“We are unable to connect to Human Interest at this time. Care Code: FDP-155.”

Troubleshooting already completed:

Updated/retried the connection multiple times
Deactivated and re-added the account
Re-entered credentials
Confirmed I can log in directly at Human Interest
Removed MFA from my Human Interest account to rule that out

I contacted Simplifi support multiple times. Support confirmed that Simplifi uses Intuit as the data aggregator and that the failure occurs during the authentication/handshake phase, where the connection is being blocked by the financial institution .

Based on Simplifi’s guidance, I contacted Human Interest directly.

Here’s the key point:
Human Interest confirmed that they do not support third-party financial integrations (including Intuit/Quicken), and that this is a platform-level limitation — not an account-specific issue.

They also document this publicly here:
https://support.humaninterest.com/s/article/Can-I-integrate-my-Human-Interest-account-with-external-financial-software

The core issue

Human Interest is still listed as a connectable institution in Simplifi, but Human Interest states that third-party integrations are not supported.

Support’s current response has been:

The bank is blocking the connection
There is no escalation path
Manual CSV import is the only option
The institution remains listed because some accounts may still work

From a user perspective, that does not resolve the issue.

If Human Interest does not support third-party integrations at a platform level, then listing it as a supported/connectable institution is misleading and results in unnecessary troubleshooting.

Questions for the Simplifi team

Is Human Interest officially supported in Simplifi today?
If Human Interest does not support third-party integrations, why is it still listed as connectable?
If only some legacy or partial connections work, can that be clearly communicated?
Can this be reviewed by the product/integrations team rather than treated as an individual support issue?
Should this institution be removed or clearly marked as unsupported if new connections are not functional?

I understand Simplifi cannot force Human Interest to allow aggregator access.

However, this is no longer just a connection issue — it’s a product accuracy issue. The platform is presenting an institution as connectable while the institution itself states it does not support integrations.

At minimum, users should not have to spend weeks troubleshooting something that may not be supported in the first place.

Find more posts tagged with

Online Banking

Comments

Coach Jon

Hello @rodneymallari,

Thanks for reaching out! I can see the support ticket you worked on with our chat support team. Although we usually don't recommend contacting your bank directly about connectivity problems, FDP-155 errors are one of the rare cases where we do suggest reaching out to them. This error will appear when the financial institution blocks access to its servers, preventing Quicken Simplifi from retrieving data to download to your file.

We cannot speak for Human Interest, so we would not know why they would state that third-party integrations are not supported, unfortunately.

With that said, I can see the FDP-155 error from my side as well. So this issue is not just specific to you. I wish I had a better answer for you, but unfortunately, this is something we cannot fix on our end, so I would still suggest contacting the financial institution in this case.

rodneymallari

Thanks for the response @Coach Jon, but I think the core issue is still being missed.

I understand that FDP-155 means the financial institution is blocking the connection and that Simplifi cannot force Human Interest to allow third-party aggregation access. At this point, that part is clear.

The bigger issue is this:

Why is Human Interest still listed as a supported/connectable institution in Simplifi if Human Interest itself states that third-party integrations are not supported?

That’s what led to weeks of troubleshooting, multiple support tickets, and repeated escalation attempts where I was continually told that escalation was “not possible.”

This is no longer just a connectivity issue — it’s a product accuracy issue.

To be transparent, I escalated this directly to Quicken leadership because support kept repeating the same connection explanation without addressing the actual concern. Eric Dunn (CEO of Quicken) replied and stated:

“You present a clear case for removing Human Interest from our list of supported financial institutions.”

He also looped in Ian Schiffer, the product manager for financial institution connectivity, to review the issue further.

So respectfully, the concern here is not whether Human Interest is blocking the connection. We already know they are.

The concern is why the institution continues to appear as supported/connectable despite Human Interest’s documented stance against external integrations, and why support repeatedly stated escalation was not possible instead of routing this as a product/institution-listing issue.

That’s the part I’m hoping gets properly reviewed.

AtlantaFoodie

I actually appreciate this thread, because I'm one of the ones who had posted with my issues. Glad to know I'm not crazy, but disappointed that Simplifi seems to be bungling the issue and missing the complaint (still). Just be accurate, folks!

Coach Jon

Hello @rodneymallari,

I appreciate the information! We would not have insight into why a financial institution shows in Quicken Simplifi. Our engineering team determines when financial institutions are removed. If they decide that a financial institution needs to be removed at any time, they will take action accordingly.

Thank you!

rodneymallari

Update: I received a response from Ian Schiffer, Product Manager for Financial Institution Connectivity at Quicken.

He confirmed that Human Interest previously allowed aggregation connections but no longer does, and that Quicken will be removing the institution from the supported/connectable list.

This ultimately confirms the core issue I was raising throughout this thread: the problem was not just an individual FDP-155 connection failure, but that Human Interest was still being presented as a supported institution despite no longer supporting third-party aggregation.

That said, I do think the support/escalation process around issues like this needs improvement. Throughout this process, I repeatedly received the same “contact the bank” response and was told escalation was not possible, even after it became clear this was a broader product/institution-listing issue rather than an individual account problem.

Hopefully clearer institution status reviews and better escalation paths can help prevent users from spending weeks troubleshooting unsupported integrations and getting stuck in support loops going forward.

rodneymallari

Thanks @Coach Jon, but this is exactly the kind of response pattern I’m referring to.

I understand that frontline support may not control institution listings directly. The issue is that throughout this process, support repeatedly treated this strictly as a user/bank connectivity problem and continued shutting down escalation attempts, even after it became clear this was a broader product/institution-listing issue.

At this point, Quicken leadership and Ian Schiffer (Product Manager for Financial Institution Connectivity) have already confirmed that Human Interest no longer supports aggregation and that the institution will be removed from the supported/connectable list.

So while support may not own the listing itself, support absolutely plays a role in recognizing when an issue should be routed beyond standard troubleshooting instead of repeatedly redirecting customers back to the bank.

That escalation gap is the real feedback I’m trying to communicate here.

Coach Jon

Hello @rodneymallari,

Thank you for sharing your feedback. We truly value your insights and have passed along your concerns listed here to our team for further consideration.