Skip to content

Card-present vs card-not-present transaction: fees, fraud and liability explained

What a card-not-present transaction is and how it differs from card-present on fees, fraud and liability, with the controls that fit each sales channel.

A card-not-present transaction is a card payment made online, by phone or with stored card details, where no terminal reads the card. A card-present payment happens when the card, or a device holding it, is physically read at a terminal. Card-not-present carries more fraud risk, usually higher fees and different liability rules.

This guide compares the two on fees, fraud, liability and security controls, then shows how to pick controls for each sales channel. It reflects Visa, EMVCo and other public sources as read in November 2026. For the stages both kinds of payment share, see how card payments work.

Key takeaways

  • The sales channel decides the label, not the card. The same card is card-present at a terminal and card-not-present online.
  • Card-not-present carries more fraud risk, and fees are usually higher to match.
  • In a shop, chip technology decides liability. Counterfeit fraud falls on the party that has not adopted it.
  • Online, 3-D Secure decides liability. A successful authentication generally shifts fraud chargebacks to the issuer.
  • Tokenization, address checks and security codes lower risk without changing who is liable.

What counts as card-present?

A payment is card-present when a terminal physically reads the card or a device that holds it. The reading is the proof that the card was there.

Four methods count:

  • Chip insert. The terminal reads the EMV chip, which produces a one-time code for that transaction. EMV is the chip standard named after Europay, Mastercard and Visa.
  • Contactless tap. The card's chip talks to the terminal over a short-range radio link.
  • Device wallet tap. A phone or watch presents a tokenized version of the card to the terminal.
  • Magnetic stripe swipe. The oldest method, and the easiest to copy, because the stripe holds the same data every time.

A card that is physically in the shop but typed into the terminal by hand does not get full card-present treatment. Without a chip or stripe read, the networks have less proof, and the fee and the fraud exposure move closer to an online sale.

What counts as a card-not-present transaction?

A card-not-present transaction, often shortened to CNP, is any card payment where the merchant never reads the card. The merchant relies on details the customer supplies or that were stored earlier.

Common examples:

  • Ecommerce checkout, where the shopper types the card number into a web page.
  • In-app purchases, including wallet payments made inside an app or a browser.
  • Mail and telephone orders, where staff key in the details.
  • Card-on-file charges, where the merchant uses a card saved from an earlier purchase.
  • Subscriptions and other recurring payments, which the merchant starts without the cardholder taking part each time.
  • Payment links and online invoices.

Stored-card and recurring charges have their own rules about consent and how each charge is labeled. Recurring card payments covers them.

How do card-present and card-not-present payments compare?

The two differ on six practical points. Fees and liability follow from the first two rows: how the card is read and how strong the proof is.

FactorCard-presentCard-not-present
How the card is readChip, contactless tap or swipe at a terminalTyped in, stored on file or passed by a wallet online
Proof the cardholder took partChip code, PIN, signature or device biometricSecurity code, address match, 3-D Secure authentication
Fraud riskLower. Mostly counterfeit, lost or stolen cardsHigher. Stolen card details can be used from anywhere
FeesUsually lower interchangeUsually higher interchange and processor pricing
Fraud liabilityCounterfeit fraud falls on the party that has not adopted chip technologyWith the merchant by default. Generally shifts to the issuer after a successful 3-D Secure authentication
Main controlsEMV chip, contactless, PIN, encrypted terminals3-D Secure, tokenization, address verification, security code, fraud screening
Dispute exposureLowerHigher, including claims that the cardholder never made the purchase

How do fees differ between the two?

Card-not-present payments usually cost more to accept. Interchange, the fee the acquirer pays the card issuer, varies by how a card is accepted, and the networks set higher rates where fraud risk is higher.

Three things drive the gap:

  1. Interchange category. The same card falls into a different, usually more expensive, rate category when it is not read by a terminal.
  2. Processor pricing. Many providers quote one rate for in-person payments and a higher one for online or keyed payments.
  3. Fraud and dispute costs. Online merchants pay for fraud screening, authentication and chargeback handling that a shop rarely needs.

Rates change, and each network publishes its own tables, so compare the in-person and online lines on your own statement. Interchange fees explained shows how the fee stack is built.

Who is liable for fraud in each case?

Liability depends on which security technology each side used. The rule in both channels is the same idea: the party that skipped the stronger control pays.

Card-present: the EMV chip liability shift

Visa's liability shift sheet states that on October 1, 2015, in-store counterfeit fraud liability in the US shifted to the party, either the issuing financial institution or the merchant, that has not adopted chip technology (Visa).

In practice that means two cases. If a chip card is used at a terminal that only reads the magnetic stripe, the merchant generally holds the liability. If both the card and the terminal support chip, the issuer continues to bear it.

Card-not-present: the 3-D Secure liability shift

3-D Secure, or 3DS, is a protocol that lets the card issuer authenticate the cardholder during an online payment. EMVCo, the body that manages the EMV standards, maintains the EMV 3DS specifications (EMVCo).

When authentication succeeds, liability for fraud losses typically transfers from the merchant to the issuing bank (Global Payments). GPayments, a 3DS vendor, adds that each card scheme determines its own liability shift rules (GPayments).

Without 3DS, the merchant bears fraud chargebacks on card-not-present sales by default. The same applies if authentication was not completed and the merchant went ahead anyway. In Europe, 3DS is also the usual way to meet the strong customer authentication rules in the second Payment Services Directive (PSD2).

3D Secure 2 explained covers the flows and the cases where the shift fails. Chargebacks explained covers what happens when a dispute arrives anyway.

Which security controls apply to each channel?

Five controls do most of the work. Two belong to one channel, and three help in both.

  • EMV chip (card-present). The chip produces a different code for every transaction, so copied data cannot be replayed. This is what the 2015 liability shift rewards.
  • 3-D Secure (card-not-present). The issuer checks the cardholder with a risk assessment and, when needed, a challenge such as a banking app approval or a biometric.
  • Tokenization (both). A token replaces the card number so the real number is not stored or sent. Visa reported in 2022 that, across more than 8,600 issuers and 800,000 merchants, its tokens led to a 28% reduction in fraud rates and a 3% increase in approval rates (Visa, August 2022). Device wallets work this way: Apple says a unique Device Account Number is created for each card, and that full card numbers are not shared with merchants (Apple, 2024).
  • Address verification service, or AVS (mostly card-not-present). The issuer compares the billing address the buyer typed with the address it holds.
  • Card verification value, or CVV (mostly card-not-present). The security code shows that the buyer probably has the card. Merchants may ask for it but may not store it after authorization.

Card tokenization explained compares gateway tokens with network tokens, and the PCI DSS guide covers what card data a business may keep.

How do you choose controls by sales channel?

Match the control to the way you sell. Most businesses run more than one channel, so treat each one separately.

Sales channelClassificationControls to put first
Shop or restaurantCard-presentChip and contactless terminals. Avoid swiping or keying a chip card
Online storeCard-not-presentHosted payment fields, 3-D Secure, address and security code checks
Phone ordersCard-not-presentA payment link instead of keyed entry. Address and security code checks when keying
SubscriptionsCard-not-presentAuthenticate the first payment, store a token, label later charges as merchant-initiated
Mobile appCard-not-presentDevice wallets, which pass a token and a device authentication
Wallet tap at a terminalCard-presentThe same chip-capable contactless terminal

Then review the results every month. Track fraud and disputes by channel, not in total, because a problem in one channel hides inside a healthy average.

Sources

What to do next

List your sales channels and mark each one card-present or card-not-present. Check that every in-store terminal reads chips, then decide where to require 3-D Secure online with 3D Secure 2 explained. BlindPay publishes this guide, and its own card payins are card-not-present: every production charge needs an authenticated 3-D Secure result.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.