Personal Capital not able to acess Discover accounts

1. What’s actually failing: Discover “bank” connections, not necessarily all Discover products

The documented problem is specific: Personal Capital has temporarily disabled the ability to add Discover Bank accounts at Discover’s request while the two firms resolve the error, and Personal Capital’s help content explicitly states the Discover Bank add flow was disabled as of November 15 with no ETA to re-enable it ^[1]. Community reports make a distinction between Discover credit card (which in some workflows moved to Capital One) and Discover bank checking/savings connections that remain broken for many aggregation tools ^{[3] [6]}.

2. Why this is happening: a mix of institutional requests and a platform migration

Public-facing support text ties the immediate cause to Discover’s request rather than an unexplained Personal Capital outage — the disablement was done “at the request of Discover Bank” while teams work on a fix ^[1]. User threads and third‑party writeups link the disruption to Discover’s broader migration/merger activity with Capital One, which has changed authorization endpoints and left some aggregators unable to authenticate or map banking vs card endpoints correctly ^{[3] [6] [7]}.

3. How it shows up for users: missing transactions, disappearing history, and failed reauthorizations

Forums and user reports describe multiple symptoms: transactions that appear while pending then vanish when posted, entire transaction histories truncating, and persistent failures to reauthorize logins or add accounts — issues seen across card and banking products and cited repeatedly since 2024 into 2026 ^{[2] [8] [5]}. Third‑party troubleshooting guides likewise note users getting temporary disables for Discover and inconsistent aggregates after institutional security or API changes ^[7].

4. What Personal Capital/Empower officially documents and what other trackers show

Personal Capital’s Known Issues and Account Linking pages list a variety of connection problems and troubleshooting guidance, and the company’s support articles reflect known incompatibilities with particular institutions and multifactor methods — but the Discover disablement is singled out as an action taken at Discover’s request with no ETA ^{[9] [10] [11] [1]}. Real‑time outage trackers like Downdetector show no consistent platform‑wide outage for Personal Capital that would explain every user complaint, suggesting targeted institution-level issues rather than an aggregator outage ^[4].

5. Practical next steps for affected users

Users should first check Personal Capital’s Known Issues and Account Linking pages for updates and follow any guidance to remove and reconnect accounts, understanding Discover may still block new add attempts ^{[9] [10]}. If credit card activity moved to Capital One endpoints, reauthorizing via Capital One flows can restore card syncing in some tools; banking accounts tied to Discover Bank remain more brittle and may require waiting for the institutional fix ^{[3] [6]}. Backfill important transaction history by downloading CSVs from Discover/Capital One and import or manually reconcile if Personal Capital’s history is truncated — support articles recommend contacting support for incorrect balances but do not guarantee a timeline for discovery fixes ^{[1] [12]}.

6. Limits of reporting and what to watch for next

Available sources document the disablement and widespread user friction but do not provide a firm timeline or technical post‑mortem explaining whether the issue is API mapping, MFA incompatibility, or the Capital One migration’s backend routing; Personal Capital’s public guidance only promises updates when available ^[1]. Observers should monitor Personal Capital Known Issues pages and community forums for reauthorization success stories and check whether the Capital One/Discover migration completes and restores bank‑side connectivity ^{[9] [3]}.