Visa Reason Code 10.3: Other Fraud – Card-Present Environment

What Visa Reason Code 10.3 Means

Visa reason code 10.3 falls under the Fraud category and is titled Other Fraud – Card-Present Environment. It applies when a fraudulent transaction occurs in a physical card-present setting but does not qualify under the EMV liability shift codes 10.1 or 10.2. This code covers a range of scenarios: counterfeit magnetic stripe cards, manual imprint fraud, key-entered transactions where the card was present but unreadable, and other face-to-face fraud situations.

Unlike codes 10.1 and 10.2, which are specifically about chip card liability shift, 10.3 is the broader bucket for card-present fraud where the EMV distinction is not the deciding factor. The cardholder asserts that a fraudulent transaction occurred despite their card being physically used at a terminal.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Counterfeit magnetic stripe card. A fraudster creates a cloned card from stolen track data and uses it at a swipe-only terminal. If the terminal does not support chip, the merchant absorbs this liability under 10.3.
• Manual key-entry transactions. When a card cannot be read and a cashier manually keys in the card number, the fraud risk shifts entirely to the merchant. Fraudsters exploit this by presenting damaged or altered cards intentionally.
• Manual imprint fraud. Older "knucklebuster" imprint machines can be used with counterfeit or altered cards. Any imprint transaction that results in fraud typically falls under 10.3.
• Fallback transactions. When a chip card cannot be read and the terminal falls back to magnetic stripe processing, any resulting fraud is assigned to the merchant unless specific fallback procedures were followed correctly.
• Card-present fraud outside EMV scope. Any card-present fraud scenario where the merchant's terminal limitation or procedure — rather than the card's chip status — is the issue.

Key Deadlines & Timeframes

Evidence You Will Need

Winning a 10.3 dispute is difficult because the cardholder is asserting they did not authorize the transaction. Your evidence must either prove the legitimate cardholder was present and authorized the charge, or demonstrate a procedural or technical defense.

• Signed transaction receipt with imprinted or manually keyed card details — establishes physical card presence but does not prove the legitimate cardholder signed
• Photo ID verification records if your staff checked identification at the time of the transaction
• Cardholder account history showing prior transactions at your location — a known customer relationship undermines a fraud claim
• Security camera footage from the time of the transaction showing the person who presented the card
• EMV terminal certification documentation showing your terminal attempted chip read before falling back to swipe
• AVS and CVV match data from the original authorization, if applicable
• Any subsequent cardholder contact referencing the purchase — a follow-up complaint or inquiry that implies the cardholder knew about the transaction

How Merchants Lose This Dispute

• Operating mag-stripe-only terminals. If your terminal does not support EMV chip, you accept full liability for counterfeit card fraud under 10.3. This is the single biggest preventable cause of these disputes.
• Improper fallback procedures. When a chip card fails to read, strict fallback procedures must be followed — including getting authorization, documenting the failure, and in some environments declining the transaction. Skipping steps eliminates your defenses.
• No ID verification policy. For high-value transactions, staff should request identification. Without an ID check policy, there is no defense against a stranger presenting a stolen or counterfeit card.
• Relying solely on a signature. A forged signature on a receipt means nothing in a fraud dispute. Visa does not accept a signature alone as proof the legitimate cardholder authorized the transaction.
• Missing the response deadline. One day late means automatic loss. Internal alerts should be set at least 5 days before the actual processor deadline.

Response Framework Overview

1. Identify your terminal capabilities. Confirm whether your terminal was EMV-certified at the time of the transaction. If it was, document the fallback attempt.
2. Gather all transaction records. Pull the receipt, authorization record, and any security footage from the transaction date.
3. Assert cardholder presence if possible. If you have ID verification records or account history proving this was a known customer, lead with this evidence.
4. Document authorization response. Provide the authorization approval code and AVS/CVV results from the original transaction.
5. Acknowledge limitations honestly. If you cannot prove the legitimate cardholder was present, consider whether accepting the chargeback is more cost-effective than escalation.

Prevention Tips

• Upgrade to EMV chip terminals immediately. This eliminates the primary source of 10.3 disputes and shifts counterfeit fraud liability back to the issuer.
• Train staff on fallback procedures. When a chip fails to read, specific protocols must be followed. Staff who skip these steps expose the business to full fraud liability.
• Implement ID verification for high-value transactions. Requiring ID at a threshold (e.g., $100+) creates a paper trail that can be used in dispute responses.
• Use security cameras at POS terminals. Clear footage of the transaction is one of the few defenses available against 10.3 disputes.
• Monitor for damaged or suspicious cards. Train staff to recognize signs of card tampering — scratches over the chip, bent chips, or mismatched embossing that suggest counterfeit cards.

Frequently Asked Questions

Is Visa 10.3 different from 10.1 and 10.2?

Yes. Codes 10.1 and 10.2 are specifically tied to the EMV liability shift — they apply when a chip card is swiped instead of dipped. Code 10.3 is the catch-all for other card-present fraud scenarios: magnetic stripe-only cards used fraudulently, manual imprint fraud, key-entered transactions, and situations where the card was physically present but the transaction was still fraudulent.

Can I win a 10.3 chargeback if I have a signed receipt?

A signed receipt establishes that a person was physically present, but it does not prove the legitimate cardholder signed it. If a fraudster used a counterfeit magnetic stripe card, their forged signature on the receipt is not a winning defense. However, if you can establish that the cardholder's behavior — using the card for other purchases before or after, returning to your store, or other corroborating evidence — indicates they were actually present, a signed receipt helps.

How long does the cardholder have to file a 10.3 dispute?

The cardholder has 120 days from the transaction date to file a Visa 10.3 dispute. Your acquirer will notify you of the chargeback and you typically have 30 days to respond, though your processor may impose a shorter internal deadline.

What is the best way to prevent 10.3 chargebacks?

Full EMV chip-and-PIN compliance eliminates most card-present fraud liability. For any transaction where the chip cannot be read, follow fallback procedures strictly: key-entered transactions require manager authorization and should be treated as high risk. Train staff to identify counterfeit card signs: unusual stiffness, incorrect embossing, misaligned holograms, and mismatched card numbers.

Related Codes & Resources