POS entry mode codes are the two-digit numbers that ride along with every card transaction and tell the payment network exactly how the account number was captured, whether that was a chip dip, a contactless tap, a magnetic stripe swipe, a keyed entry, or a stored credential. Banks and processors read that code to set the interchange rate, screen for fraud, and decide who pays when a charge is disputed. It’s a small field with outsized consequences for what a merchant pays and what a merchant loses.
The Codes You’ll Actually See
Payment networks assign a standard two-digit numeric code to each transaction identifying how the account number was obtained. The common codes are consistent across Visa and Mastercard, with a few network-specific identifiers layered on top.
- 01 — Manual entry. The account number was typed into the terminal rather than read electronically.1Mastercard Developers. Annexure 1
- 02 — Magnetic stripe. The terminal’s stripe reader captured the account data from the back of the card.1Mastercard Developers. Annexure 1
- 05 — EMV chip. The card’s integrated circuit was read through a physical chip connection, confirming a card-present, chip-authenticated transaction.1Mastercard Developers. Annexure 1
- 07 — Contactless chip. The data was captured wirelessly from a chip-enabled card or device held near the sensor.1Mastercard Developers. Annexure 1
- 09 — E-commerce (remote chip). Used for online transactions, including those authenticated with remote chip technology.1Mastercard Developers. Annexure 1
- 10 — Credential on file. The merchant is billing an account number the cardholder previously authorized them to store, covering recurring subscriptions, installments, and repeat purchases where a card was saved.2Compliance101.com. MasterCard Credential On File Updates
- 80 — Chip fallback to magnetic stripe. A chip card was inserted into a chip-capable terminal, the chip couldn’t be read, and the terminal defaulted to the stripe.3Galileo Financial Technologies. DE022 Codes
- 81 — E-commerce (including chip). Another online identifier used by networks such as Mastercard and Discover for certain card-not-present scenarios.1Mastercard Developers. Annexure 1
- 90 — Magnetic stripe (full track data). The complete, unaltered track data was read and transmitted in the authorization request.3Galileo Financial Technologies. DE022 Codes
- 91 — Contactless magnetic stripe. Magnetic stripe data was captured wirelessly through a contactless tap rather than a physical swipe.4MReports. POS Entry Mode
Code 80 is the one worth watching. Processors monitor fallback activity closely, and excessive fallbacks at a single terminal can trigger monitoring programs or penalties, because the pattern may point to a malfunctioning reader or deliberate fraud.
Why the Code Changes What You Pay
Entry mode drives interchange. Networks price secure capture methods lower and risky ones higher, so a keyed sale costs noticeably more than a chip-dipped one.
Visa’s published schedule shows the gap plainly. For exempt consumer debit cards, a chip-present retail transaction carries an interchange rate of 0.80% plus $0.15, while a manually keyed retail transaction jumps to 1.65% plus $0.15.5Visa. Visa USA Interchange Reimbursement Fees On a $100 sale that’s the difference between $0.95 and $1.80 in interchange alone. A business running hundreds of keyed transactions a day loses tens of thousands of dollars a year to that spread.
Interchange downgrades happen when a transaction that could have qualified for a cheaper rate gets bumped to a higher tier. The entry mode may not match the terminal’s capabilities, required data fields may be missing, or the transaction may not settle within the network’s timeframe. Merchants often don’t notice until they audit a processing statement, because the higher fee is applied automatically with no separate notification.
Why the Code Decides Who Eats the Fraud
Since the EMV liability shift, the entry mode code largely determines who pays for counterfeit fraud. When a chip card is used at a chip-capable terminal and the chip is properly read as code 05, the issuing bank bears liability. When a chip card is swiped at a magnetic-stripe-only terminal because the merchant never upgraded, the merchant bears it.6Visa. EMV Liability Shift
Fallback sits in a gray area. A code 80 transaction may still be approved, but if the issuer later determines proper chip processing didn’t occur, liability can shift to the merchant. Train staff to use swipe or key fallback only when the terminal itself prompts for it, not just because a customer says their chip isn’t working. Some merchants refuse fallback entirely and ask for another payment method when the chip won’t read.
Keyed transactions at chip-capable terminals carry the steepest exposure. Visa’s dispute guidelines warn that even if a keyed sale is authorized and the receipt is signed, the charge can still be disputed back to the merchant if fraud occurs and the receipt lacks a physical card imprint.7Visa. Dispute Management Guidelines for Visa Merchants
What the Code Does in a Dispute
When a cardholder disputes a charge, the entry mode code is one of the first fields the issuer checks. It shows whether the card was physically present, how it was authenticated, and whether the terminal was running at its full security capability. A chip-read transaction with full chip data is far harder for a fraudster to dispute than a keyed transaction with no physical card verification.
Visa spells this out in its dispute conditions. For the EMV liability shift counterfeit fraud condition, the issuer checks whether the terminal entry capability was coded 5 and whether full chip data was transmitted in the authorization request. If either check fails, the merchant can lose the dispute.7Visa. Dispute Management Guidelines for Visa Merchants For card-present fraud outside the EMV counterfeit category, the merchant’s strongest defense is proof that the chip or magnetic stripe was physically read, and the authorization record carrying a code 05 or 02 is that proof.
Issuers also use entry mode data to flag unusual activity. A card that’s always chip-dipped at a grocery store and suddenly shows up as manually keyed at an electronics retailer overseas is the kind of pattern that triggers a review.
Where the Code Lives in the Transaction
The entry mode code sits inside Data Element 22 (DE022), the field defined by the ISO 8583 messaging standard that payment terminals use to talk to processors. Positions 1 and 2 hold the two-digit entry mode. Position 3 reports the terminal’s PIN entry capability, telling the issuer whether the hardware could have accepted a PIN even if one wasn’t requested.3Galileo Financial Technologies. DE022 Codes If a terminal reports chip capability in positions 1 and 2 but no PIN capability in position 3, the bank can flag that mismatch. The code reports what happened; the surrounding field reports what the terminal was equipped to do.
Habits That Keep You on the Right Side of the Code
The entry mode is quiet, but it quietly affects processing costs, fraud liability, and dispute outcomes on every sale. A few practices move the numbers in your favor:
- Use the most secure entry method the card and terminal support. Dip or tap before swipe, and swipe before key entry.
- Let the terminal prompt a fallback. If the chip won’t read, wait for the device to request a swipe rather than skipping straight to one.
- Audit processing statements. Downgrades caused by entry mode mismatches or missing data fields rarely announce themselves.
- When key entry is unavoidable, take a physical imprint of the card on the receipt. That imprint is what preserves your defense if the charge is later disputed.