Small Biz Primer · US small business Independent · plain-English guides for US small businesses
Plain-English business guides
Small Biz Primer

How to start & run a business, minus the jargon.

◆ New here? Start with How to Start a Business◆ 151 guides live today, more each week ◆ New here? Start with How to Start a Business◆ 151 guides live today, more each week
Business Core · N°05

PCI, Privacy, and Payment News Every Merchant Should Watch

PCI compliance, payment page scripts, and new state privacy laws are shifting fast. Here's what merchants need to watch and act on right now.

Payment compliance used to be something you set up once and forgot about. That's no longer true. Between the fully-enforced PCI DSS 4.0.1 standard, a wave of new state privacy laws, and tighter scrutiny of the scripts running on checkout pages, the rules that govern how you take money and handle customer data are moving faster than most small business owners realize.

If you accept card payments online or in person, a few changes over the past year have quietly raised the bar. Miss them and you risk failed assessments, higher processing costs, or fines. Below is a plain-English rundown of what actually changed, why it matters, and what to do about it.

What payment compliance changes should merchants watch?

The short answer: three things deserve your attention right now.

  1. PCI DSS 4.0.1 is now fully mandatory. Every "future-dated" requirement became enforceable on March 31, 2025. There is no more grace period.
  2. Payment page scripts are under a microscope. New requirements force you to inventory, authorize, and monitor every script that touches a checkout page.
  3. State privacy laws keep multiplying. Three more states added comprehensive privacy laws in January 2026, bringing the total to 19, each with its own rules on consent, data sales, and consumer rights.

Let's break each one down.

PCI DSS 4.0.1: the grace period is over

The Payment Card Industry Data Security Standard (PCI DSS) is the rulebook every business that stores, processes, or transmits cardholder data has to follow. Version 4.0 introduced more than 60 new or updated requirements, and roughly 50 of them were labeled "future-dated" best practices, meaning you had extra time to adopt them.

That time ran out. As of March 31, 2025, all of those requirements are fully enforceable under the current v4.0.1 release, according to the PCI Security Standards Council. Version 4.0.1 itself, published in June 2024, didn't add new rules; it clarified existing ones.

For most small merchants, the changes that bite hardest fall into a few buckets:

  • Expanded multi-factor authentication (MFA). MFA is now required for all access into the cardholder data environment, not just remote admin access.
  • Authenticated internal vulnerability scanning. Scans now have to run with credentials so they see what an attacker with a foothold would see.
  • Anti-phishing controls (Requirement 5.4.1). You need automated mechanisms to protect staff against phishing attempts.
  • Targeted risk analyses. Several controls now let you set your own frequency for certain tasks, but only if you document a formal risk analysis justifying it.

The practical takeaway: if your last self-assessment questionnaire (SAQ) was filled out under the old v3.2.1 rules, it's out of date. Talking to your acquirer or a Qualified Security Assessor before your next renewal will save you from a nasty surprise. If you're still choosing how you take cards in the first place, our guides to payment processing options and how to accept credit card payments walk through the setup before compliance even enters the picture.

The checkout-page script problem: Requirements 6.4.3 and 11.6.1

This is the change most e-commerce merchants underestimate, and it deserves its own section.

Attackers have spent years slipping malicious code into the third-party scripts that load on checkout pages, chat widgets, analytics tags, marketing pixels, and payment iframes. These "digital skimming" or Magecart attacks quietly harvest card numbers as customers type them. Two PCI requirements now target this directly:

  • Requirement 6.4.3 says you must maintain an inventory of every script that loads on a payment page, confirm each one is authorized, justify its business purpose, and verify it hasn't been tampered with.
  • Requirement 11.6.1 requires a change-detection mechanism that alerts you when scripts or the security-relevant HTTP headers on your payment page are modified without approval, checked at least weekly.

According to the Cloud Security Alliance, both became mandatory on March 31, 2025. In plain terms: you can no longer treat the code on your checkout page as a black box. You have to know what's there, why it's there, and get an alert the moment it changes.

For merchants using a hosted checkout from a reputable provider, much of this burden shifts to the platform, another reason the payment processing system you choose matters so much. If you run a custom cart or embed your own payment fields, this is squarely your responsibility. Understanding how a modern hosted flow like Shop Pay handles the checkout can help you see why offloading the payment page to a specialist often reduces your compliance scope dramatically.

Privacy laws: the map keeps redrawing

PCI compliance protects card data. Privacy laws protect everything else you collect, names, emails, browsing behavior, purchase history, and they're expanding fast.

On January 1, 2026, Indiana, Kentucky, and Rhode Island brought their comprehensive consumer privacy laws into effect, pushing the number of states with such laws to 19, per legal analysis from Koley Jessen. The common threads across these laws:

  • Consumers can access, correct, delete, and port their data.
  • Opt-in consent is required before processing sensitive data.
  • High-risk processing often triggers a Data Protection Impact Assessment.
  • Enforcement sits with state attorneys general, with civil penalties commonly running $7,500 or more per violation.

Most of these laws only apply once you cross certain thresholds, often processing the data of 100,000 residents of a state, or 25,000 while earning a meaningful share of revenue from selling data. A neighborhood shop is unlikely to trip those numbers. But a growing online store selling across state lines can, faster than you'd think, and the thresholds differ from state to state.

The safe posture for a scaling business: publish a clear privacy notice, offer a genuine way to opt out of data sales, honor deletion requests, and don't collect data you don't actually need. Building those habits early is far cheaper than retrofitting them after a complaint. If privacy and data handling are part of a broader compliance push, it pairs naturally with getting your legal foundation right when you register your business.

What to do this quarter

You don't need to boil the ocean. A focused checklist covers most of the exposure:

  • Refresh your PCI self-assessment against v4.0.1 and confirm which SAQ type applies to you.
  • Turn on MFA everywhere that touches payment systems or admin accounts.
  • Inventory your checkout-page scripts and set up change-detection alerts, or confirm your provider does it for you.
  • Review your privacy notice and make sure opt-out and deletion requests actually work.
  • Ask your processor what compliance responsibilities they cover versus what falls on you. The answer often surprises merchants.

None of this is glamorous, but it's the kind of back-office discipline that separates businesses that scale cleanly from ones that hit a wall. Compliance is quietly becoming a competitive edge: it lowers your breach risk, keeps processing costs stable, and builds the customer trust that repeat sales depend on.

The bottom line

PCI compliance and privacy law are no longer occasional paperwork, they're an ongoing operating requirement. The 2025 PCI deadline and the steady march of new state privacy laws mean the standard you met two years ago probably isn't the standard you're held to today. Watch the script-integrity rules especially closely if you sell online, and treat your privacy notice as a living document, not a one-time template.

Not sure where your setup stands? Start by reviewing your current payment processing system and asking your provider exactly which parts of PCI DSS 4.0.1 they handle for you, then close whatever gaps are left.


Sources: PCI Security Standards Council, Cloud Security Alliance, Koley Jessen.