What does Visa chargeback reason code 10.3 mean?

It means the cardholder is claiming fraud on a card-present transaction that does not qualify for the EMV liability shift codes. In practice it usually involves key-entered transactions or situations where the merchant cannot prove the card was physically present. The issuer is asserting the cardholder neither authorized nor participated in the sale.

How do I fight a 10.3 chargeback on a keyed transaction?

Keyed transactions are hard to defend because you lack chip or swipe evidence. Your best path is proving the cardholder participated: a signed receipt, ID verification notes, camera footage, pickup records, or a pattern of prior undisputed purchases. If the order was really a phone sale, present it with card-not-present evidence like AVS match and delivery confirmation, though acceptance is at the issuer's discretion.

Why did I get a 10.3 instead of a 10.4?

The dividing line is the environment the transaction was processed in. If your terminal submitted the sale as card-present, the fraud dispute arrives as 10.3 even if the buyer was never in front of you. That mismatch usually signals a processing setup problem worth fixing, because you are paying card-present expectations with card-absent evidence.

Visa · Fraud

Reason code 10.3: Other Fraud - Card-Present Environment

The cardholder denies authorizing or participating in a card-present transaction that does not fall under either EMV liability shift code. This typically covers keyed-in transactions, transactions where card data was captured without the card physically present, and card-present fraud scenarios outside the counterfeit and lost-or-stolen categories. It is the catch-all fraud code for the in-person environment.

Issuer filing window

120 days from the transaction processing date

Merchant response window

typically 20-30 days to respond, depending on the acquirer

Why 10.3 chargebacks happen

The transaction was manually key-entered without the card present, for example a phone order run through a retail terminal.
No card imprint or chip data was captured, leaving the merchant unable to prove the card was physically there.
An employee processed unauthorized charges on a customer's stored card details.
A skimmed card number was keyed into a terminal by a fraudster.
The cardholder genuinely made the purchase but does not recognize the merchant descriptor and reported it as fraud.

How to fight a 10.3 chargeback

Submit proof the card was present and read electronically, such as the chip or swipe entry mode in the authorization record, which directly contradicts the claim.
Provide a signed transaction receipt, and pair it with any signature comparison the issuer can perform.
Include CCTV stills, delivery signatures, or pickup records placing the cardholder at the transaction.
If the sale was actually card-absent and mis-coded, gather your card-not-present evidence set instead: AVS and CVV2 match results, customer communications, and delivery confirmation to the cardholder's address.
Search for prior undisputed purchases from the same customer to establish a legitimate history and rebut the fraud narrative.

How to prevent 10.3 chargebacks

Stop keying card numbers into retail terminals for phone or mail orders; route those through a proper card-not-present channel with AVS and CVV2 checks.
Capture chip data on every card-present sale so you always have entry-mode evidence.
Use a clear, recognizable billing descriptor so legitimate customers do not mistake your charge for fraud.
Restrict and log employee access to any system that stores card credentials.
Reconcile refunds and voids daily to catch internal misuse before customers do.

Frequently asked questions

What does Visa chargeback reason code 10.3 mean?: It means the cardholder is claiming fraud on a card-present transaction that does not qualify for the EMV liability shift codes. In practice it usually involves key-entered transactions or situations where the merchant cannot prove the card was physically present. The issuer is asserting the cardholder neither authorized nor participated in the sale.
How do I fight a 10.3 chargeback on a keyed transaction?: Keyed transactions are hard to defend because you lack chip or swipe evidence. Your best path is proving the cardholder participated: a signed receipt, ID verification notes, camera footage, pickup records, or a pattern of prior undisputed purchases. If the order was really a phone sale, present it with card-not-present evidence like AVS match and delivery confirmation, though acceptance is at the issuer's discretion.
Why did I get a 10.3 instead of a 10.4?: The dividing line is the environment the transaction was processed in. If your terminal submitted the sale as card-present, the fraud dispute arrives as 10.3 even if the buyer was never in front of you. That mismatch usually signals a processing setup problem worth fixing, because you are paying card-present expectations with card-absent evidence.

Related Visa codes