Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
When a customer says a charge is unauthorized, check if a dispute is already open. Then learn if it is real fraud, a charge they don’t recognize, or a family purchase. Refund real fraud fast. Fight only when your records tie the buyer to the card, such as Visa CE3.0 history or 3D Secure.
Written by Chargeflow Experts. Updated 12 November 2026.
Use the order and payment IDs to find the charge. Ask simple, factual questions through your normal support channels, and save the customer’s account of what happened. Never ask for a full card number or security code in a support chat.
| Record | What It Helps Establish | Important Limit |
|---|---|---|
| AVS or CVC result | If the details entered passed the check. | A match does not show who typed them. |
| 3D Secure result | The login result and if fraud liability may shift. | Check the real result and any exceptions. |
| Account and device history | If the account was used the normal way or changed. | A known account can still be taken over. |
| Fulfillment | What you shipped or provided. | Delivery alone does not prove the cardholder approved it. |
Stripe’s verification guidance explains the CVC and AVS checks. Treat them as clues, not a yes-or-no test for fraud. A CVC check, for example, does not protect against a stolen physical card.
“Unauthorized” covers three different situations. Each one needs a different reply.
| What really happened | Signs to look for | What to do |
|---|---|---|
| Real fraud, such as a stolen card or account takeover | New device or IP, a changed email or address, rushed high-value orders. | Refund if no dispute is open, stop shipping, and block the account and card. |
| The customer doesn’t recognize the charge | A known customer, a normal order, and a statement name that doesn’t match your brand. | Show the order details and fix your billing descriptor. |
| A family member or employee used the card | A known device or address, with goods used or delivered as normal. | Share the order proof with the customer. If they still dispute, it may be friendly fraud. |
Pre-dispute tools can settle the second and third cases early. Visa’s Order Insight and Mastercard’s Consumer Clarity show the bank your order details while the customer is still asking about the charge.
If the payment is still in your control, decide with your payments team whether to hold the shipment and cancel or refund. If a dispute is already open, answer it through the dispute and do not send a second refund.
Use refund-overlap controls and support and payments ownership to keep the response in one place.
US law caps what a cardholder loses to fraud, so filing a claim costs them very little. Banks also act fast on these claims. Know the numbers before you decide to fight.
Credit card cap
$50
Most a US cardholder pays for unauthorized credit card use under Reg Z.
Debit card caps
$50 / $500
Reg E limits if the debit cardholder reports within 2 business days, or later.
Filing window
120 days
Typical time a cardholder has to dispute under most Visa and Mastercard codes.
Visa VAMP limit
1.5%
Combined fraud and dispute ratio in most regions since April 2026.
The caps come from Reg Z 1026.12(b) and Reg E 1005.6. Because the VAMP ratio counts reported fraud as well as disputes, a refund does not erase a fraud report. Cutting real fraud at checkout still matters.
Read the network and reason code on the notice before you pick evidence. If the notice says Visa 10.4 card-absent fraud, follow that code’s rules. For Mastercard 4837 no cardholder authorization, use the transaction details that code asks for. An approved payment alone does not prove the cardholder approved it.
Stripe’s 3D Secure documentation says liability usually shifts to the issuer when a payment was fully authenticated and later gets a fraud dispute. It is not guaranteed, and it does not cover other dispute types such as product not received.
Apple Pay and Google Pay can give a similar shift through their cryptograms. Learn more in 3D Secure 2.0 and chargeback liability.
For Visa 10.4 fraud disputes, Visa Compelling Evidence 3.0 lets you show the same person bought from you before without disputing. Stripe’s CE 3.0 guide lists the checks:
If the case qualifies, the fraud claim is no longer valid and liability moves to the issuer. Store IP, device and account data on every order so you can use CE3.0 later.
For PayPal cases, see unauthorized-claim guidance. For Google Pay, see the Google Pay dispute guide. To classify a case, use the dispute assessment checklist.
If your evidence supports a challenge, tie each record to the disputed charge and respond before the deadline. If your review backs the customer, refund or accept the dispute. A mismatch or a repeat claim is a reason to look closer, not proof of abuse.
See how to win an unauthorized transaction chargeback, unauthorized transactions and the representment workflow. You can explore Chargeflow’s chargeback recovery and verified Stripe integration for evidence operations.
Follow the payment and case state
Authorized but uncaptured
Look into the claim. Cancel the hold before you capture if it is fraud.
Captured without an open dispute
Check the order, login and refund records before you decide on a refund.
Formal dispute open
Save the claim, check which defenses apply and answer through the dispute. Send no separate refund.
Case closed
Check what next steps, if any, your provider allows.
An approved payment and a delivery do not prove the cardholder approved it. Check which defense fits.
Sample case: the order was delivered, but the customer says their login was stolen. Delivery is proven. Whether the cardholder approved the charge is a separate question. Check the 3DS liability-shift guidance for that payment and the CE3.0 checks above for a Visa fraud case. Neither one applies to every unauthorized claim.
You should refund an unauthorized charge when your review points to real fraud and no dispute is open yet, because a refund avoids dispute fees. If a dispute is already open, do not refund; answer the dispute instead.
Visa 10.4 and Mastercard 4837 are both fraud chargeback codes where the cardholder says they did not authorize the payment. Visa 10.4 covers card-absent sales and can be fought with CE3.0 history, while Mastercard 4837 covers missing cardholder authorization.
A CVC match does not prove the physical card was present or show who typed the details. Treat it as one verification result among several.
3D Secure does not cover every chargeback. Liability usually shifts only for fraud disputes on fully authenticated payments, and even then it is not guaranteed.
You should not block repeat claimants on that fact alone. Check for account takeover, merchant errors and the facts of each claim before you restrict a customer.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.
Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.
Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.