Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Card-not-present fraud is the use of stolen card details in transactions where the physical card is never seen, covering online, telephone, and mail order payments.

What Is Card-Not-Present Fraud?
Card-not-present fraud is what happens to card details once chip and PIN made it difficult to use a counterfeit card in a shop. The transaction takes place online, over the telephone, or by mail order, where the merchant never sees the card or the person holding it and can only check what was typed into a form. Everything an attacker needs is data, and data travels.
Four supply routes dominate, and they call for different defences.
Testing comes first. Stolen numbers are validated with low-value or zero-value authorisations at merchants known to apply weak checks, often charities, subscription sign-ups, or small retailers. Validated cards are then used for goods that resell easily, delivered to an address the fraudster controls through reshipping, parcel interception, or click-and-collect with a forged identity, which connects this subject to delivery fraud.
Sophisticated operations add an account layer: register or take over a customer account, let it age, add the stolen card as a saved payment method, and then transact as a familiar customer with order history. That defeats controls tuned to spot first-time buyers.
Authentication is the largest single lever. Since strong customer authentication was fully enforced for UK e-commerce card payments on 14 March 2022, 3-D Secure has carried most UK online transactions, and UK Finance has reported falling remote purchase losses as a result. Turkey arrived at the same place earlier by a commercial route, with acquirers effectively requiring authentication on domestic card-not-present transactions, which is why Turkish merchants see a different fraud mix from their UK counterparts and are more exposed to first-party disputes than to stolen card use.
Beyond authentication, the controls that earn their place are unglamorous.
For an authenticated transaction, fraud liability normally sits with the issuer. For an unauthenticated one, or one where the merchant requested an exemption, it usually sits with the merchant as a chargeback. That makes exemption strategy a commercial risk decision rather than a technical one: higher conversion against retained losses. The separate problem of a genuine cardholder disputing a genuine purchase belongs with chargeback fraud and is not solved by authentication at all.
Treat a skimming discovery as an incident rather than a bug. The questions that matter are how long the script was live, which orders fell within the window, whether card data left the page to an attacker-controlled endpoint, and what the acquirer and the ICO need to be told. At Privia Security, our digital forensic and incident response services cover payment page compromises, including the supplier script that usually turns out to be the entry point.
Remote purchase losses have declined since strong customer authentication was fully enforced for e-commerce card payments in March 2022, according to UK Finance reporting. The pattern that replaced it is less convenient: more authorised push payment scams, more account takeover of accounts that already hold a saved card, and more first-party disputes. Total fraud has shifted rather than disappeared.
Scripted guessing of valid card details. The attacker knows the first six or eight digits identify an issuer and product, then brute-forces the remaining digits, expiry date, and security code using small authorisation or account verification requests. Attempts are usually spread across many merchants to avoid velocity limits. Rate limiting, increasing delays after failures, and declining zero-value probes from suspicious sources are the defences.
Yes, and PCI DSS exists partly to discourage it. The practical answer is not to store the card number at all. Use your payment provider’s vault or network tokenisation so that your systems hold a token usable only by you, keep the card fields in an iframe or hosted field you do not control, and treat anything that reduces your cardholder data environment as a risk reduction worth paying for.
It depends on authentication. If the transaction was authenticated through 3-D Secure, liability for fraud normally shifts to the card issuer. If the merchant skipped authentication, including by claiming an exemption, the merchant usually absorbs the chargeback. Exemptions therefore trade conversion against retained risk, and that balance should be modelled against your real fraud rate rather than assumed.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.