01
Prepare the records
The issuer completes the agreed structured template with the document and learner information required for registration.
For training providers and organizations
Make every issued document easy to verify
eLearning.ee registers certificates, diplomas and training records from authorized issuers and provides a platform-issued UID, verification link and QR code for every accepted document.
Digitally signed source data
Controlled registration
Platform-issued UID and QR
Registration process
A traceable route from issuer to verification
Records are not published automatically. Each submission follows a controlled process that separates the issuer's responsibility for source data from the platform's responsibility for correct registration.
02
Sign and submit
An authorized representative digitally signs the data package and submits it in an .asice or .bdoc container. Where sensitive data is involved, an encrypted container and an agreed protected channel may be used.
03
Controlled registration
The platform checks the formal integrity of the submission and registers accepted documents in the verification archive.
04
Receive verification data
The issuer receives the registration result with the UID, verification URL and QR code generated by eLearning.ee.
Registration output
Everything needed for document verification
The issuer's own document number remains part of the record, while the public verification identifiers are created independently by the platform.
- A unique platform-issued UID
- A dedicated verification link
- A QR code for the issued document
- A structured registration result for the issuer
Independent control
No direct third-party access to the registry
Issuer submissions do not alter the public archive directly. Registration, correction and revocation are performed through the platform's controlled administrative process.
eLearning.ee confirms the registration and current status of information received from an authorized issuer. The issuer remains responsible for the accuracy and legal basis of the source data.
Early issuer programme
Join now as a Founding Issuer
The early-participant programme offers assisted onboarding and controlled document registration without the cost and complexity of building a separate verification system.
Founding Issuer status is retained. Early participants can continue using the original managed process on preferential terms; moving to future eID, self-service or API solutions will remain optional.
Founding Issuer
Individual annual offer
Pricing depends on document volume, historical imports and the required processing schedule. The initial price-fix period and future preferential terms are defined in the service agreement.
Ask for an offer
Platform roadmap
Designed to grow with participating issuers
The platform is being developed in stages. The current managed process will remain available, while future versions are planned to introduce:
Estonian eID access
Issuer submission portal
API integrations
Automated batch processing
Questions
Frequently asked questions
Which documents can be registered?
The service is intended for certificates, diplomas and other agreed training or qualification records issued by participating organizations.
Who creates the UID and QR code?
eLearning.ee creates the unique UID, verification URL and QR code after the document has been accepted for registration. The issuer's internal document number is stored separately.
Can an issuer change the public registry directly?
No. New records, corrections and revocations are processed through the platform administrator, creating a controlled separation between submission and publication.
How are records submitted?
Data is submitted in an agreed CSV, XLSX or JSON format inside a digitally signed .asice or .bdoc container. Where necessary, the package may be encrypted and transferred through an agreed protected channel.
Can previously issued documents be added?
Yes. Historical documents can be imported as a separately agreed service after the source data and authorization have been reviewed.
What happens if a document must be corrected or revoked?
The issuer submits an authorized correction or revocation request. The platform updates the current status while retaining an administrative trace of the action.
Become a participating issuer
Discuss a pilot for your organization
Tell us what documents you issue, their approximate volume and whether you need a historical import. We will propose a suitable onboarding process.