Damage disputes and chargebacks: protecting your agency

A chargeback is the order by which the cardholder’s issuing bank claws back a payment the agency has already collected, and it is almost always won before it arrives: with an evidence file built at pick-up and at return, not reconstructed afterwards. When your acquirer notifies you of the dispute, you have a short window, set by the payment scheme, to submit your proof — and if the material is not already complete and in order, the deadline expires while you are still looking for it.

Rental is a convenient target because the cardholder has two classic lines of attack: claiming they never authorised the amount charged after return, or claiming the damage you are billing was already there at pick-up. Both collapse against the same thing — dated, signed, internally consistent documentation — and neither collapses against an explanatory email written after the fact.

What a chargeback is, and why rental is exposed

The chain is always the same: the customer disputes the transaction with their own bank, the issuer opens the case with the scheme, the scheme passes it to the acquirer, the acquirer passes it to you. Every dispute carries a reason code — the formal ground on which the payment is being questioned: transaction not authorised, service not provided as agreed, amount different from the one agreed. The reason code is not administrative trivia; it decides which evidence is useful. Answering the wrong reason code with perfectly good material counts as not answering at all.

In rental the friction points are few and repetitive, and they are the same ones you will later read in the reason code:

• The pre-authorisation on the security deposit, which the customer sometimes reads on their statement as a full charge and disputes by misunderstanding.
• Damage found at return, especially where the customer was not present for the inspection or the vehicle was dirty or checked in the dark.
• Missing fuel, mileage over the threshold and deep cleaning: small line items that trigger disproportionate disputes when they are not documented.
• Traffic fines and unauthorised entries into the zone a traffico limitato, the restricted-traffic zones in Italian historic centres, which land months later and are passed on with a case-handling fee.

The stages of a dispute, without inventing deadlines

The sequence is standardised by the schemes; the timings are not. They vary by scheme, by reason code and by your contract with the acquirer, and they change over time. The only deadline you should work to is the one written in the notice from your acquirer or terminal provider, not the one you remember from last time. What is certain: the window is short, it runs from the date of notification, and a file submitted late is discarded unread.

1. 1Notification: the acquirer tells you the dispute, the amount withheld and the reason code. Your clock starts here.
2. 2Documentary defence: you send the file to the acquirer, which presents it to the scheme on your behalf. You cannot approach the scheme directly.
3. 3Issuer decision: the customer’s bank assesses whether the evidence is enough. If it is, the money comes back to you.
4. 4Second presentment: if the issuer is not convinced, the dispute is re-raised. At that point you need new material, not what has already been rejected.
5. 5Arbitration: the scheme has the final word, with fixed procedural costs borne by the losing side.

The evidence file, stage by stage

A credible file is not a pile of attachments: it is a coherent story with verifiable dates and the customer’s signature in the right places. The aim is that a clerk at the issuing bank, who has never seen a rental car in their life, grasps three things within a few minutes: the vehicle was undamaged at handover, the damage appeared during the rental, and the charge was provided for in the signed contract. The pattern below should be repeated on every rental, not only on the ones that look risky.

Photos and video that stand up as evidence

The difference between a photo archive and evidence is verifiability. Four counter habits that cost a few minutes and change the outcome:

• The same framings at pick-up and at return, in the same order: corners, flanks, roof, wheels, windscreen, interior, boot.
• A short video circling the vehicle in one unbroken take: a continuous sequence is harder to argue with than an isolated still.
• Enough light and a clean vehicle. An inspection done on wet or dirty bodywork is the first argument the other side will use.
• Files kept with their original date and time, with no cropping and no re-compression, filed against the contract number rather than in the phone gallery of whoever was on the desk.

How to respond once the dispute lands

The response is not a letter of protest: it is an ordered file that answers the reason code point by point. One named person should own the case, with the deadline in their calendar and access to all the material.

1. 1Read the reason code and the deadline given in the acquirer’s notice, and put that date in the calendar immediately.
2. 2Select only the documents that answer that reason code, in chronological order, with a one-page index on top.
3. 3Write a sober reconstruction of the facts: dates, who did what, a pointer to the document proving each step. No judgement on the customer.
4. 4Quote the clause that authorises the charge and attach the signed page, not the whole standard contract.
5. 5Send it to the acquirer in the format and within the size limits it specifies, and keep proof of submission.

Prevention: clauses and counter habits

Most of the chargebacks an agency loses are not lost in the case review: they are lost at the counter, weeks earlier. Some of the levers cost almost nothing.

• Explain out loud the difference between a pre-authorisation and a charge, and put it in the written confirmation: it removes a whole slice of misunderstanding disputes.
• Have the return report signed, with space for the customer’s own remarks. If they refuse, record the refusal with date, time and the staff member’s name.
• Charge nothing without prior written notice setting out the amount, the reason and the document behind it: the surprise charge is the classic trigger for a dispute.
• State the excess and the cover clearly before booking. Opacity about the deposit is the leading cause of friction.
• For fines and restricted-traffic zones, put the mechanism and the case-handling fee in the contract and point the customer to the relevant comune, the municipality: rules, hours and access gates are decided by each municipality and change often.
• Keep a register of disputes by reason: after a few months you will see for yourself which step of your check-in is the weak one.

Official sources and operational support

Two documents are worth the reading time. The first is the rulebook of the payment scheme you work with, in its current version, plus the terms handed to you by your acquirer or terminal provider: that is where the reason codes, the deadlines and the file formats live, up to date. The second covers the part that stays outside the scheme — the relationship with the customer: the Codice del consumo, Italy’s consumer code, the conciliation procedures it provides for, and the guidance of the competent Italian authorities on banking and consumer protection all still apply once the card has had its say. On clauses and pre-contract disclosure, legal advice taken once costs less than two lost disputes.

Operationally, documentary discipline is easier to keep when the system imposes it. Listing your fleet on a marketplace such as DRIVO means working with written bookings and confirmations, a calendar and fleet management in a single back-office, verified profiles and reviews, multilingual listings that reach travellers in five languages, and automatic payouts through Stripe. There is no listing fee and no monthly fee: commission applies only to completed bookings, so an empty week costs nothing. No platform wins a chargeback for you, but a written trail that creates itself is exactly the material you will later have to hand to your acquirer.