Stripe Bond Holds Explained for Rental Businesses (And Why They Expire)

Manual capture vs immediate capture

When you create a payment intent or payment method, you choose: capture immediately or capture later. For bonds and security holds, you almost always want manual capture.

• Immediate capture — Funds are taken right away. Good for final rental payment. Not suitable for bonds.
• Manual capture — Funds are reserved but not taken. You capture when you need to (e.g. for damage) or release when the hire ends cleanly.

With manual capture, the customer sees a pending hold. You keep the option to capture or release until the authorisation expires — which is where the problem starts.

Why authorisations expire (the practical impact)

Card networks (Visa, Mastercard) set limits on how long an authorisation can remain open. Typically, that is around 7 days for many cards. Some issuers allow extensions; others do not. Stripe does not control this — it is a network rule.

For a 3-day rental, a 7-day hold is fine. For a 2-week campervan hire, the hold will expire before the customer returns. If you discover damage at return, you can no longer capture the original authorisation. You must create a new charge.

That new charge posts days (or weeks) after the hire. The customer may not recognise it. They may dispute it. Your dispute win rate drops because the charge looks disconnected from the rental. See our guide on Stripe chargebacks for rental businesses for why this matters.

What happens when a hold expires

When the authorisation expires:

• ✕ You cannot capture it. The PaymentIntent or authorisation is no longer valid.
• ✕ The pending amount disappears from the customer's statement.
• → To charge for damage, you must create a new payment. That charge is more likely to be disputed.

The solution is to refresh the hold before it expires — place a new authorisation that extends the reservation. For rentals longer than 7 days, you need a process (manual or automated) to refresh on a schedule.

When to capture vs hold (rental scenarios)

Use a hold when:

• ✓ Taking a bond or security deposit at pickup
• ✓ You may need to charge for damage, cleaning, or other post-hire fees
• ✓ The rental is longer than a few days (refresh the hold as needed)

Use immediate capture when:

• ✓ Collecting the final rental payment (hire fee)
• ✓ You have identified a charge and the customer has acknowledged it (capture from the hold)

How to avoid expired holds (manual process + automation)

Manual process: Track rental end dates. For rentals longer than 5–6 days, schedule a reminder to refresh the hold before day 7. Create a new authorisation (or use Stripe's incremental authorisation if supported for your use case) and release the old one. This is error-prone and easy to forget.

Automation: Use a system that knows your rental dates and automatically refreshes holds until the hire ends. No manual tracking, no missed refreshes. Parked Funds does this: we sit alongside your booking system, create Stripe-native holds, and refresh them until return.

Either way, the goal is the same: keep a valid authorisation available so that when you need to capture for damage or other post-hire charges, you are capturing from the original flow — not creating a new charge that looks like an unauthorised transaction.