“I don’t recognize this charge”: disputes after a completed service

What actually happened

The client came in. The work got done. The card was charged. Weeks later, the client looks at a statement, sees a name they don’t know, and tells their bank: “I don’t recognize this.” Or worse: “I didn’t make this charge.”

It’s the most frustrating dispute a service business gets, because you know they were there. The bank doesn’t. It only knows its own customer says the payment wasn’t theirs.

Sometimes it’s an honest mix-up. A spouse booked the appointment. The charge posted days later. The statement shows your company’s legal name instead of the name on your sign. Sometimes it’s not honest at all. More on friendly fraud.

How the bank files it

An unrecognized charge usually lands as a fraud dispute. On Visa that’s 10.4, Other Fraud – Card-Absent Environment, when the card wasn’t present (a card on file, an online booking, a phone payment), or 10.3 when it was. Visa’s 10.4 reason is simple: the cardholder “denies authorization of or participation in” the transaction. On Mastercard, it’s 4837, No Cardholder Authorization.

Processors label it their own way. Stripe has both Fraudulent and Unrecognized, and says the second is effectively indistinguishable from the first. Square calls these unauthorized charges.

Two rule details worth knowing:

• The bank must report it as fraud first. Before filing a 10.4 dispute, Visa requires the issuer to report the fraud activity to Visa. So a customer who “just didn’t recognize it” has, on paper, reported fraud.
• 120 days. Visa gives the bank 120 days from the payment to file a 10.4 dispute.

Sometimes it starts as a question. On American Express and Discover especially, the bank may first send an inquiry asking what the charge was for. Stripe says this often happens because the cardholder doesn’t recognize the transaction description. Answer fast. Ignored inquiries can turn into chargebacks you can’t win. Chargebacks versus inquiries.

What proof matters

A fraud claim is about who, not what. One general line: show that the cardholder, or someone they authorized, made the payment and received the service. A great result doesn’t answer a fraud claim. Proof of the person does.

Processors’ own help pages point the same way. Square mentions signed receipts in person and earlier undisputed payments with the same card online. Clover mentions proof that the person who paid is someone the cardholder knows, such as a member of their household.

Repeat clients are an advantage. For Visa card-absent fraud disputes, a program called Compelling Evidence 3.0 lets merchants point to earlier undisputed payments from the same customer. Stripe checks eligibility on 10.4 disputes and flags it. A client with a payment history is much harder to call a stranger.

Stop these before they start

• Fix your statement name. Stripe’s advice: make the descriptor easy to recognize, matching the business name customers associate with the purchase.
• Send receipts. A receipt in the inbox the day of the visit answers “what is this?” before the bank ever hears the question.
• Take chip or tap in person. Square recommends it to lower the chance of a fraud dispute.
• Warn before charging a card on file. A text saying “we’ll charge the card ending 1234 for today’s visit” takes seconds.

Mistakes that lose these disputes

• Arguing quality. The customer isn’t saying the service was bad. They’re saying it wasn’t them.
• Sending records with someone else’s name and no link to the cardholder.
• Calling the customer a liar. Stick to records. The reviewer decides.
• Waiting for the customer to call back. They might withdraw the dispute. The deadline doesn’t wait, and a missed one is an automatic loss.
• Refunding after the chargeback. The bank already took the money back.

Dispute Daddy builds the response from your dispute notice and your own records, and you review and submit it to your processor yourself. See how Dispute Daddy builds it for you.