Short answer: Ecommerce fraud prevention in India comes down to four layers: keep card data off your own servers with a tokenised gateway, lock down the checkout page against injected scripts (PCI DSS 6.4.3 and 11.6.1), confirm every UPI payment through the gateway rather than a screenshot, and make your real domain and handles easy for customers to verify so fake stores stand out.
Key takeaways
- Two PCI DSS v4.0 controls for payment-page scripts, 6.4.3 and 11.6.1, became mandatory on 31 March 2025.
- An embedded payment iframe does not remove script risk from the page that hosts it; a full redirect to the gateway changes the picture.
- RBI rules already bar merchants from storing actual card numbers, and RBI's authentication directions apply from 1 April 2026.
- Never mark an order paid from a UPI screenshot. Trust only a verified gateway webhook or your settlement report.
- Stolen admin passwords and gateway API keys can turn refunds and payouts into a fraud channel, so protect them like cash.
Which frauds hit Indian online stores and their customers?
Most attacks on a D2C store or marketplace seller follow a few patterns, and each needs a different fix.
- Lookalike stores. A copied site on a near-identical domain, promoted through social media ads or WhatsApp forwards with festive-sale prices, takes UPI payments and never ships.
- Brand phishing. SMS, email or WhatsApp messages that use your name to ask customers for a "delivery fee", a KYC update or an OTP.
- Checkout skimming. A malicious script added to your checkout page, often through a compromised plugin or a third-party tag, reads card details as the customer types them.
- Fake payment proof. Edited UPI screenshots sent to sellers who confirm orders manually, which is common on WhatsApp and Instagram storefronts.
- Back-office takeover. Stolen admin logins or gateway API keys used to issue refunds, change payout bank accounts or trigger transfers.
How do you protect a checkout page from skimming scripts?
The PCI Security Standards Council says requirements 6.4.3 and 11.6.1 exist to reduce e-skimming. Together they ask you to authorise every script on the payment page, confirm its integrity, and get alerted when scripts or security-relevant HTTP headers change. Both were best practice from March 2022 and became mandatory on 31 March 2025, according to the PCI SSC blog (2025).
For a Shopify, WooCommerce or custom store in Mumbai or Bengaluru, that means:
- List every script that loads on cart and checkout pages, including analytics, chat widgets, heatmaps and ad pixels.
- Remove anything the payment step does not need, especially marketing tags.
- Set a Content Security Policy that only allows the domains you have approved, and use Subresource Integrity on fixed third-party files.
- Run change detection that alerts a named person when a checkout script or header changes, and review alerts the same day.
- Restrict who can edit themes, plugins and tag managers, with two-factor login for every admin account.
Does a payment gateway iframe make you safe?
Partly. PCI SSC removed 6.4.3 and 11.6.1 from the SAQ A questionnaire, but replaced them with an eligibility rule: a merchant that embeds a provider's payment form must confirm its own page is not open to script attacks. Its FAQ 1588 gives two ways to show this: apply controls like 6.4.3 and 11.6.1 yourself, or get written confirmation from your PCI DSS compliant provider that its embedded solution, set up as instructed, protects the page, per the PCI SSC FAQ 1588 (2025). The same rule does not apply to merchants that redirect shoppers to the provider's own page, as the PCI SSC announcement of the FAQ (2025) explains.
Checkout set-upWhere card data is enteredWhat you still own Full redirect to the gateway pageThe gateway's domainProtecting the link that sends shoppers there, your admin and your order logic Embedded iframe or drop-in formThe gateway's frame inside your pageScript control on the hosting page, or the provider's written confirmation Card fields built into your own pageYour page and possibly your serverThe widest PCI DSS scope; avoid unless you have a strong reason and a qualified assessor Confirm with your acquirer or gateway which questionnaire applies before you assume SAQ A.
What do RBI rules mean for your checkout?
Two sets of RBI rules shape how card and digital payments work on an Indian store. First, the card-on-file restriction: entities other than card issuers and card networks may not keep actual card data, and the final purge deadline was 30 September 2022, with tokenisation as the replacement, per the RBI circular on storage of card data (2022). If any old database, CSV export or log file still holds full card numbers, find and remove it.
Second, the Authentication Mechanisms for Digital Payment Transactions Directions, 2025. The RBI press release says they keep the minimum of two-factor authentication, let issuers add risk-based checks, do not require SMS OTP to be discontinued, and must be complied with by 1 April 2026, according to the RBI press release (2025). For a merchant, the practical point is to let the gateway and issuer run authentication, test your checkout on the newer methods your gateway offers, and never design a flow that collects an OTP on your own page.
How do you stop fake websites that copy your brand?
You cannot stop someone registering a lookalike domain, but you can make the real one easy to recognise and the fake one quicker to remove. RBI used the same idea for banks: it directed them to move to an exclusive .bank.in domain, with IDRBT as the only registrar, by 31 October 2025, so customers can tell a genuine bank site from a copy, per the RBI circular on .bank.in migration (2025). Retailers have no equivalent, so build your own signals:
- Register the obvious misspellings and the
.inand.co.inversions of your brand domain. - State your one official website, WhatsApp Business number and social handles on the site footer, invoices and order confirmations.
- Publish SPF, DKIM and a DMARC policy on your email domain so spoofed mail is more likely to be rejected.
- Search for your brand name with "sale" or "offer" before Diwali and other festive peaks.
- Keep a takedown kit ready: trademark proof, screenshots and the fake domain's registrar and host.
- Tell customers who were cheated to report it on the national cybercrime portal (cybercrime.gov.in) or the 1930 helpline, and log every case you hear about.
How should you confirm UPI payments safely?
UPI fraud against sellers usually depends on a person confirming an order from something the buyer sends, so take that decision away from people.
- Mark orders paid only when your gateway's signed webhook or status API confirms the transaction, and check the signature on your server.
- Use a dynamic QR or intent flow tied to the order amount, not one static QR code reused for every sale.
- Reconcile daily against the settlement report from your gateway (Razorpay, PayU or Cashfree, as examples).
- Remind customers in plain Hindi and English that your team will never ask for a UPI PIN or OTP, and that entering a PIN sends money; it is never needed to receive a refund.
Are your admin panel and gateway API keys a fraud risk?
Yes, and small stores often forget it. A CERT-In advisory issued on 9 October 2026 describes attackers using stolen payment gateway and bank API credentials, often hard-coded in source code, to call payout and transfer APIs directly, per CERT-In advisory CIAD-2026-0046 (2026). It targets financial-sector entities, but the advice suits any store that can refund or pay out through an API:
- Two-factor login on the store admin, the gateway dashboard and hosting accounts.
- API keys kept in a secrets manager or server environment, never in code or Git, and rotated on a schedule and after any staff exit.
- Maker-checker approval and daily limits for refunds and payout account changes.
- Alerts on unusual refund volume or new beneficiary accounts, and centralised logs kept for at least 180 days, which the advisory recommends.
If you suspect a compromise, check your CERT-In reporting duties with your adviser, rotate every credential and keep the logs. A periodic security audit of your store and its integrations catches many of these gaps before an attacker does.
Ecommerce fraud prevention in India: what should you fix first?
PriorityActionTypical owner This weekTwo-factor login everywhere; remove unused admins and pluginsFounder or IT lead This weekSwitch UPI confirmation to verified webhooks onlyDeveloper This monthScript inventory, CSP and change alerts on checkout pagesDeveloper or security partner This monthSearch for and purge any stored card numbersDeveloper Before festive salesLookalike domain watch, DMARC and a takedown kitMarketing with IT If you are planning a new store, it is cheaper to choose a redirect or well-documented hosted checkout at the start; the e-commerce development team at Alive Inc. designs payment flows this way, and website security hardening covers existing sites. For the conversion side of checkout, see our earlier post on designing Indian store checkouts that sell.
Frequently Asked Questions
Is PCI DSS mandatory for small online stores in India?
If you accept card payments, the card networks expect PCI DSS compliance through your acquirer or gateway, whatever your size. Many small stores validate with a short self-assessment questionnaire. Ask your gateway which questionnaire applies, and use a redirect or hosted checkout to keep the scope small.
What are PCI DSS requirements 6.4.3 and 11.6.1?
They are two PCI DSS v4.0 controls for e-commerce payment pages. Requirement 6.4.3 asks you to authorise and check the integrity of every script on the page. Requirement 11.6.1 asks for alerts when those scripts or security-relevant headers change. Both became mandatory on 31 March 2025.
How can a customer check that my online store is genuine?
Give them one rule: the store is genuine only at your exact domain, which lists your official WhatsApp Business number and social handles. Repeat that domain on invoices, packaging and order messages, and never send payment links from personal numbers.
What should I do if a fake website is using my brand name?
Collect screenshots, the domain and its registrar and hosting details, then file abuse reports with both, citing your trademark. Warn customers on your site and social channels, and point anyone who lost money to the national cybercrime portal or the 1930 helpline. A lawyer can advise on further action.
Can I store customer card details for faster repeat checkout?
Not the actual card number. RBI rules limit storage of card data to card issuers and networks, so repeat checkout works through tokens created via your payment gateway. Check your own databases and logs for any old card data.
Sources
- PCI Security Standards Council: Guidance for e-commerce requirements effective after 31 March 2025 (2025)
- PCI Security Standards Council: FAQ 1588, SAQ A eligibility criteria for scripts (2025)
- PCI Security Standards Council: FAQ clarifies new SAQ A eligibility criteria (2025)
- Reserve Bank of India: Restriction on storage of actual card data (2022)
- Reserve Bank of India: Directions on authentication mechanisms for digital payment transactions (2025)
- Reserve Bank of India: Migration to .bank.in domain (2025)
- CERT-In: Advisory CIAD-2026-0046 on payment and disbursement API abuse (2026)

