Stripe reserves and delayed payouts, explained

Stripe holds funds in a handful of distinct situations: a new account's delayed payout schedule, a reserve imposed under the Stripe Services Agreement, disputed charges waiting for the card-network cycle, and account suspensions. Each has a different fix, and treating them the same is why most support threads go nowhere.

The Stripe Services Agreement defines a "Reserve" as collateral funds Stripe holds and controls to satisfy current or potential liabilities — including amounts described in a Reserve Notice or shown in the Dashboard. Separately, Stripe's Connect documentation states that platform-created reserves cannot run longer than 180 days per cycle, which is why 90–180 day reserves are the community-standard pattern for platform businesses.

What actually moves a Stripe hold

First, get the classification in writing: payout-schedule delay, risk reserve, dispute pin, or suspension. T1 of the escalation pack does exactly this — it demands the specific contractual basis, the reason, and the timeline. Second, supply the evidence that decision-makers actually use: delivery proof, dispute-rate trend, and a source-of-funds narrative. Third, put the process on a schedule — 7 days for support, then compliance, then a formal demand, then the regulator route (for US accounts, the CFPB complaint portal covers money services).

⚠ Verify current terms at stripe.com/legal and the CFPB process at consumerfinance.gov/complaint before relying on any timeline. Figures above are community/industry-reported patterns, not guarantees. Not legal advice.