If you’ve landed on this page, chances are you’re looking to replace your DigiDocService integration—and fast. You're not alone.
The move away from DigiDocService marks a significant shift in Estonia’s digital identity ecosystem. And while the transition can be complex, it doesn’t have to be a painful or costly experience.
Why DigiDocService Is Being Phased Out
For years, DigiDocService was the go-to method for integrating Mobile-ID and ID card authentication and signing into digital services. It was especially helpful for developers working in Java or C, as official libraries only existed for those languages.
However, things have evolved:
- Mobile-ID has moved to the Mobile-ID REST API
- The official DigiDocService is being deprecated
- Developers are now expected to use public libraries or third-party providers for ID card authentication and digital signing
The shift is driven by SK ID Solutions, the original maintainers of DigiDocService, as they focus more on Smart-ID, qualified certificates, and their other core services.
What Are Your Options?
If you're a developer or decision-maker, here are your choices:
❌ Self-Hosted Solutions
You can use open-source libraries (like digidoc4j) or self-host Java services like SiVa (validation) and SiGa (signing). However, this route:
- Requires deep technical expertise
- Locks you into specific tech stacks
- Comes with ongoing maintenance overhead
- Is often overkill unless your use case is highly custom
✅ Use a Third-Party Provider (like eID Easy)
This is the most practical and scalable solution for most teams.
Why Choose eID Easy?
We’ve built a developer-friendly, fully compliant, and low-maintenance solution to help you transition away from DigiDocService smoothly.
All Major Authentication Methods, One Integration
- ID Card authentication
- Mobile-ID
- Smart-ID
All Major Signing Methods, One Flow
- Sign documents with ID Card, Mobile-ID, or Smart-ID
- Simple API: Upload a file → User signs → Get the signed file back
- No need to deal with cryptographic complexity
Multi-country Support Out of the Box
- Support for Estonian, Latvian, and Lithuanian eID methods
- Need another country? Just ask—we’re happy to integrate
Technology-Agnostic
- Use any language or framework
- Our OAuth 2.0–based authentication makes implementation seamless
- Extensive libraries and SDKs available in most modern languages
Zero Maintenance Burden
- We handle certificate updates, security patches, and backend upkeep
- You just integrate once and focus on your core business
Bonus: Understanding ASiC-E (BDOC) Signing Containers
Wondering how ASiC-E containers (also known as BDOC files) work?
- They're essentially ZIP files that contain:
- Files to be signed (datafiles)
- Digital signatures
- Metadata like certificates and timestamps
Steps to Sign an ASiC-E Container:
- Get the signer's public certificate
- Create the signature base object (includes datafiles, timestamp, signer info, etc.)
- Hash the object
- Sign the hash using the signer’s private key (e.g. via ID Card, Mobile-ID, or Smart-ID)
- Attach a timestamp or timemark
- Insert the signature into the ASiC-E container
Due to the complexity of creating the base signature object, we recommend using established libraries like digidoc4j—or letting eID Easy handle it for you.
