PCI DSS is the security standard that card networks require of every merchant that accepts card payments, including online. HaiSoft helps you configure and secure the server side to meet PCI DSS v4.0.1 requirements, in partnership with SiteLock. Support is quoted individually by our team in Orléans.
In online business, the security of card transactions is paramount. Compliance with PCI DSS (Payment Card Industry Data Security Standard) is not only a regulatory requirement for businesses that process card payments; it is also essential to protect your customers' data and maintain trust in your services. HaiSoft, in partnership with SiteLock, simplifies the PCI DSS certification process. We analyse your server and website to check their compliance and guide you through the adjustments needed to meet the required security standards.
Achieving PCI DSS compliance can seem complex and intimidating. We help simplify this process by conducting a comprehensive analysis of your environment to identify gaps against PCI standards and provide clear recommendations to address them.
By complying with PCI DSS standards, you implement security measures that protect your customers' sensitive information from data breaches. This includes security measures such as encryption, firewall usage, and strict access controls.
Customers are increasingly aware of online transaction security. By displaying your PCI DSS compliance, you communicate a strong commitment to security, which enhances customer confidence in your ability to protect their personal and financial data.
Businesses compliant with PCI DSS standards often find it easier to form partnerships and maintain good relationships with banks and other financial institutions. This compliance can also reduce costs associated with financial transactions and processing fees.
PCI DSS (Payment Card Industry Data Security Standard) is the data security standard for payment cards. It is published by the PCI Security Standards Council (PCI SSC), founded in 2006 by American Express, Discover, JCB, Mastercard and Visa. It applies to any organisation that stores, processes or transmits card data, and also covers e-commerce websites that outsource payment to a provider: their scope is then reduced, but not zero.
It is not a law: compliance is required contractually by your bank (the acquirer) and by the card networks. The current version is PCI DSS v4.0.1, published in June 2024 and the only active version since 31 December 2024; the new v4 requirements, initially best practices, have been mandatory since 31 March 2025.
The standard has 12 requirements, grouped into 6 goals:
| Goal | Requirements |
|---|---|
| Secure networks and systems | 1. Network security controls (firewalls); 2. secure configurations |
| Protect account data | 3. Protection of stored data; 4. strong cryptography during transmission over public networks |
| Vulnerability management | 5. Protection against malware; 6. development and maintenance of secure systems and software |
| Access control | 7. Access restricted to business need to know; 8. user identification and authentication; 9. restricted physical access |
| Monitoring and testing | 10. Logging and monitoring of access; 11. regular security testing |
| Security policy | 12. Information security policies and programmes |
Card networks classify merchants into levels according to their annual transaction volume. The largest (more than 6 million transactions a year) have their compliance assessed on site by a Qualified Security Assessor (QSA). The vast majority of merchants validate their compliance every year with a self-assessment questionnaire (SAQ) and an attestation of compliance (AOC) sent to their bank.
The questionnaire depends on how you accept cards. For an e-commerce website:
| Questionnaire | Situation |
|---|---|
| SAQ A | Payment is fully outsourced to a PCI DSS compliant provider: redirection to its payment page or a form embedded in an iframe. No card data passes through your server. |
| SAQ A-EP | Payment is outsourced to a provider, but your website controls elements of the payment page (for example a form that posts data directly to the provider) and can therefore affect its security. |
| SAQ D | All other cases, in particular when your server receives, processes or stores card data. |
Since the January 2025 update of SAQ A, the requirements on payment page scripts (6.4.3) and change detection (11.6.1) are no longer part of SAQ A, but merchants must confirm that their website is not susceptible to script attacks. They still apply to SAQ A-EP and D. Your bank confirms which questionnaire applies to you.
PCI DSS requirement 11.3.2 calls for an external vulnerability scan at least once every three months, and after any significant change, performed by an Approved Scanning Vendor (ASV) whose solution is approved each year by the PCI SSC. The scan must “pass”: no medium or high severity vulnerability may remain, otherwise it must be fixed and the scan run again.
These scans also apply to SAQ A merchants: the page of your website that redirects to the provider's payment page, or embeds it, must be scanned. Passing scan reports are kept and provided to your bank with your questionnaire.
Hosting your website with a provider does not make you compliant automatically: PCI DSS compliance is a shared responsibility. For PCI DSS, your hosting provider is a third-party service provider. You must keep a list of these providers, know exactly which requirements each one is responsible for (requirement 12.8) and check their compliance status every year. The provider, for its part, must acknowledge in writing the responsibilities it takes on (requirement 12.9).
At HaiSoft, managed services cover part of the technical measures expected on the server: security updates for the operating system and server software, 24/7/365 monitoring, and hosting in secure datacentres in France (in Tours, a Tier III datacentre certified ISO 27001). Your side includes, in particular, choosing the payment provider, updating your website and its modules, managing administrator accounts and completing the annual questionnaire. Discover our datacentres and our service commitments.
HaiSoft works with SiteLock, a website security specialist that we already offer for the antimalware protection of hosted websites. SiteLock is now part of the Sectigo group, whose HackerGuardian scanning solution is approved as an ASV by the PCI SSC. SiteLock's PCI compliance service combines external vulnerability scans with help completing the self-assessment questionnaire.
For its part, HaiSoft helps you configure and secure the server side in line with PCI DSS requirements. Other needs, such as vulnerability scans or help with the questionnaire, are agreed with you. Read also our article SiteLock, the answer to hacking.
PCI DSS (Payment Card Industry Data Security Standard) is the data security standard for payment cards, published by the PCI Security Standards Council. It applies to any organisation that accepts, processes, transmits or stores payment card data.
Yes. Outsourcing payment to a compliant provider greatly reduces your scope, but you still have to validate your compliance, usually with SAQ A or SAQ A-EP, and have quarterly ASV scans of your website carried out.
It is not a legal obligation but a contractual one: your bank and the card networks require it in order to accept card payments. They also set the consequences of non-compliance.
PCI DSS v4.0.1, published in June 2024. It has been the only active version since 31 December 2024, and all its requirements have been mandatory since 31 March 2025.
It depends on how you take payments: SAQ A if payment is fully outsourced to a provider (redirection or iframe), SAQ A-EP if your website controls elements of the payment page, SAQ D if your server receives or stores card data. Your bank confirms which questionnaire applies.
It is an external vulnerability scan performed by a provider approved by the PCI SSC (Approved Scanning Vendor). PCI DSS requires one at least every three months and after any significant change; it must pass, meaning no medium or high severity vulnerability.
No. Compliance is shared: HaiSoft manages and secures the server, but choosing the payment provider, updating the website and its modules, managing access and completing the annual questionnaire remain your responsibility. Our support helps you cover everything.
SiteLock, a HaiSoft partner, specialises in website security. Its PCI compliance service combines external vulnerability scans with help completing the self-assessment questionnaire. SiteLock is part of the Sectigo group, an ASV approved by the PCI SSC.
HaiSoft's support covers the configuration and security of the server side. Other needs, such as vulnerability scans or help with the self-assessment questionnaire, are agreed with you. It is quoted individually, according to your situation.
Contact us using the contact form or by phone on +33 974 078 078 (04 268 03 73 from Belgium). We review your payment method, your server and your website before offering you support.
Updated on