Education · Payments
The dispute begins later. The evidence begins at the curb.
A guest challenges a card charge through their issuer. The operator then receives a reason, a deadline, and a chance to answer with records that already exist - or do not.
The definition
A chargeback is the card network process for reversing a disputed transaction, subject to review and evidence.
It is not the same as a refund. A refund is initiated by the merchant. A chargeback begins with the cardholder and issuer, travels through network rules, and can debit the merchant while the dispute is evaluated.
No evidence package guarantees an outcome. Issuers and networks decide disputes under the applicable rules.
The timeline
The notice is not the start of the work
A dispute reason is a question framed by network rules. The operator's job is to answer that question with the session record, not to retell the entire business relationship.
A parking dispute in four moments
→Reconstructing a session weeks later is slower and less credible than preserving its ordinary record.
Evidence should answer the reason
Recognition
What was purchased?
Property, date, service, amount, vehicle, and a descriptor the cardholder can recognize.
Authorization
Who agreed?
Checkout records, authentication results, and the terms shown at payment.
Delivery
Was service completed?
Arrival, payment, retrieval, return, and staff records tied to one session.
Communication
What happened after?
Receipts, support messages, refund activity, and any documented complaint response.
CE 3.0 is a narrow path, not a magic phrase
Visa Compelling Evidence 3.0 applies to qualifying card-absent Visa disputes under network reason code 10.4. Stripe's current implementation guide describes criteria including two prior undisputed transactions in a specified age window and matching identity data. That framework is useful only when the dispute and history actually qualify.
For every other case, follow the dispute reason and processor instructions. More pages are not automatically better; relevant, consistent records are.
The operating habit
Build the evidence packet while delivering the service.
Use a recognizable statement descriptor, issue a receipt, link the payment to a real session, preserve the vehicle and handoff record, and answer complaints in the same system. Fraud defense is not a document assembled later. It is an operation that can explain itself.
When a notice arrives, pause before uploading everything. Read the reason, confirm the response deadline in the processor, and build a short chronology with documents that address that reason. Redact unrelated guest information and avoid speculative commentary. A plate photo may connect a vehicle to a visit; it does not by itself prove who authorized a card. Evidence is strongest when every item has a specific job.
