Stripe Reserve

Hold, plan, release: what Stripe actually creates

Underneath the dashboard language there are three objects, and knowing them makes every line on your balance report readable.

A **hold** reserves a single amount that releases on a specified date. A **plan** automatically creates a hold for a percentage of each charge. A **release** represents funds coming back out of the reserve, and Stripe creates one automatically when a hold reaches its scheduled release date or when the held funds get used for a refund or dispute.

The part worth internalising is that each of these moves money between two different balances, and generates two balance transactions rather than one. Creating a hold produces a `reserved_funds` entry debiting the payments balance and a `reserve_hold` entry crediting the `risk_reserved` balance. Releasing produces the mirror image: a `reserve_release` debiting `risk_reserved` and a `reserved_funds` crediting the payments balance back.

That is the mechanical reason a reserve behaves like money leaving and later returning. Nothing left Stripe. It moved sideways into a balance that payouts cannot reach, and moved back when the hold matured.

Fixed and rolling

Stripe uses two kinds of reserve, and the difference is entirely about when the money comes back.

A **fixed** reserve releases on a specified date. It suits a known, dated risk: a large order with a long delivery time, or ticket sales for an event that might be cancelled, where the sensible release point is the day after the event.

A **rolling** reserve releases a set number of days after the associated charge. Because each charge starts its own clock, the effect is a continuously replenishing buffer rather than a single lump that ends. Stripe describes rolling plans as the tool for "automated management of ongoing risk", and notes that a standard reserve window also sets consistent expectations about payouts.

There is a hard ceiling on both. Funds cannot be reserved for longer than 180 days, and the scheduled release date of a hold "can never be more than 180 days after its creation date, regardless of how it was created."

Most businesses never configure any of this. Reserves on your own account are set by Stripe based on risk factors such as your industry, your dispute rate, and unexplained spikes in volume. Reserves are usually temporary, though Stripe acknowledges that "in some rare cases, a reserve may be required indefinitely."

When a hold actually releases

A hold releases automatically when any one of three things happens: its scheduled release date arrives, 180 days pass since it was created, or a refund or dispute occurs on the associated transaction for an amount equal to or greater than the hold.

When the reserve term completes, Stripe pays out what is left. Its wording is worth reading closely, because it explains why a release is often smaller than the hold: funds "will be paid out once the reserve term is complete (minus any customer refunds or disputes that may have been covered by the reserve)." The reserve did its job, and what it absorbed does not come back.

One behaviour surprises people, and it is documented. A refund or dispute for **less** than the hold amount does not release the hold. The refunded or disputed amount comes out of the account balance instead, which can push that balance negative while the full hold sits untouched. If that happens and you would rather not wait for the scheduled date, the hold has to be released manually.

The other reserve with the same name

If you run a Stripe Connect platform, "reserve" means something related but structurally different, and mixing the two up makes balance reports impossible to read.

When a connected account’s balance goes negative and your platform is responsible for covering it, Stripe holds a reserve against your platform’s available balance. Those holds and releases appear as balance transactions of type `reserve_transaction`, and the platform balance they sit in is called `connect_reserved`. As the connected account’s balance recovers through new activity, a corresponding portion of your reserve is released.

Two details matter for reconciliation. Stripe keeps the platform reserve for an extra three business days after a bank withdrawal covering the negative balance posts, so the reserve outlives the event that caused it. And if a connected account stays negative for 180 days, the hold stops being a hold: Stripe transfers part of your balance to zero out that account through a `connect_collection_transfer`, which is a permanent movement of your money and a real loss to book, not a timing difference.

You can end a reserve early by sending a transfer to the connected account to clear its negative balance.