What Visa reason code 10.3 means
Issuers use 10.3 for card present fraud claims that are not covered by the EMV liability shift codes 10.1 and 10.2. The typical case is a transaction where the card was not electronically read: the number was keyed manually, there was no chip or contactless data, and no imprint proves the card was present. When the chip or contactless interface was read and authorized, the issuer generally cannot use 10.3, so the entry mode is the first thing to check.
Typical triggers for a 10.3 chargeback
-
Key entered transactions at the counter after a card fails to read.
-
Phone or mail orders run on a card present terminal, which mislabels a card absent sale.
-
Hotel, car rental or venue charges keyed in at checkout without the card in hand.
-
A family member using the card in store without the cardholder knowing.
Time limits for Visa 10.3
The cardholder typically has 120 days from the transaction date to dispute. Your response window is set by your acquirer or processor and is often between 7 and 21 days. Pull receipts and terminal logs right away.
Evidence that wins a 10.3 dispute
-
Terminal records showing the chip or contactless interface was read and the transaction was authorized.
-
For key entered sales, a manual imprint of the card or other proof the card was physically present where your acquirer accepts it.
-
A signed receipt or rental agreement, and a copy of photo ID checked at the counter if your policy allows it.
-
Proof the cardholder received the goods or service, such as a hotel folio with the guest name, a registration or a delivery to the cardholder.
-
Prior undisputed purchases by the same customer at your business.
-
Proof that a refund was issued before the dispute.
What to avoid when you respond
-
Do not rely on a signature alone for a keyed transaction. Issuers want proof the card was present.
-
Do not include full card numbers on copies of receipts or imprints.
-
Do not run phone orders as card present sales to save on fees. They lose card present protections and invite fraud codes.
How to prevent Visa 10.3 chargebacks
-
Always try the chip or tap before keying a card number.
-
If a card cannot be read, ask for another card instead of keying it.
-
Process phone and mail orders as card not present, with AVS and CVV checks.
-
Use a clear statement descriptor with your brand and city so cardholders recognize the charge.
-
Ask for ID on high value in store purchases.
How 10.3 appears in Stripe
For Stripe merchants 10.3 comes from in person payments taken with Stripe Terminal. Stripe shows it with the reason fraudulent and the network reason code field carries 10.3. NoChargeback reads the card present details on the charge, collects receipts and customer history, and fills the evidence fields for you. See Stripe chargeback protection.
Rebuttal letter opening for Visa 10.3
We are responding to the dispute filed under Visa reason code 10.3. The card was present at the time of the transaction: the chip was read at our EMV terminal and the transaction was authorized, as shown in the attached terminal record. The cardholder also received the service described in the signed receipt below.
Can a merchant win a Visa 10.3 chargeback?
Yes, when you can show the card was physically present. Chip or contactless data, an imprint for keyed sales and proof the cardholder received the goods are the strongest evidence.
Is a signature enough to fight 10.3?
Usually not. A signature supports your case, but issuers look first for chip, contactless or imprint data proving the card was present.
Does 10.3 apply to online orders?
No. Online and phone order fraud claims use Visa reason code 10.4. A 10.3 on a card not present sale suggests a processing error worth checking.