Unrecognized charge disputes on Stripe: the complete guide

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.

• 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.

• 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

• 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.