Collect the rental fee as a payment and the refundable damage security as a separate card authorization when that matches your agreement and provider support. With PayRequest, use a payment link for the hire charge and a deposit link for the hold. Connect both records to the same booking without describing the held amount as money already paid to you.
This is a practical workflow for rental operators already using Stripe. It describes two separate customer actions, not a built-in combined checkout or an automatic synchronization feature.
Work through a €90 hire and €500 hold
For fictional booking RENT-204, the customer owes €90 for the hire and authorizes €500 as damage security. If both actions succeed, €90 is collected and €500 is reserved. The merchant has not received €590. The authorization can reduce available card balance or credit even though it is not a settled charge.
| Record | Amount | Evidence of completion | End-of-rental action |
|---|---|---|---|
| Hire payment | €90 | Confirmed successful payment | Handle any separate cancellation or refund obligation |
| Damage authorization | €500 | Confirmed authorized state and deadline | Release, or make a justified supported capture |
| Booking | One reference | Both requirements checked independently | Inspect and record the decision |
Stripe separates authorization and capture. An ordinary successful rental payment and an active hold are different financial states. Do not treat one notification as proof that both records are complete.
Give the customer two clear instructions
Create the hire request using PayRequest payment links. Create the security request using PayRequest security deposits. Save the two references on the booking and label the messages clearly.
A customer-message template: “For booking RENT-204, the rental payment is €90 at [payment link]. The separate damage authorization is €500 at [deposit link]; it reserves available card funds and is charged only through the agreed supported process. Please complete both steps before [handover deadline].”
Replace the amounts, conditions and deadline with your actual disclosed terms. Send real links through your normal communication channel. Do not request card details by message or promise immediate bank release.
Check both states before handover
A rental payment can succeed while authorization is declined, pending or abandoned. Confirm the deposit's authorized state and actual provider deadline before treating the booking as secured. For several bookings, use the multiple-deposit queue.
Authorize close enough to the rental for the hold to cover the agreed inspection and final decision. Creating the link months before arrival does not guarantee a months-long authorization. The Stripe deposit guide explains eligibility and deadline limits.
Settle the hold after the full inspection
Suppose a supported, documented €35 missing-accessory cost is identified. In PayRequest's current Stripe flow, a final capture of €35 releases the remaining €465. There is no second capture available for a newly discovered charge from that same authorization. Review the complete inspection before the final action.
If nothing is owed, release €500; do not call it a refund of the €90 hire payment. If the rental itself must be refunded, review that separate charge separately. The API reference documents final Stripe capture and its resulting captured state.
Compare costs and allowances for both records
PayRequest currently charges €0 platform fee on this Stripe deposit-capture flow; Stripe processing fees apply separately. Ordinary rental payments follow their own plan and provider fees. Check pricing, monthly deposit starts and simultaneous active holds rather than assuming that a free deposit allowance makes every payment free.
Prepare one fictional booking, confirm what each customer page says and rehearse the two-record decision before a live rental. This provides a focused route into PayRequest while preserving your existing booking process.
Editorial note: AI assisted with this article and cover. The €90/€500/€35 figures and message are original fictional examples. Documentation was reviewed on 13 October 2026; no combined-checkout feature, live payment test or customer outcome is claimed.
