Chargeback Defense Packets for Service Work
Match a service chargeback to clear evidence: approved scope, work records, photos, invoice, payment, refunds, and a concise response.
Article
Example: A customer disputes a $425 service charge as “service not received.” The technician remembers the visit, but the photographs are on a personal phone and the invoice says only “maintenance.” The office needs a response tied to the job, not a stronger assertion that the work happened.
A chargeback packet is a short evidence set submitted through the processor's dispute process. It can help explain your position; it does not guarantee recovery or replace the underlying consumer's rights.
Read the notice before gathering documents
Record the dispute ID, transaction, amount, reason, response deadline, permitted files, and required submission channel. Assign one person to coordinate the response and preserve the receipt after upload. Use the deadline in the actual notice; do not borrow a consumer or network deadline as your merchant response window.
Visa's Core Rules, April 18, 2026 and Mastercard's Merchant Chargeback Guide, May 13, 2025 distinguish dispute categories and evidence paths. Your processor's instructions determine how your business participates in the relevant stage.
Consumer credit-card billing-error procedures under Regulation Z, 12 CFR 1026.13, and electronic-fund-transfer error procedures under Regulation E, 12 CFR 1005.11, have different scopes. Do not treat every debit, credit, fraud, service-quality, or amount dispute as the same legal claim.
Match the evidence to the allegation
| Claim | Evidence to prioritize |
|---|---|
| Service not received | Agreed service and date, work record, relevant photographs, delivery or attendance evidence, and completion status. |
| Not as described or defective | Accepted specification, before/after condition, tests, exclusions, complaint, and response offered. |
| Unauthorized payment | Transaction and authentication evidence available through the processor, authorization context, and connection between the payer and job. |
| Duplicate or incorrect amount | Approved price, transaction references, deposits, credits, invoice, and account reconciliation. |
| Cancelled service or missing refund | Cancellation terms disclosed before purchase, request date, service dates, and actual refund status and reference. |
An invoice explains a charge; it does not by itself establish performance. A signature or email can support an agreement without proving every aspect of cardholder identity. Stripe's evidence best practices specifically note the limits of customer correspondence for identity verification and recommend factual, concise evidence. Those are Stripe instructions, not a promise about another processor's process.
Build a readable packet from original records
Start with a brief cover note identifying the allegation, your response, and the attached proof. Then order only the relevant records:
- The accepted quote and scope attachment, including approved changes.
- The work order, service report, labeled photographs, and any test or delivery evidence.
- The completion signoff, including unresolved items rather than a blanket completion claim.
- The invoice, receipt, and refund or credit evidence.
- The complaint, cancellation, and response messages needed to explain the disputed issue.
Preserve original timestamps and complete source files. Select relevant excerpts for submission without altering their meaning. Explain technical terms so a reviewer outside your trade can follow the evidence.
An illustrative cover note could say:
The disputed transaction relates to quote Q-1184 for the listed condenser cleaning visit. Attachment 1 is the accepted scope. Attachment 2 records the May 16 visit, unit identity, completed tasks, and labeled photographs. Attachment 3 shows the invoice and payment matching the agreed $425 total. The attached message log records the customer's complaint and our offered inspection.
Use only statements supported by your actual records. If a portion was not completed or a complaint remains unresolved, say so.
Reconcile refunds and protect payment information
Compare the disputed amount with deposits, final payments, credits, and refunds. A customer statement helps show that arithmetic. Keep its ledger consistent with the processor's transaction records.
Follow the processor's current instructions before issuing or changing a refund during an active dispute. Stripe's response guidance describes its specific dispute workflow; a separate payment or refund can complicate reconciliation. Record what actually happened rather than treating a proposed refund as completed.
Exclude unrelated customer and employee information. Use the identifiers needed by the processor and avoid unnecessary card data. PCI SSC FAQ 1280 explains that card verification codes cannot be stored after authorization. They do not belong in a job file or evidence packet.
For future jobs, the written-quote guide and change-order guide help capture the agreement before a dispute exists. Good records should also support fair complaint resolution, not merely a later response.
Common questions
- Is a signed receipt enough to win?
No. Evidence needs to address the actual dispute, and the outcome depends on the applicable process and facts. A receipt alone rarely explains the complete service agreement and performance.
- Should every photograph and message be uploaded?
No. Submit relevant, readable evidence within the processor's requirements, preserving enough context to avoid misleading excerpts.
- What if the customer says the dispute was withdrawn?
Check the processor's instructions and actual case status. Preserve the customer's communication, but do not assume it completes your response obligations.
Sources reviewed October 18, 2026. Network rules and processor procedures can change; verify the instructions for the actual dispute.