Unrecognized charge disputes on Stripe: the complete guide
An unrecognized dispute means your customer doesn't recognize the charge on their statement at all. Functionally, it's treated almost identically to a fraud claim, but the underlying cause is frequently different: an unclear billing descriptor, not an unauthorized purchase.
Quick facts
- Response window
- Same 7 to 21 days as any Stripe dispute
- Evidence Stripe weighs most
- A clear billing descriptor match, purchase confirmation, correlating account activity
- Recovra's general read
- Often winnable, and often preventable at the source
What this reason code actually means
Stripe applies this when a customer says they don't recognize a charge on their statement. It's effectively indistinguishable from a fraud claim in how Stripe processes it, even though the underlying reason is often completely different.
Why this happens
- The billing descriptor doesn't clearly match the brand name, so the charge looks unfamiliar on a statement.
- A family member or shared account holder made the purchase without the primary cardholder's direct knowledge.
- Genuine unrecognized fraud, same as the fraudulent category.
- Time has passed since the purchase, and the charge itself has simply been forgotten.
Evidence Stripe accepts for this reason code
- A clear billing descriptor match showing what the charge would have looked like on the statement
- The purchase confirmation email
- Correlating login or session data around the time of purchase
- Customer purchase IP address and device data, similar to a fraud claim
The mistakes that lose this type of case
- Not addressing the billing descriptor directly, when it's frequently the actual root cause.
- Treating this identically to a fraud case without checking whether a descriptor fix would prevent the next one entirely.
- Submitting a purchase confirmation without any account activity data to correlate it to the actual cardholder.
- Missing the opportunity to fix the descriptor after a pattern of this reason code recurs.
An illustrative example
How Recovra handles unrecognized disputes
Recovra checks purchase and account data the same way it would for a fraud claim, since Stripe treats them almost identically. Where the evidence supports the charge being legitimate, we build and submit that case. Where a pattern points to a descriptor problem, we'll flag that directly, since it's a fix that prevents future disputes rather than just resolving the current one.
Request your free dispute auditFrequently asked questions
Is this the same as a fraud dispute?
Stripe processes it almost identically, but the underlying cause is often different, most commonly an unclear billing descriptor rather than actual fraud.
How do I check what my billing descriptor actually looks like?
It's visible in the Stripe dashboard settings, and worth checking against how the brand name would appear to someone scanning a statement quickly.
Can fixing the descriptor really reduce future disputes?
Yes, when the descriptor is the actual cause. It won't touch genuine fraud, but it addresses the most common non-fraud driver of this reason code.
If an unrecognized charge dispute is sitting in your dashboard right now, the free audit will tell you honestly whether it's worth fighting.
Request your free dispute audit