Skip to content
Services
PCI DSSISO 27001SOC 2GDPRPenetration TestingNIST CSFvCISODORA
Company
Case StudiesPartnersTrust CenterBlogGlossaryFAQFree AssessmentContact
Industries
FintechHealthcarePaymentsSaaS
AboutResourcesVeedar

PCI DSS certification in the EU: requirements, timelines and country specifics

Search for "PCI DSS certification in the EU" and you will find a lot of pages implying there is an EU version of the standard, an EU authority behind it, and an EU certificate at the end. There is none of those things. What genuinely differs between Dublin, Nicosia, Valletta, Luxembourg City and London is not the standard; it's the regulatory stack sitting next to it, and who signs off on what.

This article is the orientation piece we wish existed when a founder first asks us where to start. It covers what is identical everywhere, what is really country-specific, how long the work takes, and how to sequence PCI DSS against the EU obligations that landed in 2025 and 2026.

Is PCI DSS legally required in the EU?

No. Take four markets as worked examples: Ireland, Cyprus, Malta, and Luxembourg. In none of them is PCI DSS a legal or licensing requirement for a payment institution or an electronic money institution. The same rule works for the other European countries. It is a contractual requirement, and it reaches you through your acquirer agreement and the card scheme rules behind it.

That single fact reorders the whole project. Nobody from your national regulator will ask to see an Attestation of Compliance at authorisation. Your acquirer will. Your enterprise customer's procurement team will. And a card scheme can, through your acquirer, apply commercial consequences if you are not validated at the level your volumes require.

Some plain-English definitions, because the acronyms hide what is going on:

PCI DSS is the Payment Card Industry Data Security Standard is a twelve-requirement set of standards published by the PCI Security Standards Council, currently at version 4.0.1 (published June 2024). It applies to any organisation that stores, processes, or transmits payment card data, or that can affect the security of someone else's card data.

CDE is your cardholder data environment: the systems that touch account data, plus everything that can affect their security.

QSA, a Qualified Security Assessor, is a company or individual assessor qualified by the Council to perform assessments.

SAQ is a Self-Assessment Questionnaire, in one of several types depending on how you accept payments. RoC is a Report on Compliance, the full assessment documented by a QSA. Both paths end in an AoC, the Attestation of Compliance, the short signed form your partners actually ask for.

And one correction worth making early, because it changes how you brief your board: the Council does not certify merchants or service providers. There is no PCI certificate. You validate compliance for a point in time, and your acquirer and the card brands decide which validation they will accept. "Certification" is the word the market searches for; "validation" is the word the standard uses.

What is the same in every EU country?

More than most founders expect. The standard itself is global and is not localised:

The twelve requirement areas are identical in every market. Version 4.0.1 is the current version everywhere, and the 51 future-dated requirements that became mandatory on 31 March 2025 apply in Dublin exactly as they do in Dubai: multi-factor authentication across the whole CDE, continuous rather than annual monitoring, payment-page script integrity controls, and targeted risk analyses justifying the frequency you have chosen for flexible requirements.

Validation levels are set by the card networks, not by any EU body, and depend on your annual transaction volume and whether you're a merchant or a service provider. The brands set the thresholds, and your acquirer confirms where you land, so treat comparison-site numbers as indicative, and get your level in writing before you build toward anything.

Service providers carry the same additional obligations everywhere, including confirming that PCI DSS scope is still accurate at least once every six months and after any significant change to the in-scope environment, not annually (Requirement 12.5.2.1, a future-dated requirement that also became mandatory on 31 March 2025).

If someone offers you a "European PCI DSS certificate," or an assessment scoped to EU rules specifically, that is a marketing construct rather than a standards one.

So what actually differs by country?

Four things, and none of them are the requirements.

First, which regulator you answer to for everything adjacent. PCI DSS has no regulator. DORA, NIS2, and your national supervisor's circulars do, and those obligations overlap heavily with the evidence you are already producing for a PCI assessment, without any of them referencing PCI DSS. Poland is the sharpest illustration: KNF never named PCI DSS in Rekomendacja D or in its cloud-computing communication, and it repealed both with effect from 17 January 2025 because DORA supersedes them. The familiar Polish IT checklist is simply gone, and DORA plus its technical standards is what remains. Luxembourg's CSSF made a comparable move, replacing Circular 24/847 with Circular 25/893 for DORA entities and for payment service providers outside DORA scope — anyone still working to 24/847 is working to a superseded circular. In Cyprus, the supervisor for payment institutions and EMIs is the Central Bank of Cyprus rather than CySEC, a distinction that catches out founders and, occasionally, their advisers. And in Malta, the MFSA's cybersecurity guidance notes do list PCI DSS among recognised standards — but that document is non-binding guidance addressed to virtual-asset operators, not payment institutions, so anyone citing it as a Maltese mandate for a PSP has misread it.

Second, your acquirer's practice. Acquirers differ in how they set levels, what they accept as evidence, how they handle a lapsed validation, and how much notice they give. Two payment companies of identical size in different countries can face materially different paperwork purely because of who they bank with.

Third, who can assess you. QSA companies are qualified per region and per country, not globally. A QSA may only perform assessments in the geographies for which it qualifies. That does not mean your assessor must be headquartered in your country — a Maltese EMI can perfectly well engage a QSA based elsewhere — but it does mean you should check the Council's public QSA directory for the region before signing, and confirm the firm's status is current. If you operate across several markets, the question to ask a prospective assessor is not where they are based but how many of your countries they can actually cover, because a firm qualified in one of them will have to hand the rest to someone else.

Fourth, the language and location of the work. Remote assessment has been formally permitted since the Council published its remote assessment guidance in September 2021, but onsite remains the default, and it is the payment brands and acquirers who decide whether a remote assessment is acceptable for their programme. Worth asking early if your team is distributed.

The EU obligations now sitting alongside your PCI programme

This is the part that has changed most since 2024, and it is the reason a 2026 PCI project looks different from a 2023 one.

DORA applies to you, and probably in full. The Digital Operational Resilience Act has applied since 17 January 2025. Payment institutions and electronic money institutions are explicitly in scope — including exempted ones. The commonly repeated idea that small firms get a lighter regime is half true and misread constantly: the simplified ICT risk management framework is available to waiver-exempt payment institutions and EMIs, not to small ones. An authorised payment institution with twelve staff is subject to the full ICT risk management regime. Headcount is not the test. Poland spells this out more plainly than most: a mała instytucja płatnicza, a small payment institution, registered rather than authorised, is the Polish form of the PSD2 waiver, and the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) states directly that this is the category the simplified framework is for. A krajowa instytucja płatnicza or an e-money institution gets the full regime, whatever its size.

Three DORA workstreams collide with a PCI calendar in practice. Incident reporting runs on a much shorter clock than most teams are built for: an initial notification within 4 hours of classifying an incident as major, and no later than 24 hours from becoming aware; an intermediate report within 72 hours of that notification; a final report within a month. The register of ICT third-party providers is an annual submission with a fixed window — and the window is different everywhere. The Central Bank of Ireland's 2026 cycle ran 2–31 March against a 31 December reference date, while Poland's goes to KNF's own reporting system against a 31 March reference date. If you hold licences in both, those are two different deadlines off two different sets of data. Resilience testing sits alongside, though threat-led penetration testing is designated on a risk basis by the national authority and most firms of this size will not be designated.

The register is worth dwelling on, because the first cycles have been instructive. The Central Bank of Ireland's second submission window ran 2–31 March 2026 against a 31 December 2025 reference date, and the supervisory feedback from the first cycle was not about security posture at all — it was about data hygiene: invalid identification codes, missing or placeholder LEIs. The firms that struggled were not the insecure ones. They were the ones who had never had to name every ICT supplier in a machine-readable format before.

NIS2 mostly steps aside for you, but not entirely. Where a firm is a financial entity under DORA, DORA takes precedence as the sector-specific act. That carve-out is real, but it is not total: a group with a non-financial arm can still be pulled in, and national transposition has been uneven. Luxembourg transposed with an act of 5 May 2026, in force 10 May 2026, supervised by the ILR. Cyprus amended its existing law in April 2025, with the Digital Security Authority as the competent authority. Malta transposed it by legal notice in April 2025. Poland transposed it by an act of 23 January 2026, in force 3 April 2026, so there is live national law to comply with. Ireland had still not transposed as of mid-2026 and was referred to the Court of Justice in July 2026. If you operate across more than one of these, do not assume a single answer.

GDPR is the third clock. Cardholder data is personal data, and the EDPB treats card details as a category where a breach presents high risk in and of itself — meaning a card data breach will usually clear the bar for notifying affected individuals, not just the supervisory authority. Run the arithmetic on a single incident, and you have a 72-hour GDPR notification, a 4-hour DORA classification clock, and a card-scheme forensic investigation with its own reporting deadlines, all from the same event. If your incident response plan addresses only one of them, it addresses none of them properly.

Frequently asked questions

Is PCI DSS mandatory in the EU?

Not as a matter of EU or national law. It is a contractual requirement imposed through card scheme rules and your acquirer agreement. The practical consequence is the same — you cannot process card payments at scale without it, but no regulator enforces it, and no authorisation depends on it.

Is there an EU-specific version of PCI DSS?

No. Version 4.0.1 is the current version globally, and the requirements are identical in every country. There is no EU certificate and no EU PCI authority.

Does the QSA have to be based in my country?

No, but the QSA must qualify for your region or country, because assessors may not work outside the geographies they are qualified for. Check the PCI SSC's public QSA directory and confirm the firm's status is current before you sign.

Does DORA replace PCI DSS?

No. They are separate regimes with different owners and no formal mapping between them. DORA is EU law supervised by your national authority; PCI DSS is a card scheme standard enforced through your acquirer. Meeting one does not satisfy the other, though a significant part of the underlying evidence serves both.

Does Brexit change anything for a UK payment company?

For PCI DSS, no — the card schemes are global. For everything adjacent, yes: DORA and NIS2 do not apply in the UK, and the FCA/PRA operational resilience regime takes their place.

How much does PCI DSS certification cost in Europe?

It depends almost entirely on scope and validation path, not on country. The single largest cost lever available to you is reducing what falls inside the cardholder data environment before the assessment begins.

Where to go next

If you are somewhere between "a partner mentioned PCI" and "we should probably start," the useful first step is not choosing an assessor. It is drawing an honest boundary around your cardholder data environment and finding out which validation path your acquirer actually expects.

That is a one-hour conversation: your architecture on a screen, a clear answer on what is genuinely in scope, which path applies, and a realistic timeline against your regulatory calendar. Book a scoping call, and we will tell you where you stand, whether or not you end up working with us.

Mölnir is a QSA-led cybersecurity and compliance partner for payment companies, working across 28 countries. 100+ PCI DSS audits delivered, 30+ enterprise clients.

Comments

Be the first to comment.

Leave a comment