Upcoming Deprecation of eID and Signature Methods
We are announcing upcoming changes to selected eID and electronic signature methods supported through the eID Easy API.
As part of our ongoing efforts to maintain a reliable, secure, and focused service offering, certain methods will be discontinued and will no longer be available for new API transactions from their respective deactivation dates.
These changes are driven by factors including regulatory requirements, changes in service provider availability, low usage, and the availability of newer or more widely adopted alternatives.
We will make every effort to contact customers who have used the affected methods within the past year directly. However, we encourage all customers to review the list below to ensure that no impacted integrations are overlooked.
Affected Methods and Deactivation Dates
The following table lists the methods scheduled for deprecation, their respective deactivation dates, and recommended alternatives where available.
| Deprecated action type | Alternative(s) | Deactivation date |
|---|---|---|
Fi-ftn-advanced-full-signature | fi-ftn-intesi-adv-signature | 1 Sep 2026 |
Uanataca-qes-signature | adacom-one-shot-qes-signature, es-autofirma-signature, evrotrust-signature, infocert-qes-signature, zealid-signature | 1 Sep 2026 |
verifai-simple-signature | — | 1 Sep 2026 |
yoonik-login | — | 1 Sep 2026 |
| Facebook login | — | 1 Sep 2026 |
se-frejaeid-advanced-signature | freja-simple-signature | 30 Sep 2026 |
se-frejaeid-qes-signature | freja-simple-signature | 30 Sep 2026 |
spid-qes-signature | It-spid-qes-hash-signature for AES; otherwise another supported QES method | 1 Oct 2026 |
dk-mitid-qes-signature | dk-mitid-adv-hash-signature for AES; otherwise another supported QES method | 1 Oct 2026 |
se-bankid-qes-signature | se-bankid-adv-hash-signature for AES; otherwise another supported QES method | 1 Oct 2026 |
yes-com-qes-signature | — | 1 Dec 2026 |
dk-mitid-advanced-signature | mit-id-simple-signature (Simple) or dk-mitid-adv-hash-signature (AES) | 1 Dec 2026 |
se-bankid-advanced-signature | se-bankid-adv-hash-signature (AES) or swedish-bankid-signature (Basic + e-seal) | 1 Dec 2026 |
ee-id-login | ee-web-eid-login | 1 Dec 2026 |
pt-id-login | chave-movel-login | 1 Feb 2027 |
Pt-id-signature | chave-movel-qes-signature | 1 Feb 2027 |
rs-id-login | evrotrust-login, zealid-login | 1 Feb 2027 |
Hr-id-signature | adacom-one-shot-qes-signature, evrotrust-signature, infocert-qes-signature, zealid-signature | 1 Feb 2027 |
fi-id-login | ftn-login | 1 Feb 2027 |
fi-id-signature | fi-ftn-intesi-adv-signature or fi-ftn-advanced-signature | 1 Feb 2027 |
Cz-id-signature | cz-bankid-advanced-signature | 1 Feb 2027 |
ES-lleida-advanced-signature | adacom-one-shot-qes-signature, es-autofirma-signature, evrotrust-signature, infocert-qes-signature, zealid-signature | 1 Feb 2027 |
Important: Where an alternative is marked as "—", no specific replacement method has been designated. Customers should review the Supported Methods documentation or contact our support team to identify a suitable option.
For methods previously offering Qualified Electronic Signatures (QES), please note that Advanced Electronic Signatures (AES) are not equivalent to QES. Customers requiring QES should migrate to another supported QES method.
Required Actions
Please review your current integration to determine whether you use any of the affected methods.
If your integration references a method scheduled for deprecation, we recommend that you:
- Identify affected API flows: Review your integration for any references to the discontinued action types.
- Migrate to supported alternatives: Replace affected methods with the recommended alternatives before their respective deactivation dates.
- Update integration logic and documentation: Review customer-facing signing or identification instructions, method-selection logic, and internal documentation.
- Test your integration: Complete testing before the applicable deactivation date to avoid service disruption.
After a method's deactivation date, API requests referencing that method will no longer be accepted for new signing or identification transactions. Integrations that continue to use discontinued action types may fail or return an error.
For a full list of available methods, please refer to our Supported Methods documentation.
Need Help?
Our team is available to help you assess the impact on your integration and identify suitable alternatives.
Please contact support@eIDeasy.com if you need assistance reviewing your integration or planning your migration.
Thank you for your understanding as we continue to maintain a reliable, secure, and focused service.