If a rental deposit is declined before pickup, verify the merchant-side authorization status before handing over equipment. A checkout link, a customer's screenshot or a paid rental fee does not establish an active security hold. Identify the next supported customer action, then confirm the actual amount, currency and authorization deadline before relying on it.
This guide is for independent equipment-rental operators using online card authorizations, with Stripe as the provider example. It covers the decision before dispatch. A hold that was authorized earlier and later expired needs the separate expired-deposit workflow.
Check Whether the Rental Deposit Was Declined or Never Completed
Begin with the booking reference and deposit record. Confirm that you are looking at the correct customer, amount, currency and provider. If the customer opened checkout but did not finish, the absence of an authorization does not necessarily mean the bank declined it.
In PayRequest's current Stripe deposit flow, creating checkout returns a checkout URL and session state. The capture deadline is initially unknown. The authorization event later updates the deposit to authorized and records the provider's deadline when supplied. This behavior was reviewed in code on 12 September 2026; creating or sending the link is not the same event as obtaining the hold.
Check the provider record if the customer-facing screen and your deposit screen disagree. A delayed update, abandoned authentication and a confirmed issuer decline require different responses. Until the discrepancy is resolved, record the authorization as unconfirmed for your handover decision.
Stripe's manual-capture documentation explains that authorization reserves funds for later capture and that the authorization has a limited validity period. Even a confirmed hold is not an indefinite guarantee or a substitute for an agreed rental contract.
Choose an Action From Evidence, Not Repeated Retries
Use the specific action category available from your provider. You may need to inspect the provider dashboard or ask support; this article does not claim that PayRequest displays every raw decline code. Keep the customer message neutral and useful.
Stripe's decline-code reference distinguishes authentication requirements, incorrect details, unsupported cards, insufficient funds, issuer unavailability and duplicate attempts. Those differences matter because retrying unchanged details does not solve every failure.
| Verified situation | Useful next step | What staff should avoid |
|---|---|---|
| Checkout unfinished or authentication required | Ask the customer to complete the supported checkout/authentication flow | Treating an opened link as an active hold |
| Incorrect card or billing details | Customer corrects details in secure checkout | Collecting card numbers or security codes by email |
| Unsupported card, insufficient funds or issuer decline | Customer checks with issuer or uses a supported alternative card | Promising approval or bypassing provider controls |
| Provider or issuer temporarily unavailable | Follow the provider's retry guidance and reconcile the first attempt | Creating several new holds without checking existing attempts |
| Possible duplicate or uncertain result | Locate each attempt and confirm its current state | Assuming the latest error means every earlier attempt failed |
For a generic decline, do not tell the customer that fraud has been proven. Provider risk signals can be sensitive and do not establish what happened. Ask the customer to contact their issuer or use a supported payment route, while following the provider's guidance.
Keep the Paid Rental Fee Separate From the Deposit
Consider a fictional equipment booking with a €120 rental charge and a required €500 card authorization. The €120 charge is confirmed paid, but the deposit attempt is declined. The rental revenue record is correct; the security-hold condition is still unmet.
| Booking element | Verified state | Operational meaning |
|---|---|---|
| Rental charge | €120 paid | Rental fee received |
| Deposit attempt A | €500 declined | No confirmed €500 hold from this attempt |
| Deposit attempt B | Checkout opened, result unknown | Investigate before another attempt |
| Equipment handover | Not yet completed | Apply the agreed pickup policy using verified evidence |
Do not add €120 and €500 together and label €620 “paid.” A charge and an authorization have different meanings. Equally, do not refund a hold that was never captured merely because the customer reports a bank entry; first establish the actual payment state.
After a supported second attempt succeeds, record its reference and check whether an earlier attempt also produced an authorization. Resolve an unnecessary duplicate through the appropriate provider action. A customer's available balance can remain affected while their bank updates, so avoid promising immediate restoration.
This example is an operational control, not advice to charge a specific deposit amount. Your equipment value, agreed terms, provider eligibility and applicable rules determine what arrangement you can offer.
Make the Pickup Decision Explicit
Set a decision deadline that leaves time to resolve an issue before collection. Your handover record should identify the booking, equipment, rental payment, required deposit, latest confirmed authorization, deadline, decision owner and next action. Keep card details out of this record.
If the agreed pickup conditions require an active hold, pause handover until they are met or an authorized manager approves a documented alternative. Do not silently reduce the required amount because a smaller authorization might pass. Any changed arrangement must be agreed and recorded before you treat it as covering the rental.
A bank transfer or captured deposit may be an alternative under your terms, but neither creates the same card-authorization state. Explain the changed payment and return process to the customer. A checkout accepting a payment method does not prove that method supports a security hold.
Once the hold is confirmed, connect its actual expiry deadline to the expected return and inspection time. Use the equipment-rental inspection checklist for condition evidence. Solving today's decline does not remove the need to inspect and settle correctly after return.
Send a Customer Message That Matches the Current State
Use wording like this only when it matches your verified records: “Your €120 rental payment is received. We have not yet confirmed the separate €500 security authorization for booking R-120. Please complete the secure checkout or contact your card issuer if it is declined. We will confirm the pickup arrangement after checking the result.”
If the result is uncertain, say that you are checking it before requesting another attempt. If an authorization is confirmed, identify the amount and explain the hold separately from the rental charge. Avoid putting internal fraud indicators or complete card data into a support conversation.
The useful support record is small: timestamp, booking reference, provider reference, broad outcome, next action and owner. It should let the next staff member continue without asking the customer to repeat sensitive information.
Use PayRequest to Track the Confirmed Deposit
PayRequest security deposits provide the authorization, capture and release workflow. For equipment rentals, connect the deposit reference to your operational booking record and verify the provider state before dispatch. PayRequest cannot override a bank decline or decide whether a customer meets your rental terms.
Review pricing alongside your provider agreement. PayRequest's Free plan has no monthly subscription charge; its published fee is 2% per successful payment, capped at €25 per transaction, and provider fees are separate. Do not describe an unconfirmed authorization as a successful payment or invent a fee outcome for a failed attempt.
Start your next booking with PayRequest security deposits, an agreed deposit requirement and a named person responsible for confirming it before pickup. That gives the customer one clear next step and gives staff an evidence-based handover decision.
Editorial note: AI assisted with this article and illustrative cover. The PayRequest Stripe checkout and authorization paths were reviewed in code; no live authorization or capture was performed. The handover matrix and €120/€500 example are original operational templates.