Credit-card pre-authorisation practice — how much you hold, on what basis, for how long, with what release timing — is one of the most consequential operational policies a UAE rent-a-car operator sets, costing between AED 18,000 and AED 95,000 per branch per year in either chargeback losses, gateway fees on excess holds, customer-acquisition friction, or banking complaint volume. Most operators inherit their pre-auth practice from a payment-gateway default or from a single founder decision years ago, and never revisit the policy systematically. The right policy is knowable, the wrong policy is silently expensive, and the differences between operators of similar size on this single dimension can amount to 3 to 6 per cent of total profitability.
Pre-authorisation is the temporary hold a merchant places on a customer's credit card to reserve funds for potential charges — damage deposits, fuel costs, fines, salik, late-return fees, additional driver-day charges. The hold reduces the customer's available credit by the held amount, is settled to the merchant if charges materialise, and is released back to the customer if no charges are taken. The timing, amount, and clarity of communication around pre-auth all drive customer experience and economic outcomes for the operator.
The cost categories that pre-auth practice creates
The first cost is gateway processing fees on the pre-auth itself. Each pre-auth costs 0.05 to 0.15 per cent of the held amount in some gateway fee structures, plus a per-transaction fee of AED 0.8 to AED 1.5. For a 1,500 monthly transaction volume with average pre-auth of AED 2,200, gateway pre-auth fees alone run AED 1,800 to AED 4,800 per month. The cost is small per transaction but real in aggregate, and excessive pre-auth amounts (holding AED 5,000 when AED 2,000 would suffice) increase the percentage-based portion proportionately.
The second is chargeback losses from inadequate pre-auth. The most common chargeback scenarios in UAE rental are: customer leaves with damage that the operator only discovers at next pre-rental inspection (after the customer's card pre-auth has released), customer incurs salik tolls or fines that arrive weeks later (after pre-auth release), customer dispute over deposit deduction (pre-auth amount insufficient to cover the deduction). Each chargeback costs the operator the disputed amount plus a chargeback processing fee of AED 100 to AED 250 plus the staff time to compile dispute evidence plus the reputational cost on the operator's chargeback ratio.
The third is customer-acquisition friction. A pre-auth amount that exceeds the customer's available credit, or that surprises the customer at the counter, can trigger booking abandonment at the most expensive moment — after the customer has invested in completing the trip planning. The cost is not just the lost booking but the customer's likely choice to book elsewhere on the next trip.
The fourth is banking complaint volume from confused customers. Pre-auth releases timing varies by issuing bank (typically 5 to 30 days from the operator's release trigger), and customers seeing a long-held block on their card frequently call their bank, call the operator, and complain about the delay. Each complaint absorbs counter-staff or customer-service time of 8 to 25 minutes. At reasonable volume the absorbed time is substantial.
The right pre-auth amount by scenario
The right pre-auth amount depends on the rental's specific risk profile — vehicle category, rental duration, customer-history risk score, off-road clause, salik exposure pattern, expected fuel deposit. A flat single-number pre-auth applied to every booking either over-charges low-risk rentals (creating friction) or under-charges high-risk rentals (creating chargeback exposure).
The pattern that works: base pre-auth tied to vehicle category (compact sedan AED 1,500, mid-size SUV AED 2,500, premium SUV AED 4,500, luxury sedan AED 5,500, exotic AED 8,000+), plus rental-duration adjustment (each additional rental week adds 30 to 50 per cent), plus risk-score adjustment (new customer adds 25 per cent, repeat customer with clean history subtracts 15 per cent), plus salik-pattern adjustment (rentals to Dubai-airport customers with anticipated multi-day driving add AED 200 to AED 400).
The dynamic pre-auth is harder to implement than a flat number — it requires booking-flow integration with the risk-scoring layer — but the chargeback-and-friction trade-off pays back at any meaningful volume. Operators with the discipline to implement dynamic pre-auth typically see chargeback rate drop by 30 to 50 per cent versus the same operator's prior flat-pre-auth baseline.
The hold duration that minimises pain
The pre-auth hold persists until the operator either captures it (converts to actual charge) or explicitly releases it. The customer's card issuer adds their own release-timing window after the operator's action. The combined experience of "operator releases on day 1 after rental return, issuer processes release on day 8, customer sees the available credit restored on day 9" produces customer frustration that the operator's release timing alone does not capture.
The operator-side discipline that minimises customer pain: capture exactly what is owed within 24 hours of rental return (do not hold the entire pre-auth pending future-discovery of salik or fines), release the residual immediately, document the capture and release timing in the customer-facing receipt. The pattern that creates pain: hold the entire pre-auth for 14 to 28 days "in case" salik or fines surface, then capture the relevant portion and release the rest. The hold period is when the customer's credit is reduced and the complaint volume builds.
The trade-off is real: shorter hold periods improve customer experience but expose the operator to post-hold-release surfacing charges. The right balance is to capture early (within 24-48 hours of return) on confirmed charges, release the residual, and pursue any post-release salik or fines through customer-direct billing (email invoice with payment link, with a clear escalation path if not paid).
The communication pattern that reduces complaint volume
The communication that works: at booking flow, clear disclosure of pre-auth amount and the basis for it; at counter pickup, restatement of the pre-auth amount with the customer's acknowledgment captured (signed paperwork or e-signature); at rental return, immediate explanation of what is being captured and what is being released; in the post-rental email, a single-line summary of the financial flow.
The communication that fails: silent pre-auth not mentioned at booking, surprise at counter, no documentation of capture/release, no post-rental summary. The pre-auth is the same in both scenarios, but customer perception and complaint volume differ by a factor of 5 to 10.
Checklist: pre-auth practice review for a UAE rent-a-car operator
- Per-category base pre-auth amounts set deliberately, not by historical default.
- Rental-duration adjustment factor documented.
- Risk-score adjustment factor documented and applied.
- Salik-pattern adjustment for expected toll exposure.
- Capture-within-24-hours discipline for confirmed charges at rental return.
- Release-residual-immediately discipline for the unused portion.
- Post-release salik and fine pursuit via direct customer billing.
- Booking-flow disclosure of pre-auth amount and basis.
- Counter-pickup acknowledgment of pre-auth amount.
- Post-rental email summary of capture and release amounts.
Frequently asked questions
What is the right pre-auth for a compact sedan rented for 3 days to a repeat customer? AED 1,500 base + zero duration adjustment + minus 15 per cent for repeat-customer status = roughly AED 1,275. Most operators over-hold this scenario by 50 to 100 per cent.
What is the right pre-auth for a premium SUV rented for 14 days to a new customer? AED 4,500 base + roughly 75 per cent for 14-day duration + plus 25 per cent for new-customer status = roughly AED 9,800. This scenario warrants a high hold; under-holding here creates real chargeback exposure.
Can I pre-auth in a currency other than AED? Possible if your payment gateway supports it, and useful for GCC visitors who prefer the hold in their home currency. The FX margin on the conversion adds complexity; most operators stay in AED and absorb the gateway-conversion as part of customer cost.
What is the chargeback risk if I do not pre-auth at all? Substantially higher. The pre-auth establishes the customer's consent to the charge basis and provides chargeback dispute evidence. Operators without pre-auth practice routinely lose chargebacks they would otherwise win.
How do I handle a customer whose card has insufficient available credit for the standard pre-auth? Offer a reduced pre-auth tied to specific restrictions (no salik-incurring routes, daily mileage cap, return-with-full-tank), or decline the booking. Accepting the booking with inadequate pre-auth is the worst of both worlds.
What is the right pre-auth for a one-way booking with drop-off at a different branch? Standard pre-auth plus 25 to 50 per cent for the one-way logistics risk. Communicate the elevation at booking, not at counter.
Should I release pre-auth on cancellation? Yes, immediately. A held pre-auth on a cancelled booking is a guaranteed complaint generator.
How often should I revisit pre-auth policy? Annual review of the per-category amounts against the past 12 months of chargeback data. Adjust upward where chargebacks recurred, downward where over-holding was evident from no-capture-needed patterns.
Operate UAE rentals at the level customers expect in 2026
PRO-VIA Portal — UAE's purpose-built rental ERP. FTA invoicing, Salik & fines reconciliation, owner statements, digital handover, multi-branch reporting. Built in Dubai for operators ready to scale beyond spreadsheets.
Plans from AED 290/month. Start your portal in 10 minutes → · compare plans