Why do I get an "internal error" connecting Chase via Plaid, and how do I upload a Chase statement instead?

The Chase "internal error" in Plaid is almost always a Chase-side setting, not an ExpenseBot bug. Plaid attempts the connection but Chase never hands back a valid token — usually because Third-Party Access is disabled on the Chase account.

Fix for 95% of users:

1. Sign into chase.com in a browser (not the Chase mobile app)
2. Go to Profile & Settings → Security → Account Access
3. Make sure "Third-Party Access" is ENABLED for the accounts you want to connect
4. Sign out of Chase everywhere, then clear Chase cookies:
   • Chrome/Edge: Settings → Privacy and security → Cookies → See all site data → search "chase" → delete all Chase entries
   • Safari: Settings → Privacy → Manage Website Data → search "chase" → Remove
   • Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → search "chase" → Remove Selected
5. Come back to ExpenseBot, open the reconciliation modal, and try Chase again

If Chase still fails after that, skip Plaid entirely and use the direct upload instead.

Uploading a Chase statement directly (no Plaid needed):

1. Go to expensebot.ai and sign in
2. Click the "My Reports" tab
3. Under the "View my spreadsheet" button, click "Spreadsheet tools"
4. Click "Match Receipts to Card"

In the reconciliation modal, below any Plaid-connected cards, you'll see a gray bar:

⬆ Upload a statement — PDF, CSV, OFX, QFX accepted

Click it, pick your Chase statement PDF (or CSV export from Chase's site), and ExpenseBot will parse it, cross-check it against your scanned receipts, and flag any missing ones. Same reconciliation result — no Plaid required.