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; } } }

Automatically fallback to other online banking connectors (edited)

jade

The most core functionality of Simplifi is connecting to banks and getting up to date information. Yet these are brittle, so you have multiple provides that can provide these connections.

It's not really okay to have to delete and recreate all the connections all the time. I'd prefer a solution which has connections to both providers, and automatically falls back to the other when one gets flaky.

As an example:

https://community.simplifimoney.com/discussion/comment/38786#Comment_38786

This is better than nothing, but it's really not a solution. Making me have to go through all this work all the time is just a pain, makes me dislike the product.

Find more posts tagged with

Already Offered

Online Banking

Feature Request

Status: Already Offered

Comments

Coach Natalie

@jade, thanks for posting your request to the Community!

To clarify, with the additional aggregators of Finicity and Plaid (Intuit being our primary aggregator), Quicken Simplifi is already designed to default to the working option if one is failing or having issues. In the case of Fidelity, we had to get the new Fidelity Akoya option added by Finicity so we could offer it as a workaround to users. The Finicity connection wasn't there prior for Quicken Simplifi to default to when Intuit started having issues.

Let me know if you have any questions!

-Coach Natalie

jade

You can sign up with either aggregator to these services. But you don't sign up with both of the aggregators, so when you sign up, you don't have a real operational backup.

Imagine a solution where you actually go through the login flow twice. But…. if one of the aggregators stops working, it's fine.

That's what I was proposing.

RobWilk

Part of the problem with that idea (which in theory is good), is that one connector may require you store the password/username in their servers, while another connector may use somethingl ike OAuth where you sign in at the bank and the credentials aren't stored in the connector instead like a token is.

This "could" work if you authenticated with all the related connectors up front when you set it up, individually, and then if one failed it could (in theory) fall back to another.

-Rob

Coach Natalie

@jade, that's what's supposed to happen — when one aggregator fails, one of the other aggregators can automatically be used as a backup. Or, in the case of Fidelity, our engineering team can add a bank option for one of the other aggregators if one doesn't already exist and it's needed.

I hope this helps clarify!

-Coach Natalie