Organize Evidence for a Detailing Payment Dispute

Understand What a Dispute Is and What It Isn't

A chargeback is a card-network reversal initiated by the cardholder through their bank, not a refund you control. Your processor freezes the disputed amount and asks you to respond with evidence. Submitting evidence does not guarantee you win; the card network makes the final call based on its own rules, which differ by card type and dispute reason code.

Disputes are not the same as a customer complaint or a request for a redo. If a customer calls you unhappy, that is still a service issue you can resolve directly. A chargeback is a formal bank process with deadlines, and missing the deadline usually means an automatic loss regardless of how strong your evidence is. Check your processor's dashboard the moment a dispute lands and note the response deadline immediately.

The Four Categories of Evidence That Matter

Processors generally look for proof of four things: that the cardholder authorized the transaction, that a service was actually delivered, that your policy was disclosed before payment, and that the scope matched what the customer agreed to. Weak evidence in any one category can sink an otherwise solid submission.

Authorization evidence includes signed agreements, booking confirmations, or a message where the customer confirmed the price. Delivery evidence includes timestamped before-and-after photos, a completion message or handoff note, and any customer acknowledgment that they received the vehicle. Policy evidence is your cancellation, refund, and scope-change terms as they appeared at the time of booking. Scope evidence is the original quote and any written change orders if the job expanded.

Before the Dispute: Records to Build at Every Job

The best time to organize dispute evidence is before any job starts. A quick pre-job vehicle walk-around with timestamped photos documents existing damage that a customer might later attribute to your work. A written quote or scope summary sent to the customer creates an authorization trail even if they never sign a formal contract.

At job completion, send a brief written message confirming what was done and invite the customer to raise any concerns before they leave. This completion acknowledgment is one of the most useful pieces of evidence because it shows the customer received the service and had a chance to object. Save that exchange in a folder tied to the job, not just in your phone's general messages app.

Chargeback Evidence Checklist

Use this checklist when you receive a dispute notice. Work through it in order: identify what you have, note gaps, and gather everything before you open the processor's evidence submission form. Submitting piecemeal or late is worse than a single organized package.

Do not include anything in your submission that reveals payment card numbers, CVCs, or any sensitive cardholder data. Your processor's system handles that separately. Your job is to document the service relationship, not the payment instrument.

DETAILING CHARGEBACK EVIDENCE CHECKLIST
Job reference: _______________  Dispute received: _______________  Processor deadline: _______________

AUTHORIZATION
[ ] Booking confirmation message or email (customer-initiated or accepted)
[ ] Written quote showing price and scope, with date
[ ] Signed service agreement or digital acknowledgment (if collected)
[ ] Deposit payment record tied to this job (amount, date)

SCOPE AGREEMENT
[ ] Original service description sent to customer
[ ] Any written change-order or upsell the customer approved
[ ] Notes of any scope limitations agreed verbally (document what you have)

DELIVERY PROOF
[ ] Timestamped pre-job photos of vehicle condition
[ ] Timestamped post-job photos showing completed work
[ ] Appointment date and time from your calendar or job record
[ ] Completion message or handoff note sent to customer
[ ] Customer reply or acknowledgment after completion (if any)

POLICY DISCLOSURE
[ ] Refund or no-refund policy as it appeared at booking (screenshot or copy)
[ ] Cancellation policy the customer saw before paying
[ ] Where the policy was displayed (booking page, email, invoice footer)

COMMUNICATION LOG
[ ] Full message thread with customer in order (screenshots with timestamps)
[ ] Any complaint or dispute the customer raised before the chargeback
[ ] Your response to any complaint, and outcome

FINAL CHECKS BEFORE SUBMITTING
[ ] Deadline confirmed in processor dashboard
[ ] No card numbers, CVCs or sensitive payment data included
[ ] All files clearly labeled by category
[ ] Submission made through processor's official dispute tool

Hypothetical Worked Scenario

Hypothetical: A solo operator completes a full interior detail on a sedan for $220. The customer pays by card at pickup and drives away without comment. Ten days later the operator receives a chargeback notice citing service not as described. The processor's dashboard shows a five-business-day evidence window.

The operator pulls the job folder and finds: a pre-job photo of a heavily soiled interior with a timestamp, a written quote sent by text listing the exact services for $220, a post-job photo showing the cleaned interior with a timestamp, and a completion text that reads 'All done, took about 3.5 hours, everything looks great, let me know if you have questions.' The customer replied 'Thanks, looks good!' The operator also has a screenshot of the refund policy posted on the booking page stating all sales are final once the vehicle is returned to the customer.

The operator assembles these six items in labeled PDF pages and submits them through the processor's dispute portal before the deadline. Submitting this evidence does not guarantee a win, but it gives the processor a complete picture of authorization, delivery, and policy disclosure. Without the completion text and customer reply, the delivery proof would rest on photos alone, which is a weaker position.

Where Evidence Falls Apart: Common Failure Cases

The most common failure is missing the deadline entirely. Processors do not extend deadlines for operators who were busy or didn't check email. Set a calendar alert the same day you see a dispute notice and treat the deadline like a court date.

The second most common failure is having no written scope agreement. If the job was booked by phone and nothing was sent in writing, you have no authorization trail. Photos show work was done but not what was agreed to or at what price. Verbal-only bookings are a real dispute liability. A text or email confirmation sent to the customer costs nothing and creates the record you need.

A third failure case is policy that was buried or not shown at booking. A refund policy on a receipt the customer received after paying does not count as pre-payment disclosure. The policy needs to be visible before the transaction completes.

Keeping Evidence Organized Between Jobs

A simple per-job folder system, whether on your phone, a cloud drive, or within a CRM that lets you attach notes and files to each appointment, prevents the scramble that happens when a dispute arrives weeks after a job closed. Name folders by date and customer name so you can find them in under a minute.

Weavr's contact and appointment records let you attach notes and link tasks to individual jobs, which gives you a consistent place to store completion notes and flag any customer concern raised after handoff. Keeping everything tied to the job record, rather than scattered across texts and email, means your evidence is already grouped when you need it. For your photos and message screenshots, a dedicated folder on your phone synced to cloud storage works well alongside whatever job management system you use.

After the Dispute: Whether You Win or Lose

If you win, the held funds are released. If you lose, the chargeback stands and you may also owe a dispute fee from your processor. Either way, review what evidence you had and what you were missing, then fix the gap in your booking process so the next job generates a complete record from the start.

A pattern of disputes on similar job types, say, high-dollar paint correction or same-day bookings without written confirmations, is a signal to tighten the intake process for those jobs specifically. Requiring a written scope confirmation before starting and sending a completion message on every job are two habits that cost almost nothing and reduce your exposure significantly. These are process decisions, not guarantees against disputes.

The practical takeaway

Pull your processor's dispute deadline first, then build your evidence file from four categories: authorization, delivery, scope, and policy disclosure. A completion message and pre-job photos are the two records most operators are missing. Fix your intake process after every dispute whether you win or lose.

Explore the relevant WeavrCRM workflow · Review integrations and requirements