Somewhere in a client's inbox, there is an email from you. It has a subject line, a polite greeting, a blue button that says Pay invoice. It was delivered at 9:14 on a Tuesday morning, opened for about four seconds, and then it sank beneath forty other messages. Three weeks later the client's card statement shows a charge they don't recognize, and they do the reasonable-seeming thing: they call the bank and say, "I never got an invoice."
They may be entirely sincere. That is the uncomfortable part. In a Stripe invoice chargeback, the customer is often not lying. They are just remembering an email the way most of us remember emails, which is barely at all.
Your job isn't to prove they're wrong about their memory. It's to show a reviewer, in a few clean lines, that the invoice existed, reached them, was seen, and was paid by someone who had every reason to know what it was for.
Why "I never received it" is such a common claim
An invoice is a low-attention object. It arrives in a stream of messages the recipient is skimming, and the brain is very good at discarding what it has filed as routine. Psychologists call the broader pattern habituation: repeated, unremarkable stimuli stop registering. A "please pay this" email from a vendor you've already agreed to work with is about as unremarkable as stimuli get.
Then there's the gap. The customer pays, perhaps by clicking through on their phone, and weeks later sees a line on a statement with a billing descriptor that doesn't ring a bell. The memory of the transaction and the memory of the charge never got linked. When people can't retrieve a memory, they tend to conclude it didn't happen, and "I never got an invoice" is the natural expression of that.
This matters for how you respond. If you treat the claim as an accusation of fraud on their part, your evidence will read as combative. If you treat it as a gap in recall that your records can fill, your evidence will read as what it is: a calm reconstruction.
What the dispute is really asking
When a customer says they didn't receive an invoice, the underlying dispute is usually one of two kinds, and the reason code the bank assigns tells you which.
If the claim is unrecognized or fraudulent, the question is whether the cardholder authorized this payment. If the claim is closer to product not received or not as described, the question is whether you delivered what the invoice was for. The missing invoice is just the story wrapped around either one.
So the invoice itself is rarely your whole case. It's the thread that ties together three things the reviewer needs to believe: there was an agreement, there was a request for payment, and the person paying knew what they were paying for.
The trail an invoice leaves behind
The good news is that invoices are among the most documented transactions you'll ever process. Each step produces something you can point to.
The invoice record. In Stripe, the invoice has its own page in your dashboard showing the line items, amounts, due date, customer, and the moment it was finalized and sent. Export the PDF. It shows exactly what the customer was asked to pay and for what.
The email delivery. Stripe can email invoices to customers, and the invoice's activity shows when it was sent. Check what the dashboard shows for the delivery to the address on file. That address matters: if it matches the email the customer used for earlier correspondence with you, that's a quiet but real piece of evidence.
The hosted invoice page. If the customer paid through Stripe's hosted invoice page, the payment didn't happen by magic. Someone opened a page, saw the line items, entered or selected a card, and confirmed. Where available, the payment details can include the IP address and device information associated with that session. Be careful with this one: an IP address shows where a session came from, not who was sitting there, so use it to corroborate (for example, that it matches earlier logins or past orders), never as proof of identity on its own.
The receipt. If a receipt was emailed after payment, that is a second message to the same address, this time confirming the amount and your business name. Two touchpoints are harder to wave away than one.
The surrounding conversation. The strongest invoice evidence is often not the invoice at all. It's the email thread where the customer said "yes, send it over," the signed quote, the Slack message asking when the invoice would arrive, or the follow-up asking about the work you delivered after they paid.
The sequence a reviewer can follow
Reviewers read a lot of disputes. They reward evidence that tells a story in order, and they punish piles. Build a short chronology, a single page if you can:
- The date of the agreement, with the quote, contract, or message that shows it.
- The date the invoice was created and sent, and to which address.
- The date the hosted page was opened and the payment completed.
- The date the receipt went out.
- What you delivered, and when.
- Any contact from the customer after payment that treats the transaction as normal.
Each line should reference an attached exhibit by name. You are not arguing; you are indexing.
What not to say
Resist the urge to write "the customer is lying." You don't know that, and it doesn't help. A line like "Our records show the invoice was sent to the address below on this date and paid through the hosted payment page on this date" does more work than any adjective.
Also resist overclaiming about email. A delivery record shows your system handed the message off; it does not prove the person read it. Say what the record shows and no more. Reviewers notice overreach, and it makes your solid evidence look softer by association.
When the invoice really was missed
Sometimes the honest finding is that the invoice went to an old address, a shared inbox no one checks, or a spam folder. If that's the case, don't hide it. The question then becomes whether the customer still agreed to the purchase and received the value. If there's a signed agreement, delivered work, and later correspondence that treats the service as ongoing, you can still make a strong case without leaning on the email at all.
And if the facts are against you, say, you billed for work that wasn't agreed, then the right move may be a refund rather than a fight. A dispute you shouldn't win isn't a good use of anyone's time.
Your next moves
- Open one recent paid invoice in Stripe today and look at what it records: sent time, recipient email, payment time, receipt. Know what your own trail looks like before you need it.
- Confirm the billing email on your top ten customers matches the address they actually use with you, not a legacy one from signup.
- Turn on receipt emails if they aren't already, so every payment produces a second, separate message to the customer.
- Add a one-line reminder to your invoice emails naming the project and the agreed amount ("Invoice for the October website redesign, as quoted on Oct 3"), so the email itself ties payment to the agreement.
- Save the quote or approval message into the same folder or note as the invoice for every job over a threshold you choose, so you can assemble a chronology in minutes rather than hours.
Where a little help earns its keep
The hard part of invoice disputes isn't the evidence. It's that the deadline is seven days away, the data lives in four places, and you're answering from your phone between other things. That's the gap Argeback was built for: it pulls the dispute and the surrounding records into one place, drafts a response that follows the chronology a reviewer expects, and files before the clock runs out. If you'd rather not rebuild that page from scratch each time a customer forgets an email, you can see how it works at argeback.lumenlabs.works.