You wake up to find $4,800 of this month’s course sales sitting in a “reserved balance” instead of your bank account. Stripe didn’t warn you. The dashboard shows the money as “pending” with a 30-day hold. Your rent is due in six days.
Payment processor reserves aren’t rare. They’re automatic risk controls that lock a percentage of your revenue when transaction patterns change. For solo operators running subscription businesses, they can freeze 10–30% of incoming payments for weeks—sometimes longer.
How reserves work and when they trigger
Stripe, PayPal, and most payment processors use rolling reserves or fixed-percentage holds to cover potential chargebacks and refunds. The system monitors your account for pattern changes: a sudden revenue spike, a new product launch, a shift from one-time to recurring billing, or an uptick in dispute rates.
When a reserve triggers, the processor withholds a percentage of each transaction. That money sits in a segregated balance. After a set period—typically 30 to 90 days—the funds release on a rolling basis. If you process $10,000 in Week 1 with a 20% reserve, you’ll receive $8,000 immediately. The remaining $2,000 releases 30 days later, assuming no disputes.
Reserves don’t require your approval. They’re written into the merchant agreement. Stripe’s terms allow them to impose or adjust reserves at any time based on “risk assessment.” PayPal’s policy is nearly identical.
Common triggers include:
- Revenue increasing 200% or more month-over-month
- Launching a high-ticket product (above $500) for the first time
- Switching from physical goods to digital products or services
- Chargeback rates exceeding 0.5% of transaction volume
- Customer complaints or refund requests spiking above historical norms
What percentage gets held and for how long
Standard rolling reserves range from 10% to 30% of transaction volume, held for 30 to 120 days. Stripe’s default is 20% for 90 days when risk signals appear. PayPal’s can go as high as 30% for 180 days if your account is flagged for elevated dispute activity.
Fixed reserves are rarer but more severe. Instead of a percentage, the processor holds a flat dollar amount—say, $15,000—until they determine risk has subsided. This typically happens after multiple chargebacks on high-value transactions or if your business model changes dramatically (e.g., pivoting from consulting to software subscriptions).
Reserves aren’t interest-bearing. You don’t earn anything while the money sits. If your effective cost of capital is 8% annually, a $10,000 reserve held for 90 days costs you roughly $200 in opportunity cost—not counting cash-flow disruption.
How to check if a reserve is active
In Stripe, go to Balance → Overview. If a reserve is active, you’ll see a “Reserved funds” line with the held amount and release schedule. Click through for transaction-level detail showing which payments are affected.
PayPal buries it deeper: log in to Business Account → Reports → Reserved Funds. The interface shows pending releases by date, but won’t always explain why the reserve was imposed. You’ll need to contact support for specifics.
If you’re using Stripe Connect to process payments on behalf of sellers (e.g., a marketplace or platform business), reserves can cascade. Stripe may hold funds at the platform level and at the connected-account level, compounding cash-flow strain.
What you can do when a reserve hits
Contact processor support immediately. Explain your business model, provide transaction history, and ask for reserve terms in writing. If you can demonstrate stable operations—low refund rates, no dispute history, predictable revenue—you may negotiate a lower percentage or shorter hold period.
Provide documentation: churn reports, customer testimonials, refund policies, delivery confirmations. Processors care about risk mitigation. Evidence that you run a clean operation can reduce or lift a reserve within 5–10 business days.
If you’re launching a new offer or expect a revenue spike, email your processor before it happens. Proactive communication rarely prevents reserves, but it establishes context. When the algorithm flags your account, a support agent reviewing the case will see your heads-up and may approve a lighter hold.
Diversify payment rails. Run Stripe for subscriptions and PayPal for one-time course sales, or vice versa. If one processor imposes a reserve, the other remains unaffected. This doesn’t eliminate risk, but it reduces single-point-of-failure exposure.
Track reserve release schedules in your cash-flow forecast. Don’t budget reserved funds as liquid. They’re not available until the hold expires. If you’re running tight margins, a 20% reserve on $50,000 monthly revenue means planning around $40,000 actual receipts.
One non-obvious detail: Reserves don’t automatically lift when the hold period ends. Stripe and PayPal release funds on a rolling basis, but the reserve itself may stay active indefinitely if risk signals persist. You might receive October’s held funds in December, but November’s transactions are still subject to the same 20% hold. Always confirm whether the reserve is temporary or ongoing.
If cash flow is critical and a reserve would sink your operations, consider underwriting your own risk. Set aside 15–20% of monthly revenue in a separate account as a self-imposed buffer. It’s not ideal, but it beats scrambling when a processor locks your funds without warning.
Running into payment processor issues? Reply and tell me what happened—I’ll cover operator-reported problems in a future piece.
