What it means
The cardholder saw your charge on their statement, didn't recognise it, and asked their bank to reverse it. On Stripe the dispute shows the reason Unrecognized. For card payments it usually comes from Mastercard 4863 (Cardholder Does Not Recognize: Potential Fraud) or an American Express unrecognised-charge code such as 176. Visa has no separate code; it files these as fraud.
Stripe describes it as effectively indistinguishable from a Fraudulent dispute, and the evidence is the same.
Why software, course and membership customers file it
Most unrecognised charges aren't fraud. They're confusion:
- The statement descriptor doesn't match the product. The customer bought "Growth Marketing Course" but the statement says the name of your company or payment processor.
- An annual renewal. A year later, the customer has forgotten they signed up.
- Someone else in the household or team bought it with the cardholder's card.
What wins it
Show that the cardholder, or someone they authorised, made the payment and used the product:
| Evidence | Stripe field |
|---|---|
| The customer's name, email and IP address at checkout | customer_name, customer_email_address, customer_purchase_ip |
| Logins and use after the payment, with time, IP and device | access_activity_log |
| Messages with the customer, such as their onboarding questions or thanks | customer_communication |
| A summary linking the statement descriptor to your product, and earlier undisputed payments | uncategorized_text, uncategorized_file |
Two things matter more here than in other disputes:
- Explain the descriptor. State plainly what the cardholder would see on their statement and which product it was for. Banks often decide unrecognised charges on exactly this.
- Earlier renewals. If the same card paid you before without a dispute, say so with dates and amounts.
If the dispute arrives as an inquiry (Stripe marks it needs response, before any money moves), respond to it. A good answer can stop it becoming a chargeback. Accepting an inquiry doesn't close it.
What doesn't work, and when to accept
- A receipt on its own, without showing who used the account.
- Screenshots of your website, without anything tying the cardholder to the purchase.
If nothing links the cardholder to the account (no usage, no matching IP, no earlier payments), accept the dispute and save the counter fee.
Preventing the next one
- Set a statement descriptor customers recognise, such as your product's name or website.
- Send receipts, and remind annual customers before they renew.
How Flatfight handles it
Flatfight builds the same proof as for a fraud dispute: your product activity matched to the customer, the checkout IP and card checks from Stripe, earlier undisputed payments, and the customer's own messages if you connect your support inbox. The summary names the product behind the charge in plain words, so the bank can see what the cardholder bought.
FAQ
Is "Unrecognized" the same as fraud?
For the evidence you send, yes. The difference is the claim: the cardholder isn't sure what the charge is, rather than saying their card was stolen.
Should I contact the customer?
Yes, if you can do it respectfully. Many customers withdraw the dispute once they recognise the charge. Keep a record, and include it in your evidence if the dispute stays open.