Visa Reason Code 10.3: Card-Present Fraud

What Visa reason code 10.3 means

Reason code 10.3 is Visa’s catch-all card-present fraud code. The cardholder says they didn’t make or authorize the transaction, the transaction was flagged as card-present, and the specific conditions of the EMV liability shift codes (10.1 counterfeit, 10.2 lost or stolen with no PIN) don’t fit.

The most common trigger is a key-entered transaction at a physical location: the chip and stripe both failed, so the clerk typed the card number in. Without an electronic read, there is little proof the real card was in front of you.

10.3 is an allocation code. Your acquirer can accept it or challenge it through pre-arbitration, and Visa may arbitrate if the issuer doesn’t accept the challenge.

Ecommerce note: online and phone orders are card-absent and fall under 10.4 instead. An ecommerce brand only sees 10.3 from its in-person channels: a flagship store, trade-show booth or pop-up.

Common causes

• Key-entered sales after a chip or stripe read failure, with no imprint taken
• Stolen cards used where staff don’t check the card or the buyer
• Family members or acquaintances using the cardholder’s card in person (often friendly fraud)
• Hotel, car rental or other extended-stay charges the cardholder later disowns
• Misflagged transactions: phone orders keyed into a store terminal as if card-present

Evidence that wins a 10.3 dispute

1. Proof the card was present and read: chip, contactless or magnetic stripe entry mode in the authorization record.
2. For key-entered sales, a valid manual imprint of the card taken at the time of sale.
3. Cardholder verification: PIN verification data, or a signed receipt where signatures still apply.
4. For hotels and rentals, evidence that the disputed charge belongs to the same stay or rental the cardholder doesn’t dispute, such as a registration card, rental agreement and earlier undisputed charges from the same stay.
5. Anything linking the cardholder to the sale: loyalty account use, ID check notes, CCTV references, customer communication, or earlier undisputed purchases at the same location.

The rebuttal should explain how the card was read and why that rules out a stranger using a cloned or stolen card without the cardholder’s involvement.

How to prevent 10.3 chargebacks

• Avoid key-entering card-present sales. If you must, take an imprint and verify ID.
• Never ring up phone orders as card-present. Process them as card-not-present so the right rules and fraud tools apply.
• Use terminals that support chip and contactless, and replace failing readers.
• For hotels and rentals, keep the signed registration or rental agreement with every folio.

Should you fight or accept?

Fight when the card was electronically read, an imprint exists, or you can tie the cardholder to the transaction through a stay, rental or loyalty account. Those cases are reasonably winnable.

Accept when the sale was key-entered with no imprint and no other link to the cardholder. There is little you can submit that outweighs the issuer’s fraud claim, and fighting usually just adds fees.