Time for a Level Playing Field for Regulated UK Gambling Payments
Download Whitepaper
Transaction Processing

Card Not Present

What Is Card Not Present (CNP)? Definition and How It Works

Definition

Card Not Present (CNP) is a transaction classification for payments where the physical card is not read by a terminal, covering e-commerce, MOTO, and recurring payments, carrying higher fraud liability for the merchant and different interchange rates than card-present transactions.

How it works

Card Not Present is one of two fundamental transaction environment classifications in card payments. In a CNP transaction the cardholder's card details are entered manually or stored digitally rather than read by a chip reader, magnetic stripe reader, or contactless terminal. The card is not physically verified at the point of transaction. This classification applies to e-commerce checkout (card number entered online), mail order and telephone order (MOTO) transactions, and recurring or merchant-initiated payments using stored card credentials.

The CNP classification has direct consequences for fraud liability. Under card scheme rules, CNP transactions shift fraud chargeback liability to the merchant's acquiring bank and, through the acquiring agreement, to the merchant. If a fraudulent CNP transaction results in a chargeback under reason codes related to unauthorised use, the merchant typically bears the financial loss. This contrasts with card-present transactions where the issuer bears the liability for approved chip-and-PIN transactions.

3D Secure authentication changes the liability picture for CNP. When a CNP transaction is authenticated via 3DS and the issuer approves it, liability for fraud chargebacks shifts back to the issuer. This is the primary mechanism by which CNP merchants manage fraud chargeback exposure. Unauthenticated CNP transactions (where 3DS is not used or the cardholder is not challenged) leave the merchant liable.

Interchange rates for CNP transactions are higher than for card-present transactions for most card types. Card schemes price CNP interchange at a premium reflecting the higher fraud risk. Merchants with high CNP volumes should factor this into their cost-of-acceptance calculations and consider network token adoption, which can qualify CNP transactions for lower consumer-device interchange categories.

Why it matters

CNP transactions without 3DS authentication leave the merchant liable for fraud chargebacks; 3DS authentication with issuer approval shifts liability back to the issuer. CNP interchange is priced above card-present rates for most consumer card types; at high volume this differential represents a material acceptance cost. Transactions submitted with a network token (rather than a raw PAN) may qualify for lower consumer-device interchange rates even in CNP environments, improving cost and authorisation rates. Full 3DS challenge flow adds friction to CNP checkout; frictionless 3DS flows (where the issuer approves without consumer interaction) provide liability shift without UX impact. MOTO transactions are a CNP subcategory with their own interchange rates and fraud rules; merchants taking payments over phone or by post should ensure correct MOTO classification in their authorisation messages.

With PXP

PXP's platform handles CNP transaction processing across e-commerce, MOTO, and recurring payment contexts, supporting 3DS authentication, network tokenisation, and correct transaction classification to optimise liability and interchange outcomes for CNP volumes.

Talk to a payments specialist

Frequently asked questions

How does CNP fraud liability differ from card-present fraud liability?

In card-present transactions processed with chip-and-PIN (EMV), the issuer bears liability for fraud chargebacks because the chip authentication was completed at the point of sale. In CNP transactions without 3DS authentication, the merchant bears fraud chargeback liability. With 3DS authentication and issuer approval, liability shifts to the issuer even in CNP environments. The presence or absence of 3DS authentication is the key determinant of who bears fraud liability in online payments.

What interchange rate premium do CNP transactions carry?

CNP interchange rates vary by card scheme, card type, and region but are consistently higher than card-present rates. For Visa and Mastercard consumer credit in Europe, CNP rates are typically 0.3% (regulated) but commercial cards and cross-border transactions carry higher CNP premiums. In the US, CNP adds a significant basis point premium to most consumer and commercial interchange categories. Merchants processing high CNP volumes should analyse their interchange mix to quantify the CNP premium and evaluate optimisation options including network tokenisation.

What is the difference between CNP and MOTO?

CNP is the broad classification for all transactions where the card is not physically present. MOTO is a specific CNP subcategory for payments taken over telephone or by post where the cardholder provides their card details verbally or in writing. MOTO has its own transaction type codes in the authorisation message and its own interchange rate tiers. E-commerce and recurring payments are also CNP but are not classified as MOTO. The distinction matters for interchange qualification and PCI DSS compliance scope.

Does 3DS fully eliminate CNP fraud chargeback risk for merchants?

3DS with issuer authentication and approval shifts liability for fraud chargebacks to the issuer, but it does not eliminate all chargeback risk. Non-fraud chargeback reason codes (item not received, item not as described, subscription cancelled) are not affected by 3DS liability shift, those remain the merchant's responsibility. Additionally, in markets where 3DS SCA exemptions apply (low-value, trusted beneficiary, transaction risk analysis), the exemption rules determine whether liability shift applies. Merchants should not assume 3DS eliminates all chargeback exposure.

Revolutionize your business with PXP

Take complete control of your commerce and payments with one platform.

Get Started