E-commerce site security: how to protect card data and member data

Online shop security: card and member data to protect, checkout tampering cases, PPC survey, Card Security Guidelines 6.1, checks from JPY 49,800 (excl. tax).

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

E-commerce security means keeping customers' card data, member data and purchase history from being stolen, altered or taken offline. It is for operators who run shops on EC-CUBE, WooCommerce, Shopify and the like, and for companies with a custom-built shop. The dangers are tampered checkout screens, components that have not been updated, and operations left wholly to outside firms. Start with three things: close the admin entrance, bring components up to date, and compare what the public guidelines ask for with your current state.

What data does an e-commerce site need to protect?

An e-commerce site gathers information that turns into money the moment it is stolen. Three groups show the order in which to act.

Card data

This means the name, card number, expiry date and security code. Stolen, it is used to shop as someone else. The customer and the card company bear the loss, but the shop loses trust and can have payment stopped. Not keeping card data on your own server ("non-retention") has been treated as effective, yet the Council's guidelines say card data is still stolen from shops that do not retain it, because of flaws in the site. Entry happens on the shop's own site.

Member data and purchase history

This means member IDs and passwords, addresses, phone numbers, email addresses, dates of birth and order history, which shows what was bought and when. Member data keeps being used after theft. According to the guidelines, account takeover with stolen IDs and passwords, and fake accounts made with stolen attributes, precede card payment. For a members' shop, the login screen itself needs protecting.

The admin screen and parts loaded on the checkout screen

Without protecting these you cannot protect the other two. The admin screen is the entrance to products, prices and customer lists. External programs on the checkout screen, such as ad and analytics tags, can be rewritten to change where entered data goes. See card skimming and tampering with third-party scripts.

What incidents have actually happened to e-commerce sites?

We use only material published by the affected company or by public bodies, and we opened each original.

Saga Hirakawaya: a payment application was tampered with

On 15 June 2026 Saga Hirakawaya Co., Ltd. disclosed unauthorized access to its online shop. On 9 March 2026 some card companies raised concerns about a leak. It stopped card payment that day and began a third-party investigation, which ended on 27 March.

The notice says a flaw in part of the system was exploited, the payment application was tampered with, and malicious files were placed on a contractor's server. Information typed into the order form was sent outside. Card data (name, card number, expiry date, security code) may have leaked for 5,783 customers who paid by card between 21 March 2025 and 10 March 2026. The notice opens with 73,213 items of personal information and 6,303 items of card data that may have leaked, and the breakdown includes names, birth dates, addresses, phone numbers and emails of 30,170 people who had entered customer information. The card companies' contact is what alerted the company.

What the Personal Information Protection Commission asked 71 operators

On 16 March 2022 the Commission published its survey on unauthorized access to e-commerce sites. Seventy-one operators that had filed leak reports between April 2018 and March 2021 answered. Direct causes were flaws that let payment screens be tampered with (37%), SQL injection (31%) and weak access restriction on the admin screen (15%). SQL injection means text sent through an input field makes the back-end database act in unintended ways. As their own recognition, 66% cited insufficient understanding of vulnerabilities and 59% an attitude of leaving it to the contractor.

Of the affected sites, 77% had been built by outside contractors. Of the 71 operators, 38% built with outsourcing or cloud services without understanding or agreeing the scope of responsibility, and 39% said contracts or specifications did not mention security measures.

Repeated payment-screen tampering in EC-CUBE

IPA issued a warning on 25 December 2019 about a rise in information leaks from sites running EC-CUBE. It cited an announcement by the Ministry of Economy, Trade and Industry that many payment screens had been tampered with, with about 140,000 card numbers leaked. IPA asked owners to check their version, update to the latest and read the developer's information. A newer case: on 14 October 2026 JVN published a flaw in the Amazon Pay plugin for EC-CUBE 4 (JVN#43511918, CVE-2026-103671), and the developer says attacks exploiting it have been confirmed.

Card fraud damage continues at around JPY 50 billion a year

The Japan Consumer Credit Association counts fraud damage in 2025 at JPY 51.05 billion, down JPY 4.45 billion (about 8%) from JPY 55.5 billion in 2024, the highest since 2019. According to the guidelines, fraud at card-not-present merchants occurs almost entirely at e-commerce merchants, and about 90% of the 2025 damage was impersonation there. April to June 2026 saw JPY 10.77 billion, down 5.2% from the previous quarter, of which stolen card numbers were JPY 10.01 billion. The Association notes it changed its survey method from 2026.

What happens to reporting and notification after an incident?

This introduces the main points of the Personal Information Protection Commission's guidance and is not legal advice. For a particular case, check the guidance or ask an expert.

According to the guidance, some leaks of personal data must be reported, including one that could cause financial harm if misused. It gives as an example a leak of personal data including credit card numbers from an e-commerce site. Only the last four digits plus the expiry date do not directly count as a reportable event.

Reporting has two steps: a preliminary report within 3 to 5 days of discovery and a final report within 30 days, or 60 days where unauthorized purposes are suspected. Notice to the individuals is also expected promptly, depending on the situation.

The guidelines also set the first response to a card data leak. First contact your card company (acquirer) or payment service provider. Then, as it asks, disconnect the source network, suspend card payment and commission a forensic investigation, a specialist investigation into the cause.

What do the public guidelines ask of e-commerce sites?

Two public guides concern e-commerce: the Credit Card Security Guidelines for card payment, and IPA's Security Guidelines for Building and Operating E-commerce Sites.

Credit Card Security Guidelines [Version 6.1]

The Credit Transaction Security Measures Council (secretariat: Japan Consumer Credit Association) published Version 6.1 in March 2026. Version 6.0 of March 2025 added measures for e-commerce merchants, who account for about 90% of fraud damage. For card data protection the measure is vulnerability management of systems and websites. For fraud prevention it is protection against unauthorized login and introducing EMV 3-D Secure (identity checks by the card company). Version 6.1 adds or changes no guideline measures; the Council says the revision adds content for reliable implementation. Vulnerability measures for e-commerce merchants have been guideline measures since April 2025.

The five vulnerability measures e-commerce merchants take

The guidelines ask merchants to take all five. Use them as a checklist for your contractor.

  • Restrict which IP addresses can reach the admin screen (basic authentication if that is not possible), use two-step login, and lock the account after 10 failed logins or fewer.
  • Keep important files out of public directories (places visible from outside), and limit the types of file that can be uploaded.
  • Run vulnerability assessments or penetration tests (tests that assume an intrusion) regularly, fix what they find, and keep plugins and software up to date.
  • Install antivirus software, update its definitions and run regular full scans.
  • Take at least one measure against malicious validity checks and credit master attacks (trying mechanically generated card numbers).

The third item names assessments explicitly. An assessment does not make you "safe" once done. Doing it regularly and fixing what it finds are a pair.

How to read the relationship with the Installment Sales Act

The guidelines call themselves the "practical guideline" for the leak and fraud prevention measures the law requires, under the Ministry of Economy, Trade and Industry's basic policy for supervision under the Installment Sales Act (post-payment field). Taking the guidelines' measures, or equal or better ones, is regarded as taking the law's "necessary and appropriate measures". The guidelines also ask you to note that the law requires measures beyond those shown. Ask your card company, payment service provider or an expert which provisions apply to you.

Security Guidelines for Building and Operating E-commerce Sites (IPA)

IPA published this on 16 March 2023 in two parts, Part 1 for executives and Part 2 for practice. It names executives, staff and outside contractors as readers, so it can underpin the division of roles with a contractor.

Where should you start to check your own shop's state?

Before ordering an assessment, there is a ten-minute check you can do. An item you cannot answer is the first thing to ask your contractor.

  • Can you state which e-commerce system you use (EC-CUBE, WooCommerce, Shopify, custom) and its version?
  • Is the admin screen open only to named people and places, and are accounts of former staff or earlier agencies gone?
  • Did your contractor explain the payment method (redirect, embedded, in-house) to you in writing?
  • Do you have a list of external tags loaded on the checkout screen, and do you know who added each?
  • Is it written down whether site maintenance and vulnerability management are your job or the contractor's?

Which assessments suit an e-commerce site?

We assess in two stages, a tool scan and a person's review, and hand over a report. One re-assessment after fixes is free. All amounts exclude tax.

Shop situation Suggested assessment Guide price
A CMS-type shop such as EC-CUBE or WooCommerce; you want to know where you stand E-commerce site assessment (WordPress/CMS site assessment) from JPY 49,800 (up to 30 pages)
A custom-built shop; you want the purchase flow and member screens checked Web application assessment Lite or Standard from JPY 98,000 (up to 10 screens) / from JPY 198,000 (up to 20 screens, including screens behind login)
E-commerce running on WordPress, such as WooCommerce WordPress assessment from JPY 49,800 (up to 30 pages)

The amount rises with the number of pages or screens, how many screens behind login (member and admin screens) are included, and the number of extensions (paid plugins). Screens beyond the range can be added from JPY 10,000 per screen. Checking the purchase flow requires login, so for a custom-built shop we sometimes suggest Standard.

To see what is visible from outside, use the free URL check (JPY 0). If you cannot tell which assessment fits, tell us the name of the system you use through contact us. The formal quotation follows the free assessment.

Fixes and monitoring after an assessment

We repair the holes found, as needed. An individual vulnerability fix starts from JPY 10,000, quoted by content. Recovery from tampering or malware starts from JPY 29,800 and covers investigation, removal of malicious code and settings against recurrence.

After repair, holes return if component updates stop. Maintenance Lite is JPY 9,800 per month (excl. tax) and includes a monthly update, daily backups, tamper monitoring and a monthly report. For e-commerce on WordPress, AI monitoring service Guard Lite (JPY 5,000 per month, excl. tax, billed yearly in principle) adds a daily outside scan and tamper detection.

Related vulnerabilities and measures

E-commerce vulnerabilities are easier to read from two directions: the checkout screen and the build tool you use. The whole set of measures is in information leak measures and tampering measures.

What we take on, and what we do not

We take on assessments, fixes for the holes found, recovery from damage, and maintenance and monitoring after delivery. Ahead of any assessment we sign a non-disclosure agreement (NDA) and a consent form that name the shop's URLs, the period and the testing methods.

We do not assess the payment screen run by a payment service provider, which is outside what we can assess. We do not advise on whether you must report, or on interpreting laws such as the Installment Sales Act, because those need an expert's judgment. We also do not promise you will never be harmed: an assessment reduces the holes found at that time.

Frequently asked questions about e-commerce security

If we do not store card data ourselves, are we safe?

Not necessarily. The Council's guidelines say card data is still stolen from shops that do not store it, because of flaws in the site. Whether or not you store card data, you need vulnerability measures for the site and systems.

If customers are sent to a payment provider's screen, do we still need our own measures?

Yes. In the Personal Information Protection Commission's survey, 37% of direct causes were flaws that let a payment screen be tampered with. Protecting the admin screen, updating the components you use and sharing duties with contractors remain the shop's job whatever the method.

Does a small online shop need an assessment?

Yes. In the Commission's survey, about 40% of the 71 respondents had fewer than 50 employees. A small size does not change what is targeted when you handle card or member data. Begin with the free URL check, which reads only what a visitor could see.

How much does an e-commerce assessment cost?

For CMS-type shops such as EC-CUBE and WooCommerce, the WordPress/CMS site assessment starts from JPY 49,800 (excl. tax, up to 30 pages). For a custom-built shop, Web application assessment Lite starts from JPY 98,000 (excl. tax, up to 10 screens). The number of shop pages, member screens behind login and installed extensions moves the price. A formal quotation follows the free assessment.

Next step

Today, do three things. Confirm which e-commerce system and version you run, tidy the admin accounts, and list the external tags loaded on the checkout screen. At the same time, the free URL check gives you the outside view of your shop for JPY 0.

To compare your state with the guidelines or to settle an assessment scope, contact us. If a card company tells you about a leak, first contact your card company or payment service provider, then talk to us.

Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 18 November 2026.

Frequently asked questions

If we do not store card data ourselves, are we safe?

Not necessarily. The Council's guidelines say card data is still stolen from shops that do not store it, because of flaws in the site. Whether or not you store card data, you need vulnerability measures for the site and systems.

If customers are sent to a payment provider's screen, do we still need our own measures?

Yes. In the Personal Information Protection Commission's survey, 37% of direct causes were flaws that let a payment screen be tampered with. Protecting the admin screen, updating the components you use and sharing duties with contractors remain the shop's job whatever the method.

Does a small online shop need an assessment?

Yes. In the Commission's survey, about 40% of the 71 respondents had fewer than 50 employees. A small size does not change what is targeted when you handle card or member data. Begin with the free URL check, which reads only what a visitor could see.

How much does an e-commerce assessment cost?

For CMS-type shops such as EC-CUBE and WooCommerce, the WordPress/CMS site assessment starts from JPY 49,800 (excl. tax, up to 30 pages). For a custom-built shop, Web application assessment Lite starts from JPY 98,000 (excl. tax, up to 10 screens). The number of shop pages, member screens behind login and installed extensions moves the price. A formal quotation follows the free assessment.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.