Managing multiple Stripe security deposits becomes easier when the payment state lives in a deposit dashboard and your booking record names the person responsible for the next decision. Use PayRequest for the hosted authorization link and capture/release workflow; keep rental availability, inspections and liability decisions in your existing operation.
This guide is for short-term rental operators who already understand card holds but are tired of reconciling a spreadsheet with Stripe. It is not a tenancy-deposit protection system or a promise that every card hold lasts 30 days.
What should a multiple-deposit work queue contain?
One row should connect a booking reference to one specific deposit. Record the authorization status, actual provider deadline, return time, inspection status and decision owner. A copied amount or green spreadsheet cell does not establish that funds are still reserved.
Use this fictional morning queue as an operating template. Times are illustrative; they are not standard authorization windows.
| Booking | Confirmed deposit state | Operational question | Next decision |
|---|---|---|---|
| Camera A | Authorized; deadline tomorrow 12:00 | Returned, inspection complete, no supported charge | Owner reviews and releases |
| Studio B | Pending | Customer has not completed authorization | Follow up before key handover |
| Speaker C | Authorized; deadline today 16:00 | Returned, documented €45 accessory cost | Review the complete claim before one final capture |
PayRequest's dashboard distinguishes waiting for the customer, processing an authorization and funds reserved. The API reference explains how these labels relate to payment states. Keep the owner and inspection task in your booking or operations record; this worksheet does not assert a built-in assignment feature.
Replace duplicate payment-state entry first
Start with new bookings rather than copying every historical spreadsheet row into a live request. For each new booking, create a deposit link, save its reference and confirm the returned status before relying on the hold. Continue using your existing inspection and inventory records.
For older rows, retrieve the real payment state before taking action. A past captured payment needs its own refund or claim review; it must not be recreated as a fresh authorization just to make the spreadsheet look tidy. Retain the historical trail separately.
Stripe's hold documentation requires capture before the actual authorization expiry. Set your review process around that timestamp and an inspection buffer. Moving a rental return date in a calendar does not move the bank deadline.
Why should settlement have one decision owner?
Two employees can both believe the other has settled a booking. Give each return a named decision owner and a review time in your operational record. Before capture or release, that person checks the current deposit, the complete inspection and the amount to charge.
In PayRequest's documented Stripe flow, one final capture ends the authorization. For €500 authorized and €45 captured, €455 is released and cannot fund a later second capture. Read the partial-capture guide before treating each discovered cost as a separate payment action.
Check peak concurrency before choosing a plan
Monthly creation volume and simultaneous active holds are different limits. Four weekend hires can need four active deposits even when you only start four requests that month. PayRequest Free currently allows three new deposits per month and one active at a time. Check the paid allowance in your dashboard and current pricing before moving a busy queue.
Keep rental fees separate through payment links. A paid hire charge does not prove that the damage hold is authorized. The two-record Stripe workflow shows that distinction with a concrete example.
Start with PayRequest security deposits: connect your eligible Stripe account, prepare one booking and rehearse authorization, deadline review and final release or capture. Expand when your team can explain every row in the queue without manually guessing its financial state.
Editorial note: AI assisted with the text and illustrative cover. Public PayRequest and Stripe documentation was reviewed on 13 October 2026. The queue is an original fictional template; no customer results or live financial tests are claimed.
