The invoice was paid on time. The final files went out on a Tuesday. The client replied with a thumbs-up emoji and launched the new brand the following week. Twenty-three days later, the money disappeared from the photographer's Stripe balance — a dispute, reason: services not provided. The logo was, at that exact moment, printed on the client's storefront window.

If you sell physical products, a chargeback is a logistics argument. There's a box, a label, a carrier scan, a doorbell camera. If you sell services — design, coaching, consulting, photography, development, repairs — a chargeback is an argument about something that no longer exists anywhere except in its results. You can't return six rounds of revisions. You can't restock a strategy session. The work is gone, absorbed into the client's business, and the bank is now asking you to prove it ever happened. Most service providers lose this argument not because they didn't do the work, but because doing the work is the only thing they can prove they did — and that, strangely, is not enough.

The economics of work nobody can inspect

Economists have a useful vocabulary for this problem. In 1970, Phillip Nelson drew a distinction between search goods — things whose quality you can evaluate before buying, like a chair you can sit in — and experience goods, whose quality only reveals itself after purchase, like a restaurant meal. A few years later, Michael Darby and Edi Karni added a third category: credence goods, whose quality the buyer can't fully evaluate even after consuming them. Was the consultant's advice good? Was the mechanic's repair necessary? Was the SEO work competent? The customer often can't tell — and neither can anyone else looking in from outside.

Almost everything a service business sells lives in the experience and credence categories. That's not a flaw in your business; it's the structural reality of selling expertise and labor instead of objects. But it has a brutal consequence in a dispute: there is no neutral, physical fact the outcome can hinge on. Nobody can inspect the product, because the product is a process that already finished.

Which means service disputes are never really decided on the quality of the work. They're decided on the quality of the record of the work. Documentation isn't paperwork around the product. For dispute purposes, documentation is the product.

The reviewer has even less to see than the client does

Here's who actually reads your evidence: an analyst at the cardholder's bank, working through a queue, who has never met you, never seen your work, and will spend a few minutes on your case. They see three things — the charge, the cardholder's claim, and whatever packet you submitted.

When a merchant ships a package, the payments system hands them a ready-made artifact for exactly this moment: the tracking number, an institutional, third-party record designed to prove a physical fact to a stranger. Service businesses get no default artifact. Nothing in your normal workflow automatically generates proof that a stranger at a bank would find persuasive. If you want the equivalent of a tracking number, you have to manufacture it yourself — deliberately, at the time of the work, because you cannot manufacture it honestly afterward.

One more thing about that reviewer: they're checking your evidence against a specific claim. "Services not provided" (Visa's reason code 13.1, and its cousins on other networks) asks one question — did the service happen? Not: was it good, was it worth the price, was the client happy. Merchants routinely lose winnable service disputes by defending quality when the code only asked about existence. Ten paragraphs about your creative process bury the two exhibits that answer the actual question.

The three-beat record: agreed, delivered, acknowledged

Every service dispute that gets won is won on some version of the same three-beat structure. Think of it as the narrative a stranger needs in order to believe invisible work occurred.

Beat one: they agreed to this. A signed proposal, a checked box on your booking form, an email that says "yes, let's proceed with the scope below." It needs to exist before the work starts, name the buyer, and describe what they're buying in plain words. A verbal agreement followed by an invoice is where most freelancer chargeback disputes are already lost — the reviewer sees a charge with no evidence the cardholder asked for anything.

Beat two: you delivered it. Timestamped artifacts of the work moving from you to them: the email with the final files attached, the shared-folder access log, the calendar invites for the sessions that happened, the staging-site handoff, the project-management thread showing milestones closing. Dates matter more than volume. Three timestamped exhibits that line up with the invoice beat thirty screenshots that don't.

Beat three: they received it and behaved like a satisfied customer. This is the beat service providers skip, and it's often the decisive one. A reply saying "these look great." A request for one more small tweak — which proves engagement with the deliverable. And the quiet killer: evidence they used the work. The website you built, live at their domain. The photos you shot, posted to their Instagram. The logo in their window. A cardholder who claims a service was never provided while publicly operating on top of that service has contradicted their own dispute, and reviewers notice.

Why silence loses disputes

The gap in most service workflows is beat three, and the reason is understandable: once the work ships and the client goes quiet, following up feels like fishing for compliments — or worse, inviting criticism. So merchants let silence stand, and privately file it under "no news is good news."

A dispute reviewer reads the same silence in the opposite direction. No confirmation on file means the merchant's story ends at "I sent it," and the cardholder's story — "I never got what I paid for" — fills the vacuum. The fix is structural, not personal: build the acknowledgment into the process so it doesn't depend on anyone's mood. End every delivery with a question that requires a reply ("Can you confirm these open correctly on your end?"). Make milestone sign-off a step in the project, not a favor. You're not fishing for praise; you're generating the artifact your business model doesn't generate on its own.

Your next moves

  • Put a checkbox on your intake today. Whatever you use to book work — form, proposal tool, contract — add an affirmative step where the client confirms the scope in writing before payment. If a current project started without one, send a recap email now: "Confirming we're doing X for $Y — reply yes and I'll proceed to the next milestone."
  • Rewrite your delivery email as a template that demands a reply. Attach or link the deliverable, list what's included, and close with a direct question the client must answer. Save it as a snippet so every future handoff produces an acknowledgment artifact automatically.
  • Pick one timestamped home for milestones and use it consistently — sent email, project tool, shared folder. The test: could you show a stranger dated proof of each phase without reconstructing anything from memory?
  • The day a dispute lands, screenshot public use of your work — their live site, published photos, the campaign running on your copy. Capture it with visible dates and URLs before anything gets taken down.
  • Build a one-page timeline template now: date, event, exhibit number. When a dispute arrives, you fill in rows instead of drafting a defense from scratch at midnight — and the reviewer gets the three beats in thirty seconds.

When the deadline is shorter than your week

Everything above assumes you'll have the time and composure to assemble the packet when the dispute hits — and Stripe gives you roughly seven days, usually in the middle of client work that can't pause. That's the gap Argeback closes. It ingests your Stripe disputes the moment they're filed, drafts an evidence-backed response built around exactly this structure — agreement, delivery, acknowledgment — and files it before the deadline, all from your phone. The record of your work is yours to build; getting it in front of the bank on time shouldn't cost you a week of it. See how it works at argeback.lumenlabs.works.