Pre-authorization deposit software lets a rental business reserve an amount on a customer's eligible card, then release it or capture a justified charge before the authorization expires. Choose software by your complete rental-and-inspection horizon, not a headline promise of seven or thirty days.
This guide is for equipment hire, short-stay rental and venue operators buying a remote damage-deposit workflow. Rental payment, booking prepayment and refundable damage security serve different purposes. Explain each separately to the customer and choose a collection model that fits your actual operation.
Compare deposit software with your rental operation
| Option | Best reason to evaluate it | Question that determines fit |
|---|---|---|
| Booqable | Rental bookings, orders, inventory and payment handling together | Does its supported pre-authorization flow cover your return and inspection timing? |
| Holdyy | A focused remote card-deposit request | Which providers, authorization windows and capture rules apply to your account? |
| Swikly | A specialist deposit service with a different security model | How do its contractual collection, duration and claim terms differ from a card hold? |
| PayRequest | Deposit links alongside invoicing and client payments | Does the actual provider expiry cover the rental and your final decision? |
| Direct provider dashboard or custom integration | You already have the skills and operating process | Who owns customer communication, deadlines, capture and reconciliation? |
Booqable describes rental pre-authorizations and payment requests. Holdyy offers remote deposits. Swikly describes a service that does not affect the customer's card limit and can cover longer periods; do not label that an ordinary reserved-funds card hold. Verify its exact contract and eligibility before treating the models as interchangeable.
This is a buying framework based on public sources, not an installed-product ranking. If you need inventory availability, contracts and a rental calendar, compare the complete rental platform. A deposit-link tool can complement your existing process but does not automatically supply those functions.
Hold, charge-and-refund, or specialist service?
| Model | What happens to the money | Main operating constraint |
|---|---|---|
| Card pre-authorization | Eligible funds are reserved until capture, release or expiry | Decision must fit the actual authorization window |
| Charged refundable deposit | Customer pays; a later refund returns the refundable amount | Refund timing, provider costs and local deposit rules |
| Specialist deposit or protection service | Depends on its contract, collection mechanism and risk model | Confirm claim terms and whether it is a deposit, waiver or insurance |
A hold reduces available credit or funds, so avoid describing it as having no impact on the customer. Releasing an uncaptured hold is different from refunding a completed charge. The customer's bank controls when the statement or available balance reflects the change.
Local rental and consumer rules can affect deposits, deductions and refunds. This workflow comparison does not establish a legal right to collect any amount or replace a required tenancy-deposit scheme.
Use the actual expiry, not the card logo
Stripe's current authorization documentation lists standard online customer-initiated card windows of seven days for the major listed networks. Other transaction types can be shorter. Its extended-authorization documentation describes longer windows only for eligible transactions and accounts. Neither seven nor thirty days is a universal software guarantee.
The usable deadline is the expiry recorded for the specific successful authorization. Provider rules differ; do not apply a Stripe card window to Mollie or PayPal by analogy. A sent link is not reserved funds. You need a successful customer authorization before treating the deposit as secured.
Calculate the rental-to-decision horizon
The following original worksheet is a hypothetical equipment-rental example. It is reproducible arithmetic, not a hold we created or a customer case study.
| Time segment | Assumed hours |
|---|---|
| Authorization before pickup | 24 |
| Rental period | 72 |
| Return-to-inspection and final decision | 24 |
| Operational buffer | 12 |
| Required horizon | 132 |
Required horizon = advance authorization + rental duration + inspection/decision time + buffer. Here, 132 hours is five days and twelve hours. If an actual authorization offers 168 usable hours, the example has 36 hours of headroom. If it offers 120 hours, the example exceeds the window by 12 hours. Those are assumed windows, not promises about a particular card.
Now change the rental from 72 to 192 hours: 24 + 192 + 24 + 12 = 252 hours, or ten days and twelve hours. A seven-day window cannot cover it. Before accepting that booking, confirm an eligible longer authorization or choose an appropriate charged/refundable or specialist model. Do not collect a short hold and assume it can simply be extended at return.
The worksheet answers an operator's buying question: can this collection product cover the period during which a decision is actually possible? It does not mean you should charge an otherwise refundable deposit solely to beat an expiry.
Check partial capture and the final decision
Suppose an authorized €600 deposit secures a rental, and your supported, documented deduction is €95. A final €95 capture leaves €505 to be released. That is a hypothetical arithmetic example; it does not determine whether the deduction is lawful or justified under your contract.
The reviewed PayRequest Stripe workflow requests extended authorization when available, records the provider expiry and supports one final capture, including a partial amount. It does not support repeatedly extending that Stripe hold. After a final partial capture, do not expect to capture another damage amount from the released remainder. Complete the supported inspection and communicate the basis of the decision before final capture and before expiry.
| Buyer acceptance requirement | Why it matters |
|---|---|
| Recorded successful authorization and expiry | Confirms actual security and usable deadline |
| Rental reference linked to the deposit | Connects the decision to the correct customer and item |
| Clear capture/release permissions | Assigns who makes the final decision |
| Before/after condition record and agreed terms | Supports a justified deduction |
| Customer confirmation and bank-timing explanation | Separates release action from statement appearance |
These are acceptance requirements for a representative rental, not a claim that we tested a live checkout.
When PayRequest is a suitable choice
PayRequest security deposits let you request remote damage security by link and manage release or capture. For the Stripe flow described here, connect an eligible Stripe account, agree the deposit terms and verify that authorization expiry covers your planned rental and final inspection. Keep the equipment-rental deposit workflow separate from the actual rental charge.
Check current pricing and plan limits before choosing. Free has a 2% standard successful-payment fee; active Premium at €5/month and Business at €20/month have 0% standard platform fees. Provider fees and commission-payment exceptions are separate. These plan rates do not establish the provider cost of a particular authorization, capture or refund.
Create an account and prepare one rental deposit link. Use its actual successful authorization and expiry to complete the horizon worksheet before expanding the process. If the horizon does not fit, choose another suitable collection model rather than promising indefinite protection.
Editorial note: materially refreshed on 14 October 2026 with AI writing and illustration assistance. Official provider sources and PayRequest Stripe code were reviewed. The horizon and capture examples are hypothetical; no live authorization test, damage recovery or customer outcome is claimed.
