Readiness

Ready for the EU requirements: five signature formats and the EUDI wallet

Two changes are reaching electronic signatures in Europe: from 2027 public sector bodies must recognise five EU signature formats, and from the end of 2026 Member States must offer a European Digital Identity Wallet. Tvarka is ready for both.

The format work already runs in production and is verified by an independent European Commission validator. The wallet work is prepared: the signing flow is designed so a wallet slots in as one more method, and integration with the EU reference components can be demonstrated today.

Updated 2026-08-28. Sources are listed at the foot of the page.

1. Signature formats: Regulation (EU) 2026/248

From 23 February 2027, a public sector body that requires an advanced electronic signature for an online service must recognise every format listed in Annex I of the Regulation. Tvarka produces them already. The table below is not a promise: it is what the European Commission's reference DSS validator said about documents our own production code created.

Format Where Tvarka uses it DSS validator verdict
PAdES Signing PDF documents – the ordinary path in Tvarka Sign PAdES-BASELINE-T
XAdES ASiC-E containers and ADOC XAdES-BASELINE-T
CAdES Standalone CMS signatures through the Tvarka API CAdES-BASELINE-T
JAdES System interfaces – signed API responses JAdES-BASELINE-T
ASiC containers ASiC-E with XAdES and ASiC-E with CAdES signatures Both signatures in the container – BASELINE-T

The verdicts come from DSS 6.4 runs against documents built by the same production code that serves customers. So that a level cannot quietly drop, the format check is part of automated regression control: if a signature level fell, the tests would break before anything shipped.

Tvarka Sign also continues to create and check ADOC, so through the transition you can work in both the national and the European formats.

2. The EUDI wallet: ready to connect

The EU Digital Identity Wallet (EUDI) is a state-recognised app that holds identity and documents on a phone, established by the amended eIDAS Regulation (EU) 2024/1183. Member States must offer wallets by the end of 2026, and from the end of 2027 regulated-sector services must accept them.

We did the homework early, so what we are waiting for is the official wallet, not the technology:

  • The formats already match. A signature created through a wallet is the same standard qualified signature (PAdES, XAdES, ASiC) that Tvarka creates and verifies today. Being ready for the formats is being ready for the wallet.
  • The flow is designed for it. Signing methods are a separate layer in Tvarka, so a wallet slots in beside Smart-ID, Mobile-ID, USB/eID and NFC without changing document flows, pricing or what the user sees.
  • The integration is tested against the EU reference components. We run the European Commission's own published reference software and drive a real OpenID4VP request through it.

What that last point means concretely, and what we can show today:

Step What it establishes
A presentation transaction is created Tvarka speaks to the reference verifier in its own protocol, and our request shape is accepted
The request object is retrieved The wallet is handed a cryptographically signed object (ES512), not an unauthenticated payload
The one-time value returns The value we generated survives unchanged into the request the wallet answers, so replay protection works
The attributes requested The wallet is asked for exactly the declared fields and not one more, so data minimisation holds technically rather than by promise
The QR code The same request is scannable by phone, so the cross-device scenario is prepared too

So when an official wallet goes live in Lithuania, what remains for us is connecting it to a flow that already runs and has been tested, rather than starting from a blank page. Until then nothing changes: you sign in Tvarka with the usual qualified methods, including your national ID card held against a phone.

Sources