How IDnow delivers QTSP status, ETSI 119 461 certification, and eIDAS compliance in a single qualified IDV platform

How does IDnow prove it meets the AMLR compliance and certification bar for qualified identity verification?

IDnow holds Qualified Trust Service Provider (QTSP) status on the EU Trusted List, is independently certified against ETSI TS 119 461 for remote identity proofing, and operates inside the full eIDAS regulatory framework. You don’t have to take our word for any of it. The QTSP listing sits on a public register, the ETSI certificate comes from an independent assessor, and both map straight onto the legal definitions AMLR uses. So when a regulated institution picks IDnow, it is picking a provider a conformity assessment body has already vetted and a Member State supervisor has already listed. The compliance work doesn’t vanish. But the heavy lifting no longer lands on your team.

The IDnow approach: certification is the foundation, qualification is the proof

Why credentials matter, not just capabilities

AMLR Article 22 does more than name remote identity verification as a valid CDD method. It names Qualified Trust Services as the route, which means the service has to come from an entity formally recognised as a Qualified Trust Service Provider under eIDAS. That one word, qualified, carries the weight.

A vendor can build sophisticated document verification and never become a QTSP. Technical polish is not the same as legal qualification. For a regulated institution, using a non-QTSP to deliver what AMLR treats as a Qualified Trust Service opens a compliance gap that no contract clause can close. The qualification has to sit with the provider, instead of the paperwork between you.

IDnow holds QTSP status. It is recorded on the EU Trusted List, the public register each Member State’s supervisory body maintains, so anyone can confirm it in a minute without asking us first. That listing is the primary proof that the qualified-trust route under AMLR Article 22 is genuinely open to institutions using the IDnow platform.

What ETSI TS 119 461 adds and why it matters

QTSP status is a legal designation. ETSI TS 119 461 is the technical standard that spells out how remote identity proofing for Trust Services must actually be carried out. It sets requirements for the proofing process: document authenticity checks, biometric comparison, liveness detection, fraud controls, and the assurance levels each of those has to reach.

Conformity is assessed by an independent conformity assessment body. It is not self-declared, and it is not a checkbox. The assessor examines whether the real process matches the standard, at the level of detail regulators and auditors expect to see. IDnow has passed that assessment, and the certificate is verifiable from the assessment body itself, with no IDnow marketing in the loop.

For a buyer, the effect is concrete. The proofing engine behind IDnow’s automated and video-based verification has been benchmarked by a third party against the exact standard eIDAS and AMLR reference. The assurance level is documented rather than asserted.

eIDAS as the regulatory frame that connects everything

eIDAS, and its updated form eIDAS 2.0 under Regulation (EU) 2024/1183, is the legal framework QTSP status lives inside, and the framework under which EUDI Wallets and Qualified Electronic Attestations of Attributes (QEAAs) operate. It is not a separate certificate. It is the architecture the other credentials hang from.

Working inside eIDAS means IDnow’s qualified services are legally recognised across every EU Member State, not only where the QTSP status was first granted. For a bank onboarding customers in France, Germany and Poland at once, or planning to, that cross-border recognition is the part of eIDAS that actually matters.

Taken together, QTSP status, ETSI TS 119 461 certification, and eIDAS compliance cover the full AMLR compliance and qualification picture asks of the qualified-trust route. They complement each other rather than repeat each other, and they stack across every verification method IDnow runs.

How the credentials map to the methods

The table below shows how IDnow’s qualifications apply across the verification methods AMLR recognises.

No method sits outside the qualified framework. Every route a regulated institution needs to offer from 10 July 2027 is covered by credentials that are independently audited and publicly verifiable.

The spectrum of AMLR compliance: why partial qualification is a hidden risk

Plenty of IDV vendors cover part of this picture. Some have built strong document verification but hold no QTSP status, so their service cannot formally count as a Qualified Trust Service under AMLR. Some have earned QTSP status but never been assessed against ETSI TS 119 461, so the proofing process has never been independently benchmarked. Some are eIDAS-aware without being eIDAS-qualified.

Each gap leaves the buyer with a different problem.

No QTSP status: the qualified-trust route under AMLR Article 22 is legally closed to you. You either carry a compliance gap or stand up a parallel qualified process, which adds cost and operational drag.

No ETSI TS 119 461 certification: the proofing process has never been independently assessed. When regulators and auditors review your CDD programme, they find vendor assurance where third-party evidence should be. That is a defensibility problem, not merely a technical one.

eIDAS-aware but not eIDAS-qualified: cross-border recognition of Qualified Trust Services depends on membership of the eIDAS framework. A provider outside it cannot deliver legally recognised services in Member States whose supervisory bodies look to the EU Trusted List.

None of this is theoretical. AMLR enforcement starts in July 2027, and the regulators reviewing CDD programmes will ask whether the qualified-trust route is genuinely qualified, not just functionally similar. The gap between a QTSP and a vendor who looks like one is a matter of public record.

Why the full spectrum is harder to replicate than it looks

Holding QTSP status, keeping ETSI TS 119 461 certification current, and operating inside eIDAS is not a one-time achievement. Each one demands recurring audit cycles, regulatory engagement, and process governance. QTSP status carries continuous supervisory oversight. ETSI TS 119 461 conformity needs periodic re-assessment. eIDAS 2.0 obligations keep shifting as Member State implementation matures and the EUDI Wallet ecosystem takes shape.

For the vendor, that is a standing operational cost. For the buyer, it is the assurance that today’s qualifications will still be in place, and still current, the day regulators come to examine the programme.

So the real question in procurement is not whether a vendor cleared a qualification once. It is whether they have the governance, the regulatory relationships, and the internal process to keep renewing it. That is where the distance between a QTSP and a vendor who hopes to become one starts to bite.

How to verify our claims

Don’t take any vendor’s word, ours included. Cross-check against independent sources:

• EU Trusted List: the authoritative public register of Qualified Trust Service Providers. It confirms QTSP status directly, with no vendor documentation involved, and it is the primary proof that the qualified-trust route under AMLR Article 22 is legally available.
• ETSI TS 119 461 certificate and conformity assessment body: issued by an independent body, not self-declared, and verifiable straight from the assessor. It proves the remote proofing process has been benchmarked against the standard eIDAS and AMLR reference.
• Primary regulatory texts: Regulation (EU) 2024/1624 (AMLR) and Regulation (EU) 2024/1183 (eIDAS 2.0) on EUR-Lex define the obligations and the legal framework qualified services operate within.

FAQs

Every AMLR-recognised method, one qualified platform, and the audit trail kept ready for you.

→ See how IDnow’s Trust Platform covers every AMLR-recognised verification route