When a rental is canceled before pickup, check the security deposit separately from the booking and rental payment. Release an active, unused card authorization through the supported provider workflow. If money was already captured, investigate a refund instead. Changing a booking to canceled does not prove that a hold was released.
This guide is for equipment-rental operators closing a booking before anything leaves the premises. It gives you a three-record closure process: booking, security authorization and rental payment. Cancellation fees depend on the agreed terms and applicable rules; this article does not decide whether you may charge one.
Identify What the Customer Actually Paid or Authorized
Find the booking reference and every related payment attempt. Record the provider reference, amount, currency and current state for each. A cardholder's bank screenshot can help locate an entry, but the merchant record determines which action you can take through your payment provider.
An authorization reserves funds for a later eligible capture. A captured payment has already moved into the charge process. Stripe's manual-capture documentation distinguishes those states and explains that an uncaptured authorization expires if it is not used within its validity window. Do not assume a standard duration for every card or transaction.
Keep the reservation payment and security authorization on separate lines. A €120 rental payment plus a €600 security hold does not mean €720 was collected as revenue. If the rental is canceled, each line needs its own outcome and evidence.
First establish that pickup really did not happen. If equipment was dispatched, collected by another person or partially returned, the operational facts differ. Use your handover records before applying a before-pickup workflow to what is actually a return or damage case.
Close Open Checkout Attempts Before They Become New Holds
A sent authorization link is not proof of an active hold. If checkout was never completed, identify any still-open attempt and use the provider's supported cancellation or expiry controls where available. Stop scheduled reminders and remove the canceled booking from staff pickup lists.
PayRequest's release path and a booking system's cancellation path are separate controls. The Stripe deposit provider reviewed for this article returns without canceling a PaymentIntent when no PaymentIntent identifier is recorded. That branch is not proof that every previously shared checkout session has been invalidated.
This distinction matters when the customer opens an old email after you cancel the booking. Check the checkout attempt as well as the local deposit status. If you cannot establish that the attempt is closed, investigate its provider state and monitor for a later authorization instead of declaring the financial record settled.
Do not create a fresh authorization just to make it possible to release one. When no money was held, the correct customer message is that no confirmed hold requires release, subject to your completed attempt checks. It is not a refund confirmation.
Release an Active Hold or Review a Captured Payment
For an active, unused authorization, use the supported release action and verify its result. In the reviewed PayRequest Stripe path, release calls cancellation for the stored PaymentIntent. DepositService then records the released status and timestamp after the provider operation completes; an ordinary provider error is propagated rather than silently treated as success.
A released status does not establish when the customer's bank will show restored availability. Explain the action you confirmed and provide its reference. The separate hold-release timing guide covers the distinction between merchant release and the bank's display.
If the security deposit was captured, do not describe a refund as releasing an authorization. Check the captured amount, any earlier refunds and the current provider state. A partly captured deposit may require separate treatment of the captured portion and the unused authorization. Record both outcomes without combining them into one ambiguous “returned” amount.
Do not capture an unused damage hold merely to move a cancellation fee between records. Confirm the contractual and provider basis for any amount due, and handle it through the appropriate payment workflow. Neither a canceled booking nor possession of a card authorization proves entitlement to a charge.
Use a Three-Record Cancellation Card
Here is an original worked example: a fictional booking is canceled before pickup, its €600 security authorization is unused, and the parties agree that the separate €120 rental payment will be refunded in full. The assumed refund agreement is part of the example, not a universal cancellation policy.
| Record | Verified starting state | Action and closure evidence |
|---|---|---|
| Booking R-600 | Confirmed; equipment not handed over | Mark canceled, stop dispatch and reminders, retain cancellation timestamp |
| Security authorization | €600 active; €0 captured | Release through provider; record reference and confirmed result |
| Rental payment | €120 captured; €0 refunded | Issue agreed €120 refund; record its actual state and reference |
| Customer communication | Cancellation received | Explain €600 hold release and €120 refund separately |
After the release, €600 is the authorization amount released, not a €600 refund. The rental refund is €120. Do not send a “€720 refunded” message: it misdescribes both movements and makes later reconciliation harder.
Add an owner and next review time whenever a provider result is pending or uncertain. Check all attempts for duplicates before repeating an action. The closure card should let a colleague see what is finished, what remains open and which provider reference proves each statement.
Confirm the Outcome Without Promising Bank Timing
A suitable message, only after those outcomes are verified, is: “Booking R-600 is canceled and no equipment was handed over. We released the unused €600 security authorization, reference [reference]. We also initiated the agreed €120 rental refund, reference [reference], currently [status]. Your bank may update these entries at different times.”
If a release failed, say that it is being investigated. If the rental refund is pending, retain that label. Never ask a customer to email a complete card number or security code to help you locate the transaction; use the booking and provider references.
The security-deposit email templates help keep ordinary authorization and return messages consistent. For a cancellation, remove instructions to attend pickup or complete an old deposit checkout. Review any independently scheduled message in the booking system as well.
Keep the Deposit Workflow Connected to the Booking
PayRequest security deposits support the authorization, capture and release workflow. For equipment rentals, keep the deposit reference with your booking record and assign responsibility for cancellation closeout. Do not assume a booking cancellation automatically performs every provider action.
Use the three-record card for the next canceled rental and check current plans and pricing for your deposit workflow. The goal is a verified outcome for each record and an accurate customer explanation, with unresolved provider states kept visible until confirmed.
Editorial note: AI assisted with this article and illustrative cover. PayRequest release behavior was reviewed in code; no live authorization, cancellation or refund was executed. The closure card and amounts are original operational examples, not legal advice.