ZenWeb - Blog - PCI DSS Malaysia: What Small Online Stores Must Do in 2026

PCI DSS Malaysia: What Small Online Stores Must Do in 2026

October 31, 2026

Share this post:

PCI DSS Malaysia: What Small Online Stores Must Do in 2026
TL;DR: PCI DSS in Malaysia is the card industry’s security standard, not a law, but your payment gateway or acquirer makes it a contract term. Most small Malaysian stores qualify for the short SAQ A form by keeping card details on the gateway’s hosted page or iframe. Since 31 March 2025, SAQ A also requires you to confirm your site is protected from malicious scripts.

Most Malaysian SME owners first meet PCI DSS as a “self-assessment questionnaire” link from their payment gateway. It looks like an IT form, so it gets ticked quickly. That is risky, because your answers are a promise about how your checkout actually works.

This guide covers PCI DSS in Malaysia from a small online store’s point of view. You will see who enforces it, which questionnaire fits your checkout, the 2025 script rule, the PDPA overlap and a yearly checklist. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build and maintain websites; we are not legal advisers or PCI assessors.

This post is general information, not legal or tax advice. Please confirm your own position with a licensed lawyer, your acquirer or a qualified PCI assessor before you act.

Building or rebuilding an online store?

We design checkouts that keep card data on your gateway’s hosted page, so your PCI paperwork stays short. See our web development services →

New to PCI compliance? This short explainer covers the basics first.

Do You Need to Be PCI Compliant as a Small Business?

Source video: Jamie Trull on YouTube, published June 2025. It is US-focused; the standard is global, but Malaysian rules on top of it are covered below.

1. Is PCI DSS Mandatory in Malaysia?

Quick Answer: Not by statute. PCI DSS in Malaysia works the same way as elsewhere: the PCI Security Standards Council sets it and the card brands enforce it through banks. Visa holds acquirers responsible for their merchants’ compliance, so your gateway or acquirer writes it into your merchant agreement. In practice, any Malaysian store that accepts cards must follow it.

The chain of responsibility matters more than the acronym. Visa’s account information security programme says PCI DSS applies to every entity that stores, processes or transmits cardholder data, and that acquirers must make sure their merchants validate at the right level. Here is how that reaches a small store:

  • Card brands set the rules. Visa, Mastercard and others sort merchants into levels by yearly transaction volume.
  • Acquirers carry the risk. Bank Negara Malaysia’s Policy Document on Merchant Acquiring Services (issued 15 September 2021) regulates how acquirers on-board and oversee merchants.
  • Your gateway passes it on. It asks for a yearly self-assessment and can suspend card acceptance if you fall out of line.

The standard itself is now PCI DSS v4.0.1. The Council’s announcement of 11 June 2024 confirmed v4.0 retired on 31 December 2024. How your store is built decides how much of it applies, which is where your web development choices come in.

Key takeaway: Treat PCI DSS as a condition of keeping card payments, not an optional badge. Your merchant agreement, not a Malaysian Act, is what binds you.

2. Which PCI SAQ Fits Your Checkout Setup?

Quick Answer: Your checkout design picks the form. A redirect to the gateway’s hosted page or a gateway iframe usually means SAQ A. A card form your own site builds, even if it posts straight to the gateway, means SAQ A-EP. Storing or processing card numbers on your server means SAQ D, the full standard.

The PCI Council explains the split in its FAQ on direct post versus iframe and redirect: when your site produces the payment page, injected code can copy card details as they are typed. The table maps common store setups to the questionnaire PCI DSS in Malaysia usually calls for. For how gateways connect, see our payment gateway integration guide.

Checkout setup and the PCI DSS questionnaire it usually leads to (as at October 2026)
Five e-commerce checkout setups mapped to who builds the payment page, whether card data touches the merchant’s server, and the usual PCI SAQ type.
Checkout setupWho serves the card formCard data on your server?Usual SAQ
Redirect to gateway’s hosted payment pageGatewayNoSAQ A
Gateway iframe embedded in your checkoutGateway, inside your pageNoSAQ A, plus the 2025 script check
Your own form posting straight to the gateway (direct post or JavaScript)Your websiteNo, but your page handles itSAQ A-EP
Your server receives card numbers and calls the gateway APIYour websiteYesSAQ D
FPX or DuitNow QR only, no cardsBank or gatewayNo card data at allPCI DSS generally not triggered for those payments

Source: ZenWeb compilation from PCI SSC FAQs on SAQ A and SAQ A-EP eligibility and the PCI SSC SAQ A update of 30 January 2025. Your acquirer confirms the final SAQ type. Licence.

Shopify, WooCommerce and custom builds can land in any row, depending on the plug-in used. Our explainer on what a payment gateway is and our comparison of payment gateways in Malaysia help you check which method your provider uses.

Key takeaway: The cheapest PCI decision is made at build time. Choose a hosted page or iframe and you avoid most of the standard; build your own card form and you inherit far more of it.

3. What Changed in 2025: The SAQ A Script Rule

Quick Answer: The revised SAQ A, effective 31 March 2025, dropped requirements 6.4.3 and 11.6.1 from the form but added an eligibility condition. You must confirm your site is not susceptible to script attacks that could affect your e-commerce system. If you embed a gateway iframe, you need evidence to back that statement.

The PCI Council announced the change on 30 January 2025. Its follow-up FAQ of 28 February 2025 gives two ways to meet it, and says it applies to merchants that embed payment forms, not those that redirect away fully:

  • Protect the page yourself. Apply the techniques in requirements 6.4.3 (keep an approved list of scripts on the payment page) and 11.6.1 (detect unauthorised changes to that page).
  • Get your provider’s confirmation. Obtain written confirmation from your PCI DSS compliant processor that its embedded solution includes script-attack protection when set up as instructed.

This is a website problem as much as a payments one. Chat widgets, heatmaps and ad pixels all load scripts; our guide to heatmaps and session recordings under the PDPA explains why we keep them off checkout. The basics in our WordPress website security guide also support your confirmation.

Key takeaway: If you use an embedded iframe, ask your gateway for its script-protection letter now and file it with your SAQ. Do not tick the box on memory.

4. PCI DSS and Malaysian Data Rules: Key Dates Since 2024

Quick Answer: Four PCI dates and one Malaysian date shape 2026 compliance: v3.2.1 retired in March 2024, v4.0 in December 2024, the new SAQ A and future-dated requirements took effect on 31 March 2025, and PDPA breach notification started on 1 June 2025. Older SAQ templates are no longer valid.

Many small stores still hold an SAQ copied from an old version. The timeline shows why last year’s answers may no longer fit.

Timeline: card-security and data-protection milestones for Malaysian online stores
Dates from March 2024 to June 2025 when PCI DSS versions, SAQ A rules and Malaysian PDPA breach notification changed, with what each means for a small store.
DateMilestoneWhat it means for your store
31 Mar 2024PCI DSS v3.2.1 retiredAny SAQ based on v3.2.1 is out of date
11 Jun 2024PCI DSS v4.0.1 publishedClarifications only, no new requirements
31 Dec 2024PCI DSS v4.0 retiredv4.0.1 is the only active version
31 Mar 2025Revised SAQ A and future-dated requirements effectiveScript-attack confirmation needed for SAQ A
1 Jun 2025PDPA sections 12A and 12B in forceData breaches must be reported to the Commissioner

Source: ZenWeb compilation from PCI SSC announcements (11 June 2024, 30 January 2025) and the Personal Data Protection (Amendment) Act 2024 commencement for sections 12A and 12B. Licence.

A card-data leak is also a personal-data breach. Our guide to data breach notification in Malaysia covers who to tell and when; read it alongside your gateway’s incident instructions.

Key takeaway: If your SAQ was filled in before 31 March 2025, redo it on the current v4.0.1 form.

5. How PCI DSS Overlaps With the PDPA and Other Malaysian Rules

Quick Answer: PCI DSS in Malaysia covers card data only, by contract. The Personal Data Protection Act 2010 covers all customer data, by law, including names, addresses and phone numbers your checkout collects. A compliant SAQ does not make your store PDPA compliant, and the reverse is also true. Plan for both.

Small stores often assume one framework covers everything. The table shows who enforces each rule and whether it reaches a small store.

Rules that touch checkout data for a small Malaysian online store (as at October 2026)
Rules grouped by type, showing what data each covers, who enforces it and whether it normally applies to a small online store.
RuleCoversEnforced bySmall store?
Contract-based
PCI DSS v4.0.1Card account dataCard brands via acquirer or gatewayYes, if you take cards
Law
PDPA 2010, security principleAll personal dataPersonal Data Protection CommissionerYes
PDPA section 12B, breach notificationPersonal data breachesPersonal Data Protection CommissionerYes, when a breach occurs
Cyber Security Act 2024National critical information infrastructureNational Cyber Security AgencyRarely
Regulator policy (indirect)
BNM Policy Document on Merchant Acquiring ServicesAcquirers’ merchant on-boarding and IT riskBank Negara MalaysiaIndirectly, via your acquirer’s checks

Source: ZenWeb compilation from Visa’s security compliance page, the PDP Department’s Act 709 page and BNM’s merchant acquiring policy document. “Small store?” is ZenWeb’s plain-language reading, not a ruling. Licence.

Related PDPA questions each have their own guide:

Key takeaway: Keep card data off your site to shrink PCI DSS, then protect the names, phones and addresses you still hold under the PDPA.

Not sure which SAQ your store qualifies for?

We review how your checkout loads the card form and which scripts run on it, then tidy the build so your answers hold up. See how we build e-commerce websites in Malaysia →

6. PCI DSS Checklist for Small Online Stores: A Worked Example

Quick Answer: Map how card data flows, confirm your SAQ type with your gateway, strip unneeded scripts from checkout, lock down admin access, get the provider’s compliance evidence, complete the SAQ and attestation, and diarise the yearly renewal. For a hosted-page store this is a few hours of work a year.

Here is what PCI DSS in Malaysia looks like for Kedai Contoh Sdn Bhd, an illustrative WooCommerce homeware store taking cards on a gateway’s hosted payment page plus FPX. Its yearly routine:

  1. Map the card flow. Click through checkout and note where card details are typed. Here, the browser leaves for the gateway’s page first.
  2. Confirm the SAQ type. Ask the gateway which questionnaire it expects. For a full redirect, this is usually SAQ A.
  3. Clean the checkout pages. Remove chat widgets, heatmaps and unused plug-ins from cart and checkout, and keep a short list of scripts that remain.
  4. Lock down admin access. Use unique logins, strong passwords and two-factor authentication for every WordPress and gateway dashboard user.
  5. Collect provider evidence. Download the gateway’s PCI DSS attestation of compliance and, if you use an iframe, its script-protection confirmation.
  6. Complete the SAQ and attestation. Answer from what you verified, then sign and submit.
  7. Set the renewal. Diarise next year’s SAQ, and re-check whenever you change theme, plug-in or gateway.

Kedai Contoh already issues a consolidated e-invoice for its online sales each month, following our guide to e-invoicing for small businesses in Malaysia. Putting PCI renewal on the same compliance calendar keeps it from slipping.

Key takeaway: Your SAQ is only as true as your last website change. Re-run steps 1 and 3 every time a developer touches checkout.

7. How Much Work Is PCI Compliance for a Small Store?

Quick Answer: It depends almost entirely on checkout design. In ZenWeb’s planning estimates, a hosted-page store spends a few hours a year on PCI tasks, while a store whose own server handles card numbers can need weeks of work plus outside testing. That gap is the business case for a hosted checkout.

These are illustrative planning ranges we use when scoping store builds, not PCI SSC figures, and they exclude gateway or assessor fees.

Illustrative yearly PCI effort by checkout setup (upper estimate, hours)
Estimated yearly hours of PCI DSS work for four checkout setups, shown as bars on a 160-hour scale.
Checkout setupEffort (scale 160 hours)Estimate
Hosted payment page
SAQ A
4–8 hours
Gateway iframe
SAQ A + script check
8–16 hours
Own card form
SAQ A-EP
30–60 hours
Card data on own server
SAQ D
120–160+ hours

Source: Illustrative scenario by ZenWeb, based on planning estimates from Malaysian SME store projects (2024–2026). Bars show the upper estimate. Actual effort varies with your acquirer, platform and team. Licence.

When you budget for the work, a few related guides help:

Key takeaway: A custom card form can cost more in yearly compliance than it saves in checkout design. For most SMEs, a hosted page or iframe is the sensible default.

8. Common PCI Mistakes Malaysian Store Owners Make

Quick Answer: The costly mistakes are picking the wrong SAQ, treating HTTPS as full compliance, running pirated themes or plug-ins, taking card numbers by WhatsApp or email, and not re-checking after a redesign. Each one breaks your SAQ answers or opens the door to card-skimming code.

  • Picking the wrong SAQ. SAQ A on a site that builds its own card form understates your duties; the gap shows only after a breach.
  • Treating SSL as the whole job. HTTPS is required, as our explainer on what SSL is shows, but it does not stop malicious scripts inside your own pages.
  • Using nulled themes or plug-ins. Pirated code often hides malware, and it breaches licence terms too, as our guide to the Copyright Act 1987 for marketers explains.
  • Taking card numbers by chat or email. Card details sent by WhatsApp or email pull your whole business into scope. Send a payment link instead.
  • Ignoring a hack. If your site is compromised, follow our steps to clean malware and recover a hacked website and tell your gateway quickly.

Not every checkout problem is a security problem. If payments fail but no data is exposed, start with our guide on why a payment gateway keeps failing at checkout.

Key takeaway: Never let card numbers reach your inbox, chat or server. Every channel that touches them becomes part of your PCI scope.

9. Conclusion: Design Your Checkout to Keep PCI Small

PCI DSS in Malaysia reaches small stores through the merchant agreement, not a statute, and v4.0.1 is the version that counts as at October 2026. Your biggest lever is checkout design: keep card entry on the gateway’s page or iframe, keep scripts off checkout, and back your SAQ with your provider’s evidence. Then cover the PDPA for all other customer data. If you want a checkout built that way from the start, our web development team can scope it with you.


10. Frequently Asked Questions

1. Is PCI DSS in Malaysia a legal requirement?

No Malaysian Act names PCI DSS. It is a card-industry standard that card brands require acquirers to enforce, so it becomes a term in your merchant or gateway agreement. Breaking it can cost you the ability to accept cards.

2. Do I need PCI DSS if I use a payment gateway?

Yes, but usually in a much lighter form. If card details are entered only on the gateway’s hosted page or iframe, you typically complete the short SAQ A each year instead of the full standard.

3. What is the SAQ A script requirement?

Since 31 March 2025, merchants using SAQ A must confirm their site is not susceptible to script attacks that could affect their e-commerce system. You can meet it with your own controls or written confirmation from your PCI DSS compliant payment provider.

4. Does PCI DSS apply to FPX or DuitNow QR payments?

Generally no. FPX and DuitNow QR payments involve no card numbers, but the PDPA still applies to the customer details you collect.

5. Which PCI DSS version applies in 2026?

PCI DSS v4.0.1 is the only active version as at October 2026. v4.0 retired on 31 December 2024, so replace older questionnaires.

Cite this page: ZenWeb (2026). PCI DSS Malaysia: What Small Online Stores Must Do in 2026. https://zenweb.my/blog/pci-dss-malaysia/

You may quote our data with this credit and a link. See our Terms of Use.

Want a store checkout that keeps PCI simple?

Talk to ZenWeb about an e-commerce build with a hosted payment page, clean checkout scripts and PDPA-friendly tracking. We handle the website; your acquirer and lawyer handle the compliance sign-off.

Get my free checkout review →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.