TL;DR: Stripe Connect Not Working — most cases trace to a config mismatch, a hidden assumption, or a step skipped during setup. The fix path below covers the high-percentage causes first. If you're still stuck after 10 minutes, text PJ — most issues answered in one reply. 858-461-8054.
Operator Problem Guide
Stripe Connect Not Working
Stripe Connect stops working in 2026 most often due to one of four issues: your connected account is in restricted mode (not fully onboarded), you are using the wrong API key scope (platform key vs. connected account key), the OAuth flow was not completed correctly, or your account is in a region where a specific Stripe product is not available.
Why This Happens
Configuration gaps between tools or services
Missing integrations or manual workarounds that weren't designed to scale
Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
Verify your current setup matches the vendor's latest documentation
Look for recent changes — platform updates, new team members, configuration drift
Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
The problem is costing you money or customers per week
You've spent more than 2 hours on it without progress
A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
Check first: go to your Stripe Dashboard → Connect → Accounts and find the specific account. If the status shows "Restricted" or "Incomplete," the account holder needs to complete identity verification. If the error is in your API calls, confirm you are passing the Stripe-Account header with the connected account ID on every request that should act on behalf of that account — missing this header is the most common cause of permission errors.
