Stripe Rolling Reserves, Fixed Reserves and Delayed Payouts

Operators use reserve for three different tools, then forecast cash as if they were one number. The forecast breaks. A rolling reserve, a fixed reserve and a payout delay can sit on the same account, and each one hits a different week.

Delayed payouts

The payout schedule is how long after a charge Stripe sends available funds to the bank. In many countries a mature, low-risk account is on a short business-day cycle. A new account, a risky fulfilment profile or a review can lengthen that cycle. Lengthening it does not confiscate the money. It moves the date. If your supplier is paid on the day of the sale, a longer cycle is still a funding crisis — it is just a dated one.

Schedules are country- and account-specific. Do not copy another merchant’s “T+2” into your model unless that is the schedule written on your account. Do not assume a review puts you on a particular day count. Read the payout settings and the banner.

Rolling reserves

A rolling reserve retains a slice of volume for a window that matches, roughly, the period in which a dispute is most likely. As each day’s hold expires, that portion can become available, while new charges add a new hold. In steady trading the reserve stabilises around a fraction of a few weeks’ sales. The cash you never see in the bank is that fraction. Growth makes the reserve grow, which means the incremental cash from new sales is smaller than the incremental sales. Businesses get surprised by their own growth curve here more than anywhere else.

If sales stop, the rolling reserve should unwind as each day ages out, subject to disputes and refunds hitting it on the way. “Subject to” is the whole risk. A quiet month that coincides with a backlog of undelivered orders is when the unwind does not happen.

Fixed reserves

A fixed reserve is a lump. Stripe may build it by withholding payouts until the lump is reached, or impose it against the current balance. It is blunt, and it is meant to be. It usually appears when Stripe wants a cushion that does not shrink just because this week’s volume dipped: a long fulfilment tail, a dispute problem that is not theoretical, or an account whose future is uncertain.

Ask, in writing on the account, what releases it. “When we feel comfortable” is not a date you can send to a lender. If no release condition is stated, your forecast should show the lump as held for the dispute window you actually have, not as cash due on Friday.

Reading the balance screen

• Pending or incoming: captured but not yet available under the schedule.
• Available: what could be paid out if payouts are enabled.
• Reserved: what has been removed from available on purpose.
• In transit: a payout that has left Stripe and not necessarily landed. A bank can still reject it.
• Negative: refunds and disputes exceeded what was there. This is a debt to deal with, not a display glitch.

If you are considering any partnership, print this breakdown into the conversation. A revenue share calculated on gross card volume, while a reserve and a dispute book sit on the only account that can fund them, is a share of the wrong number. Name who funds refunds when available is zero. Name who tops up a negative balance. Name what happens to the reserve if the relationship ends before it unwinds.