Payment fraud prevention for smaller online businesses

Card-not-present fraud, chargebacks, SCA and 3-D Secure, fraud screening and PCI DSS v4.0.1 scope explained for small online merchants, with a checklist.

Key points

  • Card-not-present fraud and disputed transactions, not hacking, are the payment risks most small online merchants face day to day.
  • 3-D Secure 2 is how card payments meet PSD2 strong customer authentication; exemptions reduce friction but usually leave fraud liability with the merchant.
  • Your payment service provider's fraud tools, plus a few simple velocity and review rules, cover most of what a small shop needs.
  • Under PCI DSS v4.0.1, how you embed checkout decides your SAQ; iframe-based SAQ A merchants must now confirm their page is protected against script attacks.
  • Refund and policy abuse is fraud too: clear policies, good evidence and consistent handling reduce it.

For most small online businesses, payment fraud does not look like a dramatic hack. It looks like an order that ships normally and turns into a chargeback six weeks later, a customer who claims a parcel never arrived, or a run of small test transactions on a stolen card. This guide explains the main forms of payment fraud facing smaller merchants, how strong customer authentication and 3-D Secure actually allocate risk, what screening tools are worth using, and what PCI DSS v4.0.1 requires of a typical small shop.

Rules and products change, so treat your payment service provider’s (PSP’s) documentation and your acquirer’s instructions as the final word for your own setup.

The main types of payment fraud

Card-not-present (CNP) fraud. A criminal uses stolen card details to buy goods online. The real cardholder disputes the transaction and, unless the merchant is protected by authentication, the merchant usually bears the loss: the goods, the shipping and a chargeback fee. Stolen cards are often “tested” first with small purchases or donations, which is why sudden bursts of low-value orders are a warning sign.

Friendly fraud (first-party misuse). The genuine cardholder makes the purchase and then disputes it, claiming they did not authorise it or did not receive the goods. Some cases are honest confusion (an unrecognised billing descriptor, a family member’s purchase); others are deliberate. It is hard to stop at checkout because everything about the order is legitimate.

Triangulation fraud. A fraudster sells goods on a marketplace, then buys them from you with a stolen card for delivery to their genuine customer. We describe this from the marketplace side in common online marketplace scams.

Account takeover. Criminals log in to real customer accounts and use stored payment methods or balances. See protecting ecommerce customer accounts.

Refund and policy abuse. Claims of non-delivery, returns of different or used items, or refunds requested to a different payment method. Covered in its own section below.

Strong customer authentication and 3-D Secure

What the law requires

In the EU, the second Payment Services Directive (PSD2, Article 97) requires payment service providers to apply strong customer authentication (SCA) when a payer initiates an electronic payment, subject to exemptions. SCA means two independent elements from different categories: something the customer knows, has or is. The detailed rules, including exemptions, are in the regulatory technical standards, Delegated Regulation (EU) 2018/389. The UK kept a version of the regime after Brexit, now supervised by the Financial Conduct Authority; the principles are the same but details can differ, so UK merchants should check the FCA’s version.

Note that the legal obligation falls on payment service providers (the cardholder’s bank, and your acquirer), not directly on you. In practice, your PSP’s checkout handles it, and your job is to integrate it properly.

The EU has agreed a replacement package, a Payment Services Regulation and a third Payment Services Directive, which revises SCA and fraud-liability rules. At the time of writing (November 2026) those rules are not yet in application; watch for publication in the Official Journal and the application dates that follow.

How 3-D Secure 2 fits in

For card payments, SCA is delivered through EMV 3-D Secure (3DS2), the industry protocol managed by EMVCo. The merchant’s checkout sends data about the transaction, device and customer to the card issuer. The issuer then either approves without interrupting the customer (a frictionless flow, where its risk assessment is satisfied) or asks the customer to authenticate, typically in their banking app (a challenge flow). The more good-quality data you pass, the more often issuers can approve frictionlessly.

Exemptions and out-of-scope payments

The RTS allows certain payments to skip SCA. The ones most relevant to online merchants:

Exemption or category What it covers (EU RTS)
Low-value remote payments (Art. 16) Up to €30, until cumulative spend since the last SCA exceeds €100 or five consecutive payments
Transaction risk analysis (Art. 18) Low-risk payments up to thresholds of €100, €250 or €500, depending on the PSP’s measured fraud rate
Recurring payments (Art. 14) Same amount to the same payee, after SCA on the first payment
Trusted beneficiaries (Art. 13) Payees the customer has whitelisted with their bank
Merchant-initiated transactions Generally treated as outside SCA scope when based on an agreement authenticated at set-up
“One-leg-out” and mail/telephone orders Generally outside the SCA mandate, though best efforts may apply

Two points are often misunderstood. First, an exemption is a request: the issuer can always decline it and require a challenge. Second, if the cardholder’s bank declines a non-authenticated payment with a “SCA required” response, you need to retry with authentication rather than give up the sale.

The liability shift

Under card scheme rules, when a payment is successfully authenticated with 3-D Secure, liability for fraud-related chargebacks (the “I didn’t make this purchase” type) generally shifts from the merchant to the card issuer. Three limits matter:

  • It covers fraud disputes, not service disputes. “Item not received” or “not as described” claims are not covered by the shift.
  • Exemptions usually forgo it. When a payment goes through without a challenge because the merchant or acquirer requested an exemption, fraud liability typically stays with the merchant side. Where the issuer itself decides to approve frictionlessly after a full 3DS authentication, the shift generally applies.
  • Scheme rules vary by card brand, region and transaction type, and change over time. Ask your PSP how it handles exemptions and where liability sits for each type.

In our view, small merchants should rarely chase exemptions aggressively to remove friction. The trade-off is fraud risk you would otherwise not carry.

Screening tools that work for small shops

Basic checks

  • CVV/CVC check: confirms the customer has the three- or four-digit code. PCI DSS forbids storing it after authorisation, so card data stolen from databases often lacks it and a mismatch is a strong signal. Skimming code injected into checkout pages can capture it, however, so a match is not proof of a genuine customer.
  • Address verification (AVS): compares the billing address numbers with the issuer’s records. Supported mainly in the UK, US and Canada; patchy elsewhere, so do not decline on AVS alone for international orders.
  • 3DS result: whether the payment was authenticated, challenged or exempted.

Velocity rules

Velocity rules limit how often something can happen in a period. Useful starting points:

  • several declined attempts from the same device, IP address or email within an hour;
  • multiple different cards used on one account or delivery address;
  • many low-value orders in quick succession (a card-testing pattern);
  • a sudden spike in orders for your most resaleable items, such as electronics or gift cards.

Act on these by blocking, adding a challenge or holding for review rather than always declining outright.

Manual review

For a small business, manual review is a time cost, so reserve it for orders that are both high-value and showing mismatches. Illustrative example: a homeware shop with an average order value of £60 might review any order over £400 where the billing and delivery countries differ and the email address was created recently. Reviewers can check the address on a map, look for a social or professional footprint, or contact the customer through details on the order (never through a number the customer later supplies). Write down your criteria so decisions are consistent.

Your PSP’s fraud tools

Most PSPs now include risk scoring, rules engines and 3DS orchestration, sometimes as a paid add-on. Before buying anything separate, check what yours includes, how its rules can be tuned and whether it can request 3DS dynamically for riskier transactions. How payments flow between buyer, platform and PSP is explained in how digital payments work for marketplace sellers.

Chargebacks and friendly fraud

You cannot stop every dispute, but you can win more and prevent some:

  1. Use a recognisable billing descriptor, ideally your shop’s trading name and website, so customers recognise the charge.
  2. Make contact and refunds easy. A customer who cannot reach you often goes to their bank instead.
  3. Keep evidence: order confirmation, IP and device data, delivery tracking and proof of delivery, communications, and for digital goods, access logs.
  4. Respond to every dispute within the deadline with evidence that addresses the specific reason code. Card schemes have introduced programmes that let merchants cite prior undisputed transactions with the same customer; ask your PSP whether it supports them.
  5. Track your dispute ratio. Card schemes run monitoring programmes, and exceeding thresholds can lead to fees or loss of card acceptance. Your PSP can tell you the levels that apply.

Refund fraud and policy abuse

Refund abuse costs money directly and through chargebacks when refused. Typical patterns include claims that a parcel never arrived when tracking shows delivery, returning a different or damaged item, and “wardrobing” (using goods once and returning them).

Defences are largely operational: tracked and, for high-value goods, signed delivery; photographs or weights recorded at dispatch; inspecting returns before refunding; refunding only to the original payment method; and noting repeat claimants. Keep this proportionate. Consumers have statutory rights to cancel and return many online purchases, and a policy that treats every customer as a suspect will cost more in lost trust than it saves. Our guide to returns, refunds and cross-border selling sets out what you must allow.

PCI DSS v4.0.1: what applies to a small online shop

The Payment Card Industry Data Security Standard is a contractual requirement set by the card schemes and enforced through your acquirer. Version 4.0.1, published in June 2024, is the only active version at the time of writing; the requirements that were “future-dated” in version 4.0 became mandatory on 31 March 2025. In mid-2026 the PCI Security Standards Council (PCI SSC) consulted on v4.0.1 to inform its next iteration; check the PCI SSC Document Library for the current version.

Small merchants usually validate with a Self-Assessment Questionnaire (SAQ). Which one depends on how card data reaches your PSP:

Checkout set-up Typical SAQ Why
Customer is redirected to the PSP’s hosted payment page SAQ A Your site never handles card data
PSP’s payment form embedded in your page via iframe SAQ A, subject to the script criterion below Card data goes to the PSP, but your page hosts the frame
Your page creates or controls the payment form (e.g. direct post or merchant-hosted JavaScript form) SAQ A-EP Your website can affect the security of the card data
Card data passes through your own servers SAQ D Full scope

In January 2025, PCI SSC revised SAQ A: it removed Requirements 6.4.3 and 11.6.1 (payment-page script management and tamper detection) and 12.3.1 from the questionnaire, and added an eligibility criterion that the merchant confirms its site is not susceptible to attacks from scripts that could affect its e-commerce systems. FAQ 1588, published in February 2025, clarifies that this criterion applies to merchants whose webpage embeds a provider’s payment form (such as an iframe), not to those using a full redirect. Merchants can meet it either by applying techniques such as those in 6.4.3 and 11.6.1, themselves or through a third party, or by obtaining confirmation from their PCI DSS-compliant PSP that its embedded solution, implemented as instructed, protects against script attacks.

The practical lesson: if you embed a payment iframe, ask your PSP in writing whether it provides that confirmation, and keep the set-up exactly as documented. Every third-party script on your checkout page (analytics, chat, A/B testing, tag managers) is a potential route for card-skimming code, so keep them to a minimum there. Always confirm with your acquirer which SAQ, if any, you must submit.

What to do next

  1. Confirm with your PSP that 3DS2 is active, how exemptions are requested and where fraud liability sits.
  2. Enable CVV checks, AVS where supported, and a handful of velocity rules; review the results monthly.
  3. Set written manual-review and refund rules, and a recognisable billing descriptor.
  4. Identify your checkout type, confirm your SAQ with your acquirer, and if you use an iframe, obtain the PSP’s script-protection confirmation.
  5. Remove non-essential scripts from checkout pages. For the wider security basics behind this, see data security basics for online retailers.

This article is general information, not legal advice. Check your payment provider and acquirer for the rules that apply to your account.

Sources and further reading

  1. Directive (EU) 2015/2366 on payment services in the internal market (PSD2) — EUR-Lex
  2. Commission Delegated Regulation (EU) 2018/389 (RTS on strong customer authentication) — EUR-Lex
  3. Strong customer authentication — Financial Conduct Authority
  4. EMV 3-D Secure — EMVCo
  5. Important updates announced for merchants validating to Self-Assessment Questionnaire A — PCI Security Standards Council
  6. FAQ 1588: How does an e-commerce merchant meet the SAQ A eligibility criteria for scripts? — PCI Security Standards Council
  7. PCI SSC Document Library — PCI Security Standards Council