eID verification in Latvia: Smart-ID, eParaksts and the rules
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
Latvia’s digital identity landscape centers on Smart-ID, the most widely used option with about 1.2 million local users, alongside the state-run eParaksts mobile service, eID card, and eParaksts smart cards operated through LVRTC. eParaksts mobile and the eID card belong to Latvia’s eIDAS-notified scheme at substantial and high assurance levels, while Smart-ID is nationally qualified but not EU-notified. Latvian law generally equates qualifying electronic identification with in-person identity verification, and remote AML checks can use secure electronic signatures, high-security eIDs, video identification, bank payments, or document-and-selfie methods; EU AML rules due from July 2027 will explicitly recognize substantial- and high-assurance eIDs. Businesses are advised to prioritize Smart-ID for Latvian users while retaining document-based verification for foreign residents, visitors, and others without eligible eIDs, and they should account for age-verification needs and forthcoming European Digital Identity Wallet requirements, including potential acceptance obligations from December 2027. The source also describes Didit’s Smart-ID integration, planned support for eParaksts mobile, and fallback document checks using NFC chip reading, liveness detection, and face matching.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.