Visa 10.3 — Other Fraud — Card-Present Environment
Visa 10.3: the cardholder says they didn't make a sale you keyed in
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Visa 10.3 means the cardholder says they didn't make a purchase that was keyed in at the point of sale. It turns on whether the card itself was there: the bank checks whether it was swiped or chip-read and the sale authorized, or, for a keyed sale, whether a manual imprint was taken. Keyed with no imprint, accept.
What decides a Visa 10.3
- The manual imprint, for a keyed sale
- When your reader can't read a card that's in front of you, Visa lists a manual imprint of the card as a response, except in Europe. A keyed sale's receipt with no imprint doesn't help: the imprint itself is what you send, with the authorization record.
- A phone order run on a card-present terminal
- Visa names an online or mail and phone order that wasn't identified as one as a common cause of 10.3. If a customer read their card number to you over the phone and you keyed it into your counter reader, the sale was never in person; accept it.
- Keying a card you were holding
- Keying in a card that was in your hand, instead of reading it, is a common mistake on 10.3. If your reader's record shows this sale was in fact swiped or chip-read and authorized, send that record: Visa lists it as a response.
The bank's test
The bank checks:
- Was the card swiped or its chip read, and the sale authorized at the point of sale?
- For a keyed sale, was a manual imprint of the card taken?
- Was it really an in-person sale, or an online or phone order processed as one?
- Has the payment already been refunded, or does the cardholder no longer dispute it?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Card reader or processor record (chip, PIN, imprint) | Showing the swipe or chip read and the authorization, or the manual imprint. | The terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified. | Stripe: Uncategorized fileSquare: Authorization documentation | Every seller |
| Receipt or invoice | Showing the sale: what was bought and the amount. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Refund or credit already issued | If the payment was already refunded. | Refund date, amount, and reference. | Stripe: Uncategorized fileSquare: Generic evidence | Every seller |
| Messages with the customer | If the cardholder has withdrawn the dispute. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
What doesn't help
- A keyed sale's receipt with no imprint.
- Delivery or 3D Secure records.
Visa's rules for 10.3
- Visa: 10.3 covers a key-entered sale in a card-present environment that the cardholder says they didn't make. Common causes Visa names: the card wasn't swiped or chip-read, no manual imprint was taken for a keyed sale, or an online or mail/phone order wasn't identified as one. Responses Visa lists: the card was swiped or chip-read and authorized (provide the authorization record); a manual imprint was taken (provide it; doesn't apply in Europe); a credit or reversal was processed; the cardholder no longer disputes it. If the card wasn't swiped, chip-read, or imprinted, Visa says to accept. Source: Visa, Dispute Management Guidelines for Visa Merchants (June 2024), Condition 10.3; read 2026-10-15.
- Visa's current rules keep the credit and withdrawal responses: at pre-arbitration the acquirer may show a credit or reversal the issuer didn't address, that the dispute is invalid, or that the cardholder no longer disputes the transaction; or evidence of an imprint. Source: Visa, Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.8.4.6, Table 11-26; read 2026-11-03.
- The bank's test and the evidence list were checked against Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.8.4, on 2026-10-29.
Common mistakes with Visa 10.3
- Keying in a card that was in the seller's hand instead of reading it.
- Processing a phone order on a card-present terminal.
Should you fight it?
Fight it when the record shows the card was swiped or chip-read and the sale authorized, or when you keyed the card in and took a manual imprint of it. The imprint response doesn't apply in Europe. Visa also lists a credit or reversal already processed, or the cardholder no longer disputing it, as responses. Accept it when any of these is true:
- The card was keyed with no imprint.
- The sale was really a phone or online order.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Read every card present at the sale by chip, tap, or swipe.
- If the reader can't read the card, take a manual imprint.
- Process phone and online orders as card-not-present sales.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
You run in-person weekend bookkeeping workshops for small-business owners and take payment at the door. On October 4 a participant pays $295 for the two-day workshop with their Visa card. Your card reader can't read the card's chip or stripe, so you key the card in, the payment is approved, and you take a manual imprint of the card. In November the cardholder files a 10.3 dispute saying they didn't make the purchase.
The response would attach:
- Exhibit A: a copy of the manual imprint taken on October 4, with the date and amount, and all but the last four digits of the card number covered.
- Exhibit B: the card-reader provider's record of the October 4 sale: entry mode keyed, and the issuer's authorization code.
- Exhibit C: the receipt: the two-day workshop, $295, the date and time it was taken at the door, and the card ending.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Visa reason code 10.3, for $295.00 charged on October 4 for a two-day bookkeeping workshop, paid at the door. The card was in front of us: when our reader couldn't read it, we keyed it in and took a manual imprint.
The sale was authorized at the point of sale. Our card-reader provider's record shows the card keyed in after the reader couldn't read it, and the issuer's approval with its authorization code (Exhibit B).
A manual imprint of the card was taken for the keyed sale. A copy of the imprint, with the date and amount, is attached (Exhibit A).
This was an in-person sale, not a phone or online order processed as one. The receipt shows the payment taken at the workshop door on the morning of October 4 (Exhibit C).
The card was present at the sale, the keyed payment was authorized, and the card was imprinted when the reader couldn't read it. We ask that the dispute be decided in our favor.
Questions people ask
What is Visa reason code 10.3?
Visa's code for other fraud in a card-present environment: the cardholder says they didn't make a purchase that was keyed in at the point of sale.
Does a manual imprint still count for a 10.3?
Visa lists a manual imprint taken for a keyed sale as a response to 10.3, and says it doesn't apply in Europe. A keyed sale's receipt with no imprint doesn't help.
We took a customer's card over the phone on our card reader. Can we fight the 10.3?
No. Visa names a phone or online order that wasn't identified as one as a common cause of 10.3, and a sale that was really a phone or online order is one to accept. Run phone orders as card-not-present sales.
Our reader shows the card was swiped, but the dispute says it was keyed. What do we send?
The authorization record from your reader showing the swipe and the approval. Visa lists a card that was swiped or chip-read and authorized as a response to 10.3.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.