HTTP 400 with Capital One Credit Card
I am receiving an HTTP 400 error when I try to connect my Captial One credit card account.
Captial One reports that everything is approved. Somehow, the authorization token fails to make it back to Quicken.
I am using Quicken Classic for Windows. I am also using Windows 11 and Microsoft Edge.
From my Captial One Account:
What is show in my browser (and why I am guessing this is a Quicken issue):
Answers
-
Hi @FrMoore,
Thanks for reporting this! I just tested with my own Capital One on my end and wasn’t able to reproduce the HTTP 400 error. Since you mentioned the authorization token isn’t making it back to Quicken, it’s possible something on your system is interfering with that handoff.
Can you let us know if you have a firewall, antivirus, VPN, or pop-up blocker enabled? If so, please try temporarily disabling those to see if the connection works. Sometimes these can interrupt the secure redirect during the sign-in process.
Let us know what you find—we’ll go from there.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0
Categories
- All Categories
- 56 Product Ideas
- 36 Announcements
- 225 Alerts, Online Banking & Known Product Issues
- 22 Product Alerts
- 702 Welcome to the Community!
- 671 Before you Buy
- 1.2K Product Ideas
- 53.7K Quicken Classic for Windows
- 16.3K Quicken Classic for Mac
- 1K Quicken Mobile
- 812 Quicken on the Web
- 111 Quicken LifeHub


