P5 · Handling payments and disputes
A Client Filed a Chargeback: What That Means for You
Respond to a freelance chargeback by identifying the reason and deadline, preserving the right evidence, and submitting a concise packet tied to the cardholder's claim.
A chargeback is a card-payment dispute handled through the issuer, card network, and processor; it is different from a voluntary refund you initiate under your customer policy. The processor may remove or hold the disputed amount while the case is open and may charge a dispute fee. Exact timelines and fees come from your processor and network, not a universal freelancer rule.
A filed chargeback changes the workflow from refund talk to formal evidence
A chargeback is a formal card dispute, not the same thing as a client asking you for a refund. Once filed, the processor may remove or hold the disputed funds while the issuer and network process the case, and a dispute fee may apply.
Read the reason code or processor explanation before sending evidence. A response to 'service not received' should emphasize delivery; a response to 'not as described' needs scope, acceptance criteria, revisions, and client communications. A stack of unrelated screenshots is weaker than evidence organized around the question the issuer is deciding.
Start by identifying the dispute story the issuer is reviewing
Common service disputes include unrecognized charges, alleged non-delivery, cancellation disagreements, duplicate processing, and claims that the service did not match the description.
Match every document to the dispute reason
Build a short chronology: contract signed, payment authorized, kickoff, milestone delivered, client approved, final files sent, complaint received. Then attach the few documents that prove those steps—signed scope, invoice or receipt, delivery records, messages approving work, meeting summaries, revision history, and the cancellation or refund policy the client saw before paying. Do not edit timestamps or overstate what technical data proves. For processor-side representment detail, the linked chargeback guide can help organize the response, but your processor's current deadline and evidence rules control the case. Afterward, ask what allowed the dispute: a bad descriptor, weak acceptance record, unclear cancellation term, or client-selection problem.
Treat a chargeback notice as a deadline-driven evidence request. Read the processor’s reason category and response due date first, then preserve the exact transaction record. Build a compact packet that connects the cardholder to the purchase and the purchase to delivery: signed contract or accepted proposal, invoice, payment confirmation, statement descriptor, client emails, milestone approvals, file-delivery logs, meeting records, refund/cancellation policy, and any proof that the customer used or accepted the work. More pages are not automatically better. The strongest evidence answers the specific dispute reason and is easy for a reviewer to follow. Do not fabricate signatures, timestamps, or ‘proof’ after the fact.
Separate chargeback strategy from the client relationship. Sometimes a cardholder disputes because they do not recognize the descriptor; sometimes there is a genuine quality, cancellation, or scope disagreement; sometimes the client uses the card process after accepting work. If a legitimate refund is owed under the contract, resolving it can be better than fighting mechanically. If the dispute is inaccurate, respond through the processor within the deadline and keep communication professional. Track the outcome and the root cause. An unclear descriptor suggests a billing fix; a ‘not as described’ pattern suggests scope and acceptance evidence need improvement; repeated high-value card disputes may justify a different payment rail or deposit structure. Representment rules and reason codes vary by network and processor, so use the linked dispute guide only after you have assembled the contract, delivery, and communication evidence described here.
After each dispute, write a five-line postmortem: reason code/category, transaction amount, evidence submitted, outcome, and one process change. Over time, patterns matter more than one loss. If disputes cluster around final milestone payments, strengthen acceptance and delivery records. If they cluster around subscription renewals, improve renewal notice and cancellation handling. If ‘unrecognized’ is common, fix the descriptor and receipts. Keep the processor’s final decision and any fee/withdrawal in the accounting file. A chargeback is both a financial event and a product/process signal; treating it only as a one-off fight wastes the information it provides. Also reconcile the temporary debit and any later reversal in the books so the revenue, chargeback fee, and recovered amount are not confused. Payment disputes can distort monthly profit if the accounting simply deletes the original sale.
Match the evidence packet to the dispute reason
Your response should be organized around the specific dispute reason. A 40-page dump of unrelated messages is weaker than a concise packet that directly proves authorization, delivery, acceptance, and policy disclosure.
When you need to turn the project file into a processor-ready response, a chargeback evidence guide can help structure the evidence packet; the processor deadline and dispute reason still control what you submit.
Use a few primary records instead of a screenshot dump
Useful evidence can include signed scope, invoice, card receipt, client messages approving work, login or delivery records, meeting notes, revision history, and a refund/cancellation policy the client saw before paying.
Build an evidence packet around the dispute reason
Response packet: page 1 is a one-paragraph summary and timeline; page 2 is signed scope and payment authorization; page 3 is delivery proof; page 4 is written acceptance; page 5 is the relevant cancellation/refund term. Match the packet to the processor's reason code and upload deadline.
Chargeback evidence packet
- Reason
- Read the processor’s dispute category and issuer claim first. “Unauthorized,” “not received,” “not as described,” “duplicate,” and “canceled” disputes call for different evidence; a generic stack of documents can bury the point.
- Timeline
- Create a dated chronology from authorization through delivery, acceptance, complaint, refund discussion, and dispute notice. Keep the summary factual and make every date traceable to a record.
- Evidence
- Select signed scope/terms, invoice or payment authorization, delivery proof, client acceptance, correspondence, refund/cancellation policy acknowledgment, and other documents that directly answer the reason. Square specifically advises clear, concise, transaction-linked evidence.
- Deadline
- Use the response deadline displayed by the processor for that dispute and submit through its required workflow. Do not assume one universal chargeback response period across networks and processors.
- After-action
- Whether you win or lose, review descriptor clarity, scope/acceptance, refund wording, milestone evidence, and client screening. A dispute can reveal a preventable ambiguity in the operating process even when the work was legitimate.
First-hour response to a payment dispute
- Read the processor reason and deadline first.
- Freeze a clean copy of relevant evidence.
- Build a dated one-page chronology.
- Submit only documents tied to the dispute issue.
- Review root causes after the case closes.
Processor dispute-evidence references
Chargeback questions when a client bypasses refund discussion
How is a chargeback different from a refund?
A refund is initiated by the merchant under its own policy; a chargeback is a dispute initiated through the cardholder's issuer and payment network. Once a dispute opens, follow the processor's deadline and evidence process instead of treating it as an ordinary customer-service refund request.
What evidence is useful for a service-business chargeback?
Square's current guidance points to items such as contracts, invoices, email correspondence, terms, and signed or otherwise clear proof of satisfactory delivery. The useful set depends on the dispute reason, so select evidence that directly answers the cardholder's claim.
Should I upload every screenshot I have?
No. A short chronology plus legible, relevant documents is usually easier to review than a screenshot dump. Identify the transaction, what was promised, when it was delivered, what the client acknowledged, and how any complaint was handled, then attach evidence for those points.
Does winning a chargeback guarantee I will keep the money forever?
Not necessarily in every process. Network rules, issuer decisions, further review or arbitration, and processor terms can affect the outcome. Follow the specific processor instructions and treat the case result as separate from any independent contractual claim you may have.
If I win a chargeback, does that prove I complied with the client contract?
No. A card dispute decision is made within the payment-network process and does not necessarily resolve every contract, refund, warranty, or legal claim between the parties. Keep the contract, scope, acceptance evidence, delivery records, invoice, and communications even after the processor closes the dispute because a separate commercial disagreement may continue.