Código de motivo de devolución de Visa 10.1: Fraude por falsificación con transferencia de responsabilidad EMV
Visa reason code 10.1 concerns counterfeit-card fraud in a card-present payment that meets the rules. The cardholder denies taking part. The payment must qualify for Visa's EMV liability shift. Check the card, entry mode and chip data. Owning a chip terminal does not, by itself, defeat the claim.
What Does Visa 10.1 Mean?
The code concerns a counterfeit card used in person. It does not cover every payment denied by a customer. Visa requires the payment to fit the relevant EMV liability shift. The issuer must report the fraud as counterfeit.
A copied magnetic stripe is different from copying a secure chip. For background on related card-data risks, see the guide to EMV bypass cloning. Do not assume a chip card or terminal is proof that no fraud occurred.
For non-counterfeit cases with a PIN-preferring card, compare Visa 10.2. Its PIN and market rules differ from 10.1. Check that the payment fits that code.
Which Processing Conditions Matter?
For 10.1, the card must be a chip card and the buyer must deny taking part. The payment must involve a counterfeit card used in person. One ground concerns a payment not made at a chip reader. Others concern missing full-chip data on certain chip-initiated payments:
- For online approval, check the full-chip data in the authorization request.
- For offline approval, check the full-chip data in the clearing record.
“Online” here means an authorization sent to the issuer. It does not mean an internet purchase. Keep that distinction clear when describing the case.
Review the Exclusions With the Acquirer
Visa also lists cases that cannot be disputed under this code. These include chip-initiated and fallback payments. Ask the acquirer to check the entry mode and chip data against the rules. A receipt saying “chip” does not settle every part of that check.
Visa excludes payments with a token under this code outside Europe. Other exclusions have their own terms. Check the actual record and the right rule. Do not assume every token or swipe has the same result.
Visa's EMV participation table also varies by region and payment type. An exclusion under 10.1 does not mean no other dispute condition can apply.
Build a Transaction-Level Evidence Pack
- Identify the payment. Match the amount, date and reference to the dispute notice.
- Verify card and terminal data. Ask the acquirer to confirm chip-card status and the recorded entry mode.
- Check the transmitted records. Distinguish the authorization record from clearing data. Identify any missing fields.
- Explain the specific remedy. Link the record to the applicable exclusion, credit or withdrawal.
Do not send a sales brochure for the device as the whole reply. A receipt, sale record and chip log have different roles. Label each item and explain what the relevant field shows.
Which Response Routes Are Available?
At pre-arbitration, Visa permits proof of a missed credit or reversal, an invalid dispute or a withdrawn claim. A later travel or rental charge has its own route. Where it applies, records must link the charge to the earlier period and required chip record.
The US rules also list a compelling-evidence route for 10.1. That is not permission to apply the card-absent CE 3.0 checklist to every in-person case. Ask the acquirer which evidence is permitted for the condition, region and stage.
Which Deadline Applies?
Visa gives the issuer 120 calendar days from payment processing to raise this condition. That is not the merchant's response allowance. Follow the provider's due date. Stripe's response guidance explains its merchant deadlines; do not assume a universal 30-day window.
Hypothetical Chip-Data Example
A terminal can read chips, but the case record lacks the required chip data. The equipment invoice does not prove the data was sent. Request the relevant authorization or clearing record and have the acquirer check the applicable rule and exclusions.
{{COMPONENT_IDENTIFIER}}
Reduce Avoidable Chip-Processing Gaps
- Use the proper chip flow for the card and market.
- Investigate missing chip data with the provider.
- Do not force declined payments through a manual workaround.
- Keep permitted transaction records and train staff on failed-chip procedures.
Sources checked November 16, 2026: Visa rules, October 24, 2026 edition, sections 11.1.2 and 11.8.2, and the linked Stripe guidance. Review the actual payment data and case stage before choosing a response.

















