Practical Guides

PCI DSS for Small Businesses: Obligations, Costs and How to Simplify

February 2, 2025 6 min read PCI Proxy EU

PCI DSS for small businesses is a reality that many small business owners ignore until their acquirer or PSP sends a compliance request. PCI DSS has no minimum revenue thresholds: any organisation that accepts card payments is subject to its requirements. For small businesses, the key is understanding which obligations actually apply and how to manage them without a dedicated IT manager.

PCI DSS small businesses: obligations and how to simplify

Who must comply with PCI DSS: small businesses included

The PCI DSS compliance obligation arises from the contract with the acquirer or PSP that enables card payments. It does not depend on company size, number of employees or revenue: it depends on accepting, processing, storing or transmitting card payment data. A store with a single POS, a small e-commerce with a few dozen transactions per month, a tradesperson accepting online payments: all are subject to PCI DSS.

The good news for small businesses is that the compliance level varies based on transaction volume. A merchant with fewer than 20,000 annual e-commerce transactions falls within Level 4, the level with the least onerous requirements. In many cases they can independently complete an SAQ, without needing a certified external auditor. The bad news is that "less onerous" does not mean "absent": the SAQ must be completed, basic controls must be implemented, and non-compliance has real consequences.

What an SME risks without PCI DSS compliance

Non-compliance consequences do not necessarily arrive immediately: they often emerge only following a breach or an acquirer audit. The main penalties are: monthly fines from card schemes (Visa, Mastercard) that can reach $100,000 per month in the most serious situations; increased interchange fees; forensic investigation costs at the merchant's expense in case of breach; and, in the worst case, revocation of the ability to accept card payments, which for an SME can mean closure.

A breach exposing real card data has an estimated average cost between €50,000 and €200,000 for an SME, including forensic costs, customer notifications, fraud reimbursement and potential legal actions. This is not a theoretical risk: SMEs are frequently targeted by attackers precisely because they have less protected systems than large companies yet still handle real card data.

How to simplify PCI DSS for small businesses

The most effective strategy for an SME is to eliminate direct handling of card data from the payment architecture. If the checkout uses a PCI DSS certified hosted page or a client-side SDK that sends data directly to the provider's vault, the SME never sees a PAN. The CDE perimeter becomes almost null, the applicable SAQ is SAQ A (a few dozen questions), and compliance is managed independently in a few hours per year.

PCI Proxy EU is designed exactly for this scenario: providing the SME with a Level 1 certified vault, documented APIs, ready-to-use SDKs and support to complete the SAQ A. The service cost is proportionate to transaction volume and is lower than the annual cost of traditional compliance (consultant, ASV vulnerability scan, possible pen test). A small business adopting this architecture reduces risk, simplifies obligations and focuses on its business.

Frequently asked questions

Is a small shop with a POS required to comply with PCI DSS?

Yes. Any merchant accepting card payments through a physical POS is subject to PCI DSS. In practice, if the POS is provided directly by the acquirer or bank and is not connected to the business network, the perimeter is very limited and the applicable SAQ is often SAQ B, with minimal requirements. The acquirer should have already communicated the applicable level and SAQ type at the time of service activation.

Will my acquirer notify me if I'm not compliant?

Not systematically. The acquirer may send SAQ completion requests or reminders if it does not receive compliance documentation within prescribed deadlines, but it does not monitor your technical compliance status in real time. The responsibility for being compliant lies with the merchant: do not wait for a notification to start the process.

Can I manage PCI compliance without a dedicated IT manager?

Yes, with the right architecture. If you use a hosted page or certified SDK and your CDE is minimal, the SAQ A can be completed by the owner or an administrative manager without specific technical skills. The key is choosing a payment solution that reduces the perimeter to a minimum: with PCI Proxy EU, many SMEs manage compliance independently.

Want to manage PCI DSS compliance without a dedicated IT team and without disproportionate costs? Discover PCI Proxy EU.

PCI Proxy EU Team

RoxPay, PCI DSS tokenization in Europe

Content reviewed by payment and PCI DSS compliance experts.

PCI DSS simple even for SMEs

With PCI Proxy EU, PCI DSS compliance is managed without a dedicated IT team and without disproportionate costs.