Direct answer

A chargeback is won on the packet, not on the argument.

A chargeback is the bank taking the money back first and asking questions second. The work is already delivered, the payment is already reversed, and the only thing that decides what happens next is the evidence packet you submit inside your payment processor or platform deadline. Here is the whole sequence, in order.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 21, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

Step 1. Read the reason code and the deadline first

The moment the notice lands, find two things before you do anything else: the reason code or reason given for the dispute, and the date your response is due. The reason tells you which packet to build, because a claim that the work was never received and a claim that the work was not as described are answered by different evidence. The deadline is harder than it looks. Missing the response window is an automatic loss in most systems, even when your evidence is strong. Write the deadline down, work backwards from it, and treat everything else on this page as steps toward submitting before it.

Step 2. Do not refund privately, and do not deliver more work

While the dispute is open, the money is already out of your account through the bank. Sending the client a private refund on top of that can leave you paying twice for the same charge if the dispute also closes in their favor. The same caution applies to extra work: do not deliver new files, fixes, or extras to settle the matter informally while the case is open, because new delivery muddies the record of what was delivered and when. Keep everything inside the dispute system from here on, so every message and every file is part of one dated file.

Step 3. Send the client one short message, in case it is a mistake

Some chargebacks are not a fight at all. A charge can look unfamiliar on a statement, a second person at the client can dispute a payment they did not make themselves, or a duplicate payment can get reversed on one side only. One short, factual message covers that case: name the charge, the date, and the work it paid for, and ask the client to check and to withdraw the dispute with their bank if it was a mistake. A client withdrawal is the fastest clean ending there is. Keep it to one message. If the client confirms a mistake, keep their reply, and still watch the deadline until the dispute system shows the case as closed. If the client does not reply, or says the dispute stands, move straight to the packet.

Step 4. Build the evidence packet, matched to the stated reason

The packet is a small bundle, in time order, with each item labelled in one line. It has five parts: the agreement that set the work and the price; the invoice and the payment record, so amount and date line up with the charge; the delivery record, showing each step of the work with the time it was saved; the acceptance state, showing whether the client accepted the work, flagged it, or has not decided; and the messages where the client used or approved the work. Then match the order to the reason: never-received claims lead with the delivery record and the acceptance state, not-as-described claims lead with the agreement and the approval messages. This is what the delivery-plus-acceptance half of a chargeback packet looks like when the work ran through Zambo:

Accepted: the client decision is on the record

Pending: delivered and checked, still waiting on the client

Notice what those two records give a reviewer. The accepted record shows the work, its steps, and the client's own decision on a date, marked ok_to_release. The pending record shows delivered, checked work with the decision still open, which is also a documented state, not a gap. If your work did not run through a recording tool, assemble the same half of the packet from sent mail, file history, and version history. It is weaker, because you gathered it yourself after the fact, and it is still far stronger than a paragraph saying the work was sent.

Step 5. Submit one timeline statement plus the packet, before the deadline

Submit inside your payment processor or platform dispute system, not by email and not in a chat thread with the client. The submission is two things: one clear timeline statement, and the packet behind it. The statement fits on one page: what was agreed, when the work was delivered, when the client accepted or used it, when they paid, and when the chargeback arrived. Plain dates, no adjectives, no grievances. Then attach the packet in the same order the statement walks through it, so the reviewer can check each sentence against a document in seconds. Submit with time to spare, save the submission confirmation, and keep a copy of everything you sent.

Step 6. After it resolves, fix the setup

Win or lose, the next job should not be able to produce the same scramble. Three changes do most of the work. Take a deposit before work starts, so a single reversed payment is never the whole fee. Get acceptance on the delivery record before you hand over final files, so the client's decision exists before the money argument can start. And let card payments carry the record: deliver through a handover link, keep the agreement and the invoice on that same record, and file the packet pieces as you go instead of rebuilding them under a deadline. A chargeback against that setup is answered by forwarding a record that already exists.

What a record does not decide

A verifiable receipt proves the saved result was not changed since it was saved. It does not prove the work was good, it does not prove who produced it, and the bank decides the chargeback, not the record. A record makes the evidence complete and checkable; it cannot force an outcome. This page is general information, not legal or financial advice, and dispute rules, reason codes, and deadlines vary by bank, by processor or platform, and by what you agreed with the client.

Frequently asked questions

My client filed a chargeback after I delivered the work. What do I do?

A chargeback means the bank has already taken the money back and is asking questions second, so the fight is won on the evidence packet you submit inside the deadline, not on arguing with the client. Start the day the notice lands: read the reason code and the response deadline, because missing that window is an automatic loss. Do not refund privately and do not deliver more work while the dispute is open. Send the client one short message in case it is a genuine mistake, such as an unrecognized or duplicate charge, because a client withdrawal is the fastest clean ending. Then build the packet matched to the stated reason: the agreement, the invoice and payment record, the delivery record with per-step times, the acceptance state, and the messages where the client used or approved the work. Submit one clear timeline statement plus the packet inside your payment processor or platform dispute system, before the deadline.

What happens if I miss the chargeback response deadline?

In most systems, missing the response deadline closes the dispute in the client's favor by default, with no review of evidence you meant to send later. Treat the deadline in the notice as the real deadline, not the date the money left, not the date you first heard about it informally, and not a date you can usually extend by asking. Work backwards from it: gather the packet first, write the one timeline statement second, and submit with time to spare so a failed upload or a missing file does not cost you the whole case. If the notice is already close to its deadline when you find it, submit what you have on time rather than waiting for a perfect packet. A complete agreement, invoice, delivery record, and acceptance state submitted on time beats a stronger packet submitted late.

What if the chargeback was a genuine mistake by the client?

It happens more often than people expect: a charge looks unfamiliar on a statement, one person at the client pays and another disputes it, or the same invoice gets paid twice and one payment gets reversed. That is why the one short message to the client comes before the packet hardens into a fight. Keep it factual: name the charge, the date, and the work it paid for, and ask them to check and to withdraw the dispute with their bank if it was a mistake. A withdrawal by the client is the fastest clean ending, because the bank is acting on their instruction. If they say it was a mistake, ask them to confirm the withdrawal in writing and keep that message in the packet anyway, and still meet the response deadline unless the dispute system shows the case as closed.

What evidence actually helps in a chargeback after delivery?

The evidence that helps is the evidence matched to the reason the bank was given. If the reason is that the work was not received, lead with the delivery record showing each step and the time it was saved, plus the acceptance state. If the reason is that the work was not as described, lead with the agreement and the messages where the client approved or used the work. In every case include the invoice and the payment record so amount, date, and charge line up without anyone having to trust your summary. Put it in time order, label each item in one line, and keep opinion out. The reviewer was not in your messages and has only the packet, so a calm timeline they can check beats a long defense they have to take on faith.

How do I protect the next job so a chargeback is easier to answer?

Set the job up so the packet already exists before anyone disputes anything. Take a deposit before work starts, deliver through a record instead of loose attachments, and get acceptance on that record before you hand over final files, so a card payment carries the agreement, the delivery steps, and the client's decision with it. When the work runs through Zambo, every step is saved as it happens and the client receives one handover link to check and accept or flag. For $0.99, win the dispute with the packet: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related