Visa 10.4 — Other Fraud — Card-Absent Environment
"I don't recognise this charge" on a digital product
By Byron Kiriibwa · Updated
When a customer says they don't recognise a charge for a digital product, it usually comes through as fraud: Visa 10.4 or Mastercard 4837. The question is who made the purchase. The bank looks for 3D Secure, links to earlier undisputed payments, the same device or account, and whether the cardholder used what was bought.
The bank's test
The bank checks:
- Was the payment authenticated with 3D Secure? If so, fraud liability usually sits with the card issuer.
- Does anything link this cardholder to the seller: earlier undisputed payments, the same IP address or device, the same account or email?
- Did the purchase go somewhere the cardholder controls: their billing address, their email, their login?
- Did the cardholder use what was bought?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| 3D Secure authentication | If the payment was authenticated. | State that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank. | Stripe: Uncategorized text. There's no field of its own: for a payment that shifts liability, Stripe adds the 3D Secure result itself, so mention it in your letter.Square: Authorization documentation | Every seller |
| Earlier payments from the same customer | Showing the same customer paid before without disputing. | List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account). | Stripe: Uncategorized textSquare: Related transaction documentation | Every seller |
| Customer IP address and device | Showing the IP address or device matches earlier activity. | Give the purchase IP and show the same IP or device on logins or earlier orders. | Stripe: Customer purchase IPSquare: Cardholder information | Every seller |
| Customer account history | Showing the account is tied to the cardholder's email. | Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform. | Stripe: Uncategorized file or Uncategorized textSquare: Cardholder information | Every seller |
| Messages with the customer | Showing messages from the cardholder's email about this order. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
| Address and security-code checks | Showing the address and security-code results, as supporting detail only. | Report the check results as Stripe recorded them. Supporting evidence only, never the main argument. | Stripe: Uncategorized text. There's no field of its own: mention the address and card code results in your letter.Square: Authorization documentation | Every seller |
| Access granted or digital product delivered | Showing it was sent to the cardholder's email. | The delivery or welcome email, or the platform record showing when access was granted and to which email. | Stripe: Access activity log or Customer communicationSquare: Online or app access log | Courses, memberships, digital products |
| Access and usage log | Showing use from the same IP address or device as the purchase. | Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export. | Stripe: Access activity logSquare: Online or app access log | Courses, memberships, digital products |
What doesn't help
- An address or security-code match on its own; it shows the buyer had the card details, not that they were the cardholder.
- Proof of delivery to an address, email, or account with no link to the cardholder.
- Arguing that the product was good. In a fraud dispute the question is who made the purchase, not its quality.
Visa's rules for 10.4
- Compelling Evidence 3.0 (Visa 10.4 only): at least two earlier transactions on the same payment method, paid and undisputed (not validation charges), 120–364 days before the disputed one, all processed by Stripe. They must match the disputed transaction on two main elements (purchase IP; device fingerprint or device ID, not both) or one main plus one secondary (shipping address, email address, customer account ID). Source: Stripe docs, checked 2026-10-06.
- Visa's own CE 3.0 rule (Visa Core Rules and Visa Product and Service Rules, 24 October 2026, section 11.8.5.3; read 2026-10-29): for disputes processed from 24 October 2026, the two earlier undisputed transactions on the same card (or a token for it) may have been at one or more merchants, processed more than 120 days before the dispute was submitted and no more than 365 days before it. Device ID and device fingerprint count as one element, not two. Stripe can show only payments it processed for this seller, so its eligibility check stays the one to follow.
- 3D Secure: if the payment was authenticated, liability generally shifts to the issuer. Stripe adds the authentication result (ECI) to the evidence automatically. Visa doesn't allow 10.4 for a payment authenticated with Visa Secure (ECI 5 with a CAVV), or for an attempted authentication (ECI 6 with a CAVV) unless the card is a non-reloadable prepaid card.
- Other cases where Visa doesn't allow 10.4: the issuer approved the payment although the CVV2 was entered and didn't match; the issuer had already reported the card for fraud when it approved the payment; or the issuer has raised more than 35 disputes on the card in the past 120 days (from 24 October 2026 Visa counts them per payment credential, so a token for the card counts too).
- Other Visa fraud codes in the same Stripe category: 10.1, 10.2, 10.3 (card-present, chip), 10.5 (Visa monitoring programs).
- If the issuer challenges the seller's compelling evidence at pre-arbitration and any contact detail the seller gave matches the cardholder's on the issuer's records, the issuer must say it contacted the cardholder about the evidence and explain why they still dispute. So give every detail that matches the cardholder: full name, billing or shipping address, phone, email. For digital goods, Visa's compelling evidence asks for the date the goods or services were provided (it said downloaded before), which fits access and use records. Source: Visa Core Rules and Visa Product and Service Rules (24 October 2026), sections 11.3.2 and 11.6.1; read 2026-10-29.
Common mistakes with Visa 10.4, Mastercard 4837
- Sending delivery proof without explaining how the recipient connects to the cardholder.
- Not collecting IP address, device, and email at checkout, so there is nothing to link the purchase to the cardholder.
- Ignoring an authentication result that would have settled the dispute.
Should you fight it?
Fight it when your records tie this cardholder to the purchase: 3D Secure, earlier payments they didn't dispute, the same account or device, and use of what was bought. A confusing statement name is a common cause, so check that first. Accept it when any of these is true:
- No authentication and nothing at all linking this cardholder to any earlier activity.
- Goods shipped to an address unrelated to the cardholder, with no other link.
- Digital access granted but never used, and nothing else ties the cardholder to the purchase.
- The seller suspects the order really was fraud. Accepting also avoids paying to fight a case that should be lost.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Use 3D Secure for risky or high-value online payments (Stripe Radar rules can require it).
- Collect email, billing address, IP address, and device data at checkout (Stripe Checkout or Stripe.js does this).
- Deliver digital products through a login tied to the buyer's email, and log access.
- For high-value goods, ship only to the billing address or a previously used address, with signature on delivery.
- Use a statement descriptor customers will recognize.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
A customer buys a $19 monthly app subscription with the same card they've used for eight months without a dispute. In June they dispute the charge as unrecognised. The June payment came from the same device and login as the earlier ones, and they used the app ten times that month.
The response would attach:
- Exhibit A: the eight earlier payments on the same card and account, none disputed.
- Exhibit B: the June payment's device and IP address, matching the earlier ones.
- Exhibit C: the customer's account record, created with their email eight months earlier.
- Exhibit D: their ten uses of the app in June, with dates.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Visa reason code 10.4, for $19.00 charged in June for the customer's monthly subscription. The cardholder made this purchase.
The cardholder has paid us before on the same card without dispute. The same card paid for this subscription eight times before June, and none of those payments was disputed (Exhibit A).
The June payment came from the cardholder's own device and account. Its device and IP address match the earlier payments (Exhibit B), and it was made from the account the customer created with their email eight months ago (Exhibit C).
The cardholder used what was bought. The account used the app ten times in June, after the payment (Exhibit D).
The cardholder has a history of undisputed payments, made this one from their own device and account, and used the subscription. We ask that the dispute be decided in our favor.
Questions people ask
Why would a real customer not recognise our charge?
Often the name on their card statement doesn't match your brand or website. Check what your statement descriptor shows; a clearer one prevents many of these.
Does an address or security-code match prove it was them?
Not on its own. It shows the buyer had the card details. Links to the cardholder, such as earlier payments, their account and device, carry more weight.
What is 3D Secure and why does it matter?
It's an extra check by the card issuer at checkout. When a payment passed it, fraud liability usually sits with the issuer instead of you.
When should we accept a fraud dispute?
When nothing links the cardholder to the purchase, or you suspect it really was fraud. Accepting then avoids paying to fight a case that should be lost.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.