Transaction unrecognized chargebacks: fix the descriptor first

What the bank was told

The cardholder looked at their bank statement, did not recognize the charge, and asked their bank about it. The bank filed a dispute to find out. Nobody has firmly claimed theft yet, which is exactly what makes these winnable with the right evidence.

Often triggered by an unfamiliar billing descriptor on a bank statement. First verify your Stripe/Shopify billing descriptor is recognizable. If the descriptor is clear and you have login + delivery evidence, these disputes are contestable. If you believe it is true fraud, skip the dispute.

How the bank actually decides it

The analyst wants a story that ties their cardholder to the purchase: the confirmation email went to the cardholder's address, the account that placed the order carries their name and login history, the delivery went to their home.

Identity linkage decides this code. Product quality and refund policies are beside the point. The question is whose purchase this was, and every link you can show makes 'I don't recognize this' harder to sustain.

The evidence that decides it

Order confirmation email sent to cardholder's email address
Login records showing account access from the cardholder's device/IP
Billing descriptor matching your store name (check this first)
Delivery confirmation to the cardholder's address
Customer service interactions post-purchase
IP address and device data at time of purchase

Your first hour after it lands

Read your own billing descriptor first

Open your payment settings and look at the exact string cardholders see on a statement. If your store is Sunset Candle Co and the descriptor is a holding-company name, you have found the cause of this dispute and probably the next one.

Assemble the identity chain

Order confirmation sent to their email, account login records, the delivery address, any support contact. Each link ties the cardholder to the purchase.

Judge whether this is actually fraud

If the identity chain comes up empty and the order pattern looks like a stolen card, treat it under the fraudulent code's rules instead: fight only with Compelling Evidence 3.0 history or 3D Secure.

One response only

A dispute response locks the moment it is submitted, yours orShopify’s automatic one, with no edits after. Whatever goes in first is your whole case, which is why the first hour matters more than the last day.

Preventing the next one

Set the billing descriptor to your customer-facing store name
Send order confirmations immediately, from a sender name customers recognize
Charge under the same brand you market under, everywhere

Questions merchants actually ask

How is this different from a fraudulent-code dispute?

Unrecognized means the cardholder is unsure. Fraudulent means they are asserting theft. Unrecognized disputes are winnable with identity evidence, and banks sometimes drop them once the cardholder recognizes the purchase. If the bank becomes convinced it was theft, it can refile under the fraud code.

What single fix prevents most of these?

The billing descriptor. An unrecognizable statement line is the classic trigger for this code, and it is fixable in your payment settings in minutes.

What does Backstop do with these?

It assembles the identity evidence it can see in your order data, confirmation email address, delivery address, customer history, into the evidence pack, with this code's guidance beside it and deadline emails at 7, 3, and 1 day.

Where Backstop fits

Backstop assembles the identity chain your order data already contains, the confirmation email, the addresses, the customer's history with your store, into a single evidence pack, and flags the deadline so the response window never closes on you quietly.

Transaction Unrecognized disputes, handled plainly