Picture a client you've worked with for eight months. The calls are friendly. The invoices get paid. Then one morning a Stripe notification says their card was disputed, for the full amount, with the reason "unrecognized."

You reread the last email thread, looking for the thing you did wrong. There isn't one. The person you work with is not the person who disputed.

That gap explains most business-to-business chargebacks, and it's what you have to close to win them.

The buyer and the payer are different people

In a consumer dispute, one human usually did both things: bought the item and looked at the statement. In a business, those jobs are split.

Your contact, say a marketing lead, approved the work and handed over a company card. Weeks later, someone in finance reconciles the card statement. That person sees a line item with your billing descriptor and a dollar amount. They weren't in the kickoff call or on the email thread, and they never saw the proposal.

So they do what they're trained to do with something they can't match to a record: they flag it. Sometimes they call the card issuer to dispute it. The card network's category for this is often fraud or "unrecognized," because that's the closest box available. It doesn't mean your client thinks you're a thief. It means the left hand never told the right.

Economists call this a principal-agent problem. The company (the principal) delegates spending to an employee (the agent), and the information the company needs to evaluate that spending stays with the agent. The dispute is what that information gap looks like on a ledger.

Why this changes how you build your response

The reviewer deciding your case is also a stranger. They see a charge, a claim that the cardholder didn't authorize it, and whatever you submit. Your job is to supply the missing link between the finance person's confusion and the employee's decision.

That means your evidence should answer one question in plain terms: who at this company agreed to this, and when?

A generic receipt doesn't answer it. A proof-of-service log doesn't either, at least not alone. What works is anything that ties a named individual at the client organization to the purchase.

Evidence that closes the gap

Start with the paper trail that names people, not just amounts.

The signed or accepted order form. If your client clicked "accept" on a proposal or signed a statement of work, you have a timestamped agreement with a name attached. That is worth more than any amount of usage data.

Email from a company domain. A message from someone at the client's own domain, saying "yes, go ahead" or "here's the card to use," shows the purchase was knowingly made on behalf of the business. Include the full header or a clean screenshot with date and sender visible.

The invoice with their reference numbers. If the client issued a purchase order, the PO number on your invoice is a quiet but strong signal. Companies generate POs through an internal approval process. A matching number means the spend went through their own system.

Proof the work was delivered and received. Meeting notes, deliverables sent, a thread where they gave feedback on the work. If they reviewed it and asked for revisions, they used it.

A record of payment-method use. If the same card paid prior invoices and nobody disputed them, say so. A history of undisputed charges on the same card is relevant context, and Stripe's own guidance on repeat customers supports leaning on it. Be accurate about what it shows. It shows the card and the relationship are established, not that this specific charge was approved.

Then put the story at the top, in a few lines, written for a reviewer who has never heard of you. Name the client contact, the date they accepted, and what was delivered. Keep it factual and calm.

The fastest fix is not always a fight

Before filing anything, consider a short email to your actual contact.

Something like: "Our payment processor shows your finance team disputed the charge for invoice 1042. I think it may be a matching issue on their end. Could you let them know it's the March project you approved?"

If the dispute is a mix-up, your contact can talk to finance, finance can call the issuer, and the dispute may be withdrawn. You can also forward that response as evidence that the buyer acknowledged the purchase, if they reply in writing.

Two cautions. A withdrawal isn't guaranteed, and it doesn't change the clock: the evidence deadline keeps running regardless of what's happening in your inbox. Stripe shows the due date on each dispute, and it's often about a week out, so treat the email as a parallel track, not a substitute for filing. Also, ask your contact in a way that doesn't sound like you're pressuring them. They may be embarrassed that their own finance team flagged their purchase, and that embarrassment is manageable if you're gracious about it.

Prevention: make your charge recognizable to someone who wasn't there

Most of this is avoidable, because the root cause is a charge that finance can't identify.

  • Put the client's company name and a project or PO reference on every invoice and receipt, not just the amount.
  • Check that your billing descriptor looks like your business name, not a processor code.
  • Send receipts to a billing contact in addition to the buyer, if the client will give you one.
  • For large or first-time engagements, ask who will see the statement, and tell that person what the charge will look like.

None of these requires more than a few minutes. Each one removes a reason for a stranger to wonder whether the charge is real.

Your next moves

  • Today, open your last three business-client invoices. Check whether each one includes the client's company name, a reference or PO number, and your trading name as it appears on card statements. Fix the template if any is missing.
  • Search your inbox for the written "yes." For every client currently on a recurring or high-value engagement, find the email or signed form where someone at their company agreed. Save it in the client's folder so it takes seconds to find later.
  • Add a billing contact to your onboarding. One question: "Who in your finance team should receive receipts?" Add that person to the invoice emails.
  • Check your Stripe descriptor. In your Stripe settings, confirm the statement descriptor matches what clients know you as. Send yourself a test charge if you're unsure how it renders.
  • If a dispute is open now, write the opening summary first: client contact's name, date of agreement, what was delivered. Then attach only the documents that support those three facts, and file before the due date shown in your dashboard.

Where Argeback fits

The hardest part of a B2B dispute isn't the argument. It's remembering where the proof of one person's yes lives, and assembling it in a matter of days while you're also running the business. Argeback pulls your Stripe disputes into one place, drafts a response built around the evidence you actually have, and files it ahead of the deadline from your phone. If you'd rather not dig through email threads at the end of a long day, you can see how it works at argeback.lumenlabs.works.