Citi Cards re-connection problem

NotACPA

I've recently needed to re-connect my Citi Cards Mastercard, and for several days now, I've gotten this error. "Try Again" only results in the same error. Any ideas?

I'm not typing the website address … Q is generating it for it's known PFI.

Sceptic

@NotACPA - I have never seen this error before so I asked Copilot and this is what it suggested for the 431 Header Too Large error. I am not sure any of these suggestions will resolve your error, but I think it's worth a try -

Fixes that work (ranked by effectiveness)

1. Clear Citi‑specific cookies in Edge

This is the fix confirmed by Quicken support and users.
Edge → Settings → Cookies and site permissions → Manage and delete cookies → Search for citi.com → Delete all Citi cookies.
Then retry the Quicken connection.

2. Try an InPrivate window

Edge → Ctrl+Shift+N → Let Quicken open the Citi login → complete OAuth.
This bypasses stored cookies entirely.

3. Temporarily change your default browser

Set Firefox or Chrome as default → run Quicken’s “Reset Account” or “Reauthorize” → complete Citi login.
Users report this works immediately.

4. Disable VPN or security software (if used)

Citi’s OAuth can reject requests with added headers from VPNs or filtering tools.
Quicken’s official troubleshooting also recommends disabling VPN/AV temporarily.

5. Sign out/in of Quicken ID

This resets Quicken’s cloud token and sometimes clears stale OAuth metadata.
Quicken recommends this for Citi connection failures.

If the error persists

Citi’s Open Banking/OAuth support team can check whether your Citi profile has corrupted OAuth tokens. Quicken recommends asking specifically for “Open Banking” or “OAuth Banking” support.

Bottom line

The error is not caused by Quicken itself. It’s a browser cookie/header overflow during Citi’s OAuth login. Clearing Citi cookies or switching browsers resolves it in nearly all cases.