Card-Present vs Card-Not-Present: What Retail Payments Teams Get Wrong
Card-present vs card-not-present is one of the first distinctions anyone learns in payments, yet retailers that sell both in stores and online still get it wrong in expensive ways. The two environments differ in cost, fraud liability, dispute rights and the data that travels with each payment. This guide explains the differences and shows what a retail payments team should do about them when stores and online start to blend together.
This guide to card-present vs card-not-present covers cost, fraud liability and authentication, then shows how retail payments teams can avoid the most common errors.
What card-present and card-not-present mean
A card-present transaction happens when the card, or a device holding it, is physically presented at the point of sale and read by a terminal using chip, contactless or a magnetic stripe. A card-not-present transaction happens when the card details are keyed in or sent remotely, which covers online checkout, phone orders, mail orders and many recurring payments.
Difference 1: Cost
Card networks generally set lower interchange rates for card-present transactions than for card-not-present ones, because the card being physically present reduces risk. The gap varies by card type, network and region, so check your own statements. If you run both channels, compare the effective rate by channel and not only the headline price from your processor.
Difference 2: Fraud liability
In the United States, the EMV liability shift in October 2015 changed who pays for counterfeit card fraud in stores: if a chip card is swiped instead of inserted because the merchant has no chip reader, liability can move to the merchant. In card-not-present sales, the merchant is generally the party carrying the risk of fraud chargebacks unless an authentication method such as 3D Secure provides a liability shift. Because of this, online fraud controls are not optional.
Difference 3: Authentication and data
A chip or contactless payment carries a cryptogram generated for that single transaction, which is strong evidence that the physical card or device was used. Online, you have to build confidence from other signals: AVS and CVV checks, device and behavior data, and 3D Secure authentication. The different data is also why the same customer can be approved in store and declined online.
Card-present vs card-not-present: where the line is blurring
Several common scenarios do not fit neatly into either bucket, and each needs a clear internal rule:
- Digital wallets in store: a tap with a phone is processed as card-present, but it uses a network token and cryptogram instead of the real card number.
- Buy online, pick up in store: the payment is card-not-present, but the customer arrives with an ID and sometimes the card, which creates an opportunity to reduce fraud.
- Buy online, return in store: the refund should usually go back to the original form of payment, which means the store system needs a way to reach an online transaction.
- Cards on file used at the register: storing credentials for use in several channels requires consistent tokenization and consent.
- Pay by link and phone orders: these are card-not-present even when a store employee takes the order.
What retail teams should do about card-present vs card-not-present
First, report authorization rate, fraud rate, chargebacks and cost separately for each channel, so a problem in one is not averaged away by the other. Second, use one tokenization strategy across channels so a customer’s card can be recognized everywhere without storing raw card numbers. Our guide on network tokenization versus PCI tokenization explains the options.
Third, make sure refunds and exchanges can reference the original transaction no matter where it happened. Fourth, review how your processor identifies each transaction type, because a mislabeled transaction can be priced and scored incorrectly. Finally, consider whether one processor or an orchestration layer for both channels would reduce reconciliation work.
Common card-present vs card-not-present mistakes
Treating pay-by-link and phone orders as in-store payments, comparing channel authorization rates without adjusting for different customer mixes, and assuming that a strong in-store fraud record carries over to online are the three mistakes that show up most often.
Treat card-present vs card-not-present as a spectrum rather than a binary label. Curbside pickup, pay-by-link and mobile wallets sit in between, and each combination changes cost and liability. Reviewing card-present vs card-not-present performance by channel is the quickest way to find where you are overpaying or absorbing avoidable fraud.
Card-present vs card-not-present: Key Takeaways
- Card-present payments usually cost less and carry less fraud risk for the merchant.
- Card-not-present fraud liability generally sits with the merchant unless authentication shifts it.
- Wallets, pickup orders and returns blur the line, so define a rule for each.
- Report metrics by channel and use one tokenization approach across them.
Frequently Asked Questions
What is the difference between card-present and card-not-present?
Card-present means the card or a device holding it is physically presented at a terminal. Card-not-present means the details are keyed in or sent remotely, as in online, phone and many recurring payments.
Why are card-not-present transactions more expensive?
Card networks generally charge higher interchange for card-not-present transactions because the card is not physically verified, which carries more fraud risk. Exact rates vary by network, card type and region.
Is a phone tap with Apple Pay card-present?
Yes. A contactless wallet payment at a terminal is processed as card-present, but it uses a network token and a one-time cryptogram instead of the real card number.
Who is liable for fraud in card-not-present sales?
In general the merchant carries fraud chargeback liability for card-not-present sales, unless an authentication method such as 3D Secure shifts liability to the issuer.
Related Reading
- Payments KPIs: 10 Metrics Every Payments PM Should Track
- Network Tokenization vs PCI Tokenization
- Who Gets the Swipe Fee
- What Is Payment Orchestration?
- Fraud Rules vs Machine Learning: How to Combine Them Without Blocking Good Customers
- Payment Processing Costs: Where They Hide and How to Reduce Them
- Merchant-Initiated vs Customer-Initiated Transactions Explained
Free Payment Performance Audit
Losing revenue to declined payments?
I help online merchants recover revenue lost to declines, false fraud flags and failed renewals. Tell me a little about your payment setup and I will send back the three biggest fixes I would make across authorization rate, retry logic, tokenization and routing. No cost, no obligation.
Request a free audit →Free download
Decline Code Cheat Sheet for Merchants
The 15 most common card decline codes on one page: what each one means, whether to retry, and how to fix it.
No spam. Unsubscribe anytime. See the privacy policy.