You may have received an email or in-product message regarding some changes coming to your Chase accounts in Simplifi.
What is happening?
Chase is transitioning all accounts to a new connection method. From now on, you'll use a bank-hosted sign-in form to authorize downloads. The overall process for adding accounts and downloading is the same, but the screen you use to sign in to Chase will look different.
What does this mean for me?
When it is time to migrate your accounts to the new connection method, Simplifi will walk you through authorizing them under the new connection. You'll simply enter your Chase username and password, check the box next to each of your accounts, and then authorize the access. Ensure all your accounts are checked, even if they're already added to Simplifi.
Frequently Asked Questions
Learn the answers to frequently asked questions for this topic!
How will I know when it's time to migrate my accounts?
Simplifi will alert you via the Account List (lighting bolts) and through Settings > Accounts:
What does the new sign-in look like?
We're glad you asked. Under the new connection method, you'll be directed to a bank-hosted login page, similar to the one below:
Do I need to select ALL of my accounts in the authorization screen?
Yes, when prompted, please select all of our accounts in the Chase authorization screen, similar to the one below. You'll be able to ignore any accounts you don't want to add to Simplifi in the proceeding screen.
Please note: You're not required to select to include new, eligible accounts automatically to move forward with authorizing your accounts.
I'm an authorized user on a Chase account. Will I be able to add that account to Simplifi?
Chase is limiting download access to only the Primary user. Chase Authorized users may encounter an error while adding Chase or reactivating Chase accounts, which will appear in the authorization window. This is for security purposes to ensure the account owner(s) are allowing access to the bank data. Unfortunately, there is currently no workaround for this issue.