DSIT Explains DVS Statement Requirements

Why It Matters

Accurate certification language protects user trust and prevents regulatory penalties, shaping the credibility of the UK’s digital identity ecosystem.

Key Takeaways

• DSIT restricts DVS claims to trust‑framework certification only
• AML or KYC certifications cannot be advertised by DVS providers
• Providers must list specific supplementary codes they meet
• Service descriptions should cite sector use cases, not regulations
• Misleading claims may lead to certification revocation

Pulse Analysis

The rapid expansion of digital verification services (DVS) has placed the UK’s identity ecosystem under heightened scrutiny. While regulators such as the Financial Conduct Authority allow certified DVS to be used for identity checks under anti‑money‑laundering rules, the technical standards that underpin certification are set by the Digital Identity and Attributes Trust Framework and its supplementary codes. DSIT’s latest guidance draws a clear line between regulatory compliance and technical certification, ensuring that providers do not conflate the two in marketing materials.

By mandating that DVS providers reference only the specific supplementary codes they have been assessed against, the government aims to eliminate vague or misleading claims that could erode user confidence. Misrepresenting a service as “AML‑certified” suggests a level of regulatory endorsement that does not exist, potentially exposing providers to enforcement action and revocation of their certification status. The guidance also encourages firms to frame their offerings in terms of sector relevance—such as property, employment, or conveyancing—providing clearer context for customers while avoiding any implication of blanket regulatory compliance.

For the industry, this clarity translates into a more trustworthy market where certification signals genuine technical robustness rather than regulatory shortcuts. The Office for Digital Identities and Attributes (OfDIA) is finalising detailed application guidance that will embed these best‑practice descriptions into the certification process. Providers that adopt the recommended language early will likely enjoy smoother certification journeys and stronger market positioning as regulators and end‑users alike demand transparent, standards‑based assurances.