The Client Approved the Work. Then the Chargeback Arrived.

Five Forty-Seven A.M.

The notification came in at 5:47 a.m.

Elliot Chen had not yet poured the coffee. The kettle was on. The blue light from the laptop screen was the only light in the room, and it cast a pale rectangle across the kitchen counter where he had left his phone the night before. The window above the sink showed a section of street that was still entirely dark — no traffic, no porch lights, no movement. It was the part of the morning that felt borrowed.

He had not meant to check email yet. He had a rule about it. Email after the coffee. The rule had survived approximately ten months of independent practice, which was about ten months longer than most of his rules survived.

He had broken the rule because the laptop had pinged, and because his phone had pinged at the same time, and because two pings at the same time before sunrise had a particular shape to them that he had learned to recognize without fully wanting to.

The browser tab title read Dispute Notification — Action Required.

He clicked it.

It was a chargeback. The amount was the full project — three thousand four hundred dollars, not a partial dispute. The reason code was services not as described. The customer's name was on the dispute screen, and reading it produced a small, specific physical reaction that he would think about for several days afterward: a tightness in the upper chest, slightly to the right of center, with no other symptoms. It was a feeling he had read described in books as outrage but which he experienced more accurately as confusion. He read the dispute reason twice. He read the customer's name a third time.

The customer was someone who, two and a half weeks earlier, had written him an email that said, in three sentences, this is exactly what I needed. Thank you for being so patient with my changes. You're a real one, Elliot.

The email was still in his inbox. He could see it from the dispute notification screen if he opened a new tab. He opened a new tab. He read the email. He went back to the dispute notification.

He sat at the counter for a long minute with the kettle starting to whistle and the kitchen still mostly dark and the laptop screen and his phone showing the same rectangle of bad news in two slightly different fonts.

This was the second time in his independent career that he had received a chargeback. The first time had been a clear miscommunication that had resolved within a day. This was not that.

What a Chargeback Actually Feels Like

There is a particular kind of small-business stress that is very specific and not widely discussed. It is the stress of having a payment that was already in your account — money you had already counted, already allocated against next month's rent, already, in a small but psychologically significant way, spent — yanked back through a system that had no relationship with the actual people involved.

A chargeback is, in its surface mechanics, a customer telling their card issuer that a charge should not have happened. The card issuer reverses the charge while it investigates. The merchant — Elliot, in this case — has a window of time, usually a week or two, to respond with documentation. If the documentation is sufficient, the chargeback is reversed. If it is not, or if it is, but the customer's bank decides otherwise, the money stays gone.

The mechanics are not the stressful part. The stressful part is that the customer's reasoning is filtered through an interface. There is no phone call. There is no opportunity to ask what specifically went wrong. There is no chance to see the customer's face. There is only a reason code (services not as described) and a dispute screen that lays out the case in a corporate-neutral font and asks the merchant to upload supporting evidence by a deadline.

The stress is the disorientation of having reality contested by a third party that has never met either of the people involved.

Elliot poured the coffee. He took it back to the counter. He sat down. He read the dispute screen one more time.

He had a deadline of seven days.

He thought, briefly, about writing the response immediately. He thought about everything he wanted to say. He thought about the this is exactly what I needed email, and about how unfair it was, and about how he would explain that unfairness to a faceless reviewer in a cubicle somewhere who would read his response in approximately ninety seconds and decide.

He stopped himself.

He had a small habit, in moments like this, of asking himself what a calmer version of himself would say to him about the next move. The calmer version was usually right. The calmer version, that morning, said: not yet. First, organize.

He closed the dispute tab. He opened a new note in his Notes app. He titled it chargeback — [customer initials], [date]. He started writing down what he knew.

What He Already Had

The thing Elliot had not yet realized, sitting in front of his cooling coffee in the dark kitchen, was that he had a great deal more documentation than he felt like he had.

The project had been, by his usual standards, well-documented. He had a written scope of work. He had three rounds of revision feedback in email. He had a delivery email with the final files attached, sent on a specific date and time. He had the this is exactly what I needed approval email two days after delivery. He had an invoice. He had a payment confirmation. He had, somewhere in his project management app, a record of every status update and milestone.

The reason it did not feel like he had documentation was that the documentation was scattered. Some was in email. Some was in a project management app. Some was in his laptop's Downloads folder. Some was in a Google Drive folder he had set up at the start of the project. Some was in a chain of Slack messages with the customer, because the customer had insisted on Slack for early-stage feedback and only switched to email after Elliot suggested it.

The documentation was not missing. It was unconsolidated. And in the form it was in — fragmentary, scattered across five tools — it was not yet usable as a chargeback response.

He started by opening a folder on his desktop. He named it chargeback response. He created subfolders inside it: 01 contract, 02 invoice, 03 deliverables, 04 approvals, 05 timeline, 06 supporting messages. He did this not because he had read somewhere that a numbered folder structure was the right way to respond to a chargeback. He did it because he had learned, over ten months, that when his work felt overwhelming the most useful first move was to give the work a structure.

He went into his Google Drive. He found the original signed scope-of-work PDF. He copied it into 01 contract.

He opened his email. He searched for the invoice he had sent the customer. He saved the PDF copy of the invoice into 02 invoice. He saved the email containing the invoice — date and time stamp visible — alongside it.

He found the original delivery email he had sent on the project completion date. He saved a copy of the email into 03 deliverables. He noted the date, the time, the recipient, and the file names of the deliverables. He saved screenshots of the delivered files showing their creation timestamps.

He opened his email again. He searched for the customer's approval. He found three approval-shaped messages: an early-stage this looks great, ready for the next round, a mid-stage exactly what I had in mind, and the final this is exactly what I needed. He saved all three into 04 approvals. He noted the dates.

He opened his Slack archive. He scrolled back to the early stages of the project. He found the messages where the customer had described what they wanted. He took screenshots — not just of the helpful messages, but of the surrounding context, with timestamps and the customer's name visible. He put the screenshots into 06 supporting messages.

He opened a blank document. He titled it timeline. He started typing.

It took him about two hours.

The Timeline

The timeline, when he was done, was two pages long. It was not dramatic. It was not adversarial. It was a list of dates with one sentence under each.

The first entry was the project's initial inquiry — the customer's first email reaching out, two months before the dispute. The next entry was the scope-of-work signature. The next was the kickoff call, with date and time. The next was each of the three revision rounds — date sent, date received, customer feedback summarized in his own words with reference to the email or Slack message that supported it. The next was the delivery — date, time, file names, recipient. The next was the this is exactly what I needed approval, two days later. The next was the invoice — date sent, date paid. The next was the date of the chargeback notification — five forty-seven a.m. that morning.

He read it.

What struck him, reading it, was that he was not reading a defense. He was reading the actual sequence of events of a normal project that had concluded normally and then been disputed seventeen days later. The sequence did not need editorial framing. It just needed to be seen.

He went back to his draft response document and started writing the actual response.

The Draft He Did Not Send

The first draft he wrote was a thousand words long.

He wrote about how the customer had been involved at every revision round. He wrote about how the this is exactly what I needed email was, by any reasonable interpretation, a final acceptance. He wrote about how the chargeback reason — services not as described — was contradicted by the customer's own words in writing. He wrote, in his fourth paragraph, that the customer had appeared satisfied throughout the project and that this dispute came as a complete surprise.

He read the draft. He sat with it. He went and made another coffee.

When he came back, he started over.

The second draft was four short paragraphs.

The first paragraph was a one-sentence statement of the project — type of work, agreed scope, agreed price.

The second paragraph was the timeline, condensed to its essential dates: scope signed (date), three revision rounds (dates), delivery (date and time), customer approval (date, with the this is exactly what I needed phrase quoted in single quotation marks for context), invoice paid (date).

The third paragraph was the dispute itself, stated factually: chargeback notification received (date), reason code (services not as described), amount disputed (full project total).

The fourth paragraph was the supporting documents, listed by file name and brief description.

It was, in total, less than three hundred words. It contained no defensiveness, no editorial framing, no anger. It was a statement of facts in the order they had occurred, attached to the documents that supported each fact.

He read it.

He uploaded it, with the supporting documents, eighteen hours after receiving the dispute notification. The processor's interface confirmed receipt. The deadline indicator changed from 6 days remaining to response submitted.

The processor would respond in eight to twelve weeks. He went and made breakfast. He sat at the counter, eating eggs, and noticed that the chest tightness from earlier had loosened at some point during the morning without his noticing exactly when.

What the Story Was Actually About

The chargeback outcome is not the point of this story. Neither, ultimately, is the customer's reasoning, which Elliot would never fully learn. What matters here — what stayed with him in the weeks afterward, and what shaped how he would set up his next project — was the difference between the version of himself that had wanted to respond at 5:48 a.m. and the version that had eventually responded at 11:32 p.m. that night.

The first version had wanted to defend himself. The second version had wanted to describe a sequence of events. Those are different acts. They produce different documents. They get different responses from people who are reading them.

What Elliot understood by the end of that day was not a strategy for winning chargeback disputes. It was a smaller and more useful thing: that the documents he had — the contract, the deliverables, the approvals, the invoice, the timeline — had always been there. He had simply not had them in one folder, in chronological order, with each piece labeled. The first hour of organizing had not produced a defense. It had produced a record. The record was what allowed the response to be calm.

This is not specific to chargebacks. The pattern repeats across most California small-business disputes. An unpaid invoice. A breach-of-contract disagreement with a vendor. A contractor refund question. A demand for a refund from a service customer. The question that decides most of these is rarely who is right. It is whose record of events can be read most easily by someone who was not there.

What Elliot Organized Before Responding

If you are reading this with a chargeback notification in your own inbox, or with the related but different problem of an invoice a client has gone quiet on, these are the items Elliot pulled into his chargeback response folder, in roughly the order he gathered them. None of them, on its own, decides anything. Together, they make the sequence legible.

Elliot kept all of this in one folder. The folder was the response. The written response itself was just a short letter that pointed to the folder.

• The invoice. The PDF, the email containing it, and the date and time it was sent.
• The contract or written scope. Whether a signed PDF, a statement of work, or an email exchange that confirmed what would be done and for how much. Anything that establishes what was agreed.
• Proof of delivery. The email or message in which the deliverables were sent, with date, time, recipient, and file names. Screenshots of the deliverables themselves with their file timestamps if available.
• Approval messages. Every customer message that suggests acceptance, satisfaction, or use of the deliverables. Even small ones — got it, thanks, looks good, moving forward with this — establish a pattern of acceptance.
• Final-file delivery record. If the project had a final formal delivery, that exact moment with its exact artifact and timestamp.
• The payment processor's notice. The full text of the chargeback notification, including the reason code, the disputed amount, the customer's stated reason, and the response deadline.
• The disputed amount. Stated clearly: total project value, partial dispute amount if applicable, any prior partial refunds.
• The refund policy or terms. If your contract or invoice referenced a refund policy, save the exact language as it existed at the time.
• Project timestamps. From your project management app, calendar, or email — the actual dates of the major project milestones. A processor reviewing your response can verify these against your documents.
• Screenshots. Of approval messages, of any praise, of the customer's own description of what they wanted. Screenshots are more useful than copy-pasted text because they preserve sender identity and date.
• Any client praise. Even informal — a Slack thumbs-up, a love it! in the middle of a thread, a forwarded email saying let me know what you think with an enthusiastic reply.
• Notes about deadlines. The processor deadline, your own production deadline, any earlier deadlines that were met.

What You Can Do Next

If you are facing a similar situation — a chargeback after completed work, an invoice a client has disputed, a contract a customer claims was not performed — the most useful first move is rarely the response itself. It is the inventory.

The xCounsel Toolkit's free Lawyer-Ready Case Summary Builder walks through the same questions Elliot eventually asked himself: who, what, when, how much, what was agreed, what was delivered, what messages exist, what is in writing. The output is a short structured summary that you can use as the spine of your processor response, or — if the chargeback ultimately succeeds despite documentation — as the spine of a follow-up California demand letter to the customer for the disputed amount.

If you are trying to decide what evidence matters most in your specific situation, the What Evidence May Help guide is short and practical. It is general information, but it can help you decide where to spend your first hour of organizing.

For the broader category of unpaid or contested invoices from California clients, the California unpaid invoice demand letter overview explains the framing — including California Civil Code section 3289, which provides for 10% annual interest on unpaid invoices once payment is due and unpaid. For disputes that turn on whether the contract or written scope was performed, the breach of contract letter overview covers the structure.

Not sure yet whether your situation is one to push on, one to negotiate, or one to walk away from? The Find Your Path quiz takes about a minute and points you toward the article, tool, or next step that fits where you are right now.

If your facts are organized and you are ready to move forward, you can Start a Matter. The chargeback outcome is not always the end of the story — even when a processor's decision goes against the merchant, separate options remain.

Related Reading

• California unpaid invoice demand letter overview — for follow-up after a chargeback decision
• California breach of contract letter overview — when the dispute turns on whether the work was performed
• California demand letter overview — the broader framing
• What evidence may help in a California civil dispute — categories that matter
• What to gather before requesting a contract review — earlier-stage preparation pattern
• Browse California civil dispute guides — the full Resource Center

Frequently Asked Questions

What evidence helps explain a chargeback after completed work?

The most useful items are the original invoice, the contract or written scope, proof of delivery, the customer's approval messages, and a chronological timeline. Together, these establish the sequence: agreement made, work performed, work delivered, work accepted. The xCounsel Toolkit walks through these one at a time.

What if the client says the work was not what they expected?

This is one of the most common patterns in chargeback disputes. Save the original scope and any messages where the client described what they wanted. Save the messages around delivery — including any client message after delivery that does not raise a quality concern. The fact that a client used or referenced the deliverables for two weeks before disputing them can be relevant to the question of whether the deliverables met the agreed expectations at the time.

Should I keep project files and approvals?

Yes. Project files, draft revisions, approval messages, and the final delivery record are the central artifacts in any chargeback or unpaid-invoice dispute. Keep them in a way that makes them easy to retrieve later — a single folder per project, named by date and customer, is often enough. Keep them for at least three to four years after a project closes, depending on the jurisdiction and project size.

What if the payment processor deadline is soon?

Most processors give 7 to 14 days. If you have less than 48 hours, prioritize: invoice, contract or scope, the single clearest delivery record, the single clearest approval message, and a one-paragraph timeline. A short, organized response within deadline beats a long, late one.

Can a written timeline help?

Yes. A two-paragraph timeline that lists dates and a sentence per event is often the most useful single document in a chargeback response. Reviewers triage many disputes per day; clarity rewards the responder who makes the sequence easy to read. The timeline does not need to be persuasive. It needs to be accurate and easy to follow.

Frequently Asked Questions