All Systems Operational
E-Ident
Operational
E-Ident
Operational
ID Verifier
Operational
E-Signing
Operational
E-Signing
Operational
Archive
Operational
DocArc
Operational
E-Archive
Operational
Meldingsarkiver
Operational
e-Nett
Operational
IDP’s 3rd Party Dependencies
Operational
MitID
Operational
FTN Aktia
Operational
FTN Danske Bank
Operational
FTN Nordea
Operational
FTN Oma SP
Operational
FTN OP
Operational
FTN Pop Pankki
Operational
FTN S-Pankki
Operational
FTN Säästöpankki Savingsbank
Operational
FTN Mobiilivarmenne
Operational
Swedish BankID
Operational
Norwegian BankID
Operational
Smart-ID
Operational
Mobile-ID
Operational
Buypass
Operational
Ausweis
Operational
Beligan eID
Operational
ID-Rights
Operational
ID-Rights
Operational
Experian
Operational
Virre
Operational
TrustPortal
Operational
e-Consent
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Maintenance of SK services Aug 26, 2026 22:00 - Aug 27, 2026 03:00 CEST
Please be advised that SKID Solutions will be performing emergency maintenance on its IT infrastructure on 26.08.2026 from 22:00 until 27.08.2026 03:00 CET.
On 26 August 2026, brief service disruptions may occur in Estonian and Lithuanian Mobile-ID between 22:00 and 22:59 CET.
From 23:00 on 26 August to 03:00 on 27 August 2026, all SK services may experience intermittent short-term interruptions while maintenance work is being carried out.
Maintenance work will provide greater confidentiality, integrity, and availability to ensure the quality of our services.
SKID will do everything to keep the disruptions as short as possible.
Posted on Aug 25, 2026 - 20:26 CEST
On 26 August 2026, brief service disruptions may occur in Estonian and Lithuanian Mobile-ID between 22:00 and 22:59 CET.
From 23:00 on 26 August to 03:00 on 27 August 2026, all SK services may experience intermittent short-term interruptions while maintenance work is being carried out.
Maintenance work will provide greater confidentiality, integrity, and availability to ensure the quality of our services.
SKID will do everything to keep the disruptions as short as possible.
Posted on Aug 25, 2026 - 20:26 CEST
Added 3DS Flow Support for NO BankID Sep 2, 2026 12:00-14:00 CEST
We would like to inform customers that 3D Secure (3DS) flow support is now available for Norwegian BankID (NO BankID) through both OIDC and CIBA authentication flows.
What's New?
Support for 3DS card payment authentication using NO BankID.
New e3ds scope introduced to initiate 3DS transactions.
3DS requests require the mandatory parameters:
scope=e3ds
binding_message
acr_values
state
Additional UI presentation options are supported, including page, popup, kiosk, and modal modes.
Impact:
Customers can now use NO BankID for Strong Customer Authentication (SCA) in 3DS card payment scenarios.
Authentication responses will include a JSON-formatted binding_message in the ID Token containing the approved payment and authentication details.
Action Required: Customers planning to use 3DS authentication should update their integrations to include the required 3DS parameters and ensure the binding_message is provided in the expected Base64-encoded JSON format.
Please find the release note at: https://doc.ingroupe.com/developer/added-3ds-flow-support-for-no-bankid
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Posted on Jul 31, 2026 - 10:32 CEST
What's New?
Support for 3DS card payment authentication using NO BankID.
New e3ds scope introduced to initiate 3DS transactions.
3DS requests require the mandatory parameters:
scope=e3ds
binding_message
acr_values
state
Additional UI presentation options are supported, including page, popup, kiosk, and modal modes.
Impact:
Customers can now use NO BankID for Strong Customer Authentication (SCA) in 3DS card payment scenarios.
Authentication responses will include a JSON-formatted binding_message in the ID Token containing the approved payment and authentication details.
Action Required: Customers planning to use 3DS authentication should update their integrations to include the required 3DS parameters and ensure the binding_message is provided in the expected Base64-encoded JSON format.
Please find the release note at: https://doc.ingroupe.com/developer/added-3ds-flow-support-for-no-bankid
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Posted on Jul 31, 2026 - 10:32 CEST
MitID Update: CPR Matching Validation Enabled Sep 2, 2026 12:00-14:00 CEST
We would like to inform customers of an update to the MitID integration.
MitID authentication requests that include a presetid/login_hint will now perform a CPR/loginHint validation (CPR Match) during the authentication flow. If the provided CPR/loginHint matches the authenticated user, authentication will proceed normally. If the validation fails, the authentication request will be rejected and a failure response will be returned with the corresponding error details (for example, LOGIN_HINT_MISMATCH).
Impact:
Applies to MitID private authentication flows only.
Does not apply to MitID Erhverv, CIBA requests, or MitID iFrame requests.
Action Required: If your integration uses presetid or login_hint, please ensure that the CPR/loginHint information provided is accurate and aligned with the user's MitID identity to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/mitid-updated-to-perform-cpr-match
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Posted on Jul 31, 2026 - 10:30 CEST
MitID authentication requests that include a presetid/login_hint will now perform a CPR/loginHint validation (CPR Match) during the authentication flow. If the provided CPR/loginHint matches the authenticated user, authentication will proceed normally. If the validation fails, the authentication request will be rejected and a failure response will be returned with the corresponding error details (for example, LOGIN_HINT_MISMATCH).
Impact:
Applies to MitID private authentication flows only.
Does not apply to MitID Erhverv, CIBA requests, or MitID iFrame requests.
Action Required: If your integration uses presetid or login_hint, please ensure that the CPR/loginHint information provided is accurate and aligned with the user's MitID identity to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/mitid-updated-to-perform-cpr-match
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Posted on Jul 31, 2026 - 10:30 CEST
Scheduled Change: Enhanced Validation of OIDC Request Parameters Oct 1, 2026 13:00-15:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Jun 26, 2026 - 10:55 CEST
Jun 26, 2026 - 10:55 CEST
Scheduled -
Status: Upcoming Change
We are going to enforce additional validation checks for OIDC authorization requests. As part of this update, requests that do not fully comply with the OIDC specification or contain inconsistencies between top-level request parameters and the signed request object may be rejected.
Impact
Customers using our authentication services may experience failed login or consent flows if their integrations submit invalid or non-compliant OIDC request parameters.
Action Required
We recommend that all integrators review their OIDC implementation and verify.
Expected Outcome
No impact is expected for integrations that already adhere to the documented OIDC requirements. Customers with non-compliant requests may need to update their implementation to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/more-validations-added-for-oidc-request-parameters
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Jun 25, 2026 - 14:33 CEST
We are going to enforce additional validation checks for OIDC authorization requests. As part of this update, requests that do not fully comply with the OIDC specification or contain inconsistencies between top-level request parameters and the signed request object may be rejected.
Impact
Customers using our authentication services may experience failed login or consent flows if their integrations submit invalid or non-compliant OIDC request parameters.
Action Required
We recommend that all integrators review their OIDC implementation and verify.
Expected Outcome
No impact is expected for integrations that already adhere to the documented OIDC requirements. Customers with non-compliant requests may need to update their implementation to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/more-validations-added-for-oidc-request-parameters
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Jun 25, 2026 - 14:33 CEST
BankID (NO) Pricing Changes - Effective from 1 January 2027 Jan 1, 2027 00:00-01:00 CET
In English:
Stø is introducing a new pricing model for BankID authentication, effective 1 January 2027.
The change applies to both BankID High and BankID with Biometrics, and affects all
resellers and customers. According to Stø, the new model is designed to better reflect
customer usage patterns and feedback.
The new model replaces transaction-based pricing with an annual subscription based on the
number of unique active users. Customers will be able to choose between two subscription
packages: Standard and Plus.
Both packages include unlimited use of BankID authentication* and remove the current
distinction between BankID High and BankID with Biometrics. The Plus package is intended
for businesses that are legally or regulatorily required to collect national identity numbers
from their customers, or that require functionality beyond what is included in the Standard
package.
To align with Stø's new commercial model, we will also introduce a user-based pricing model
for our BankID services from 1 January 2027. Our new price list is provided below.
To continue using BankID authentication from January 2027, you will need to select one of
the available subscription packages. Based on current usage patterns, we will select the
package that best fits each customer on their behalf. This is to ensure continued access.
During Q3 2026, we will send you information about the selected package, together with
further guidance on the transition. To help answer common questions, we have included
Stø's Frequently Asked Questions below. If you require any additional information, please
contact your usual account representative.
* Some exceptions apply. These are described in the Frequently Asked Questions below. If
your organisation is affected by one of these exceptions, we will contact you separately
during the autumn.
You can find out the new Pricing and FAQ here (In English):
https://doc.ingroupe.com/developer/bankid-new-pricing
På Norsk:
Stø innfører en ny prismodell for BankID Autentiseringstjenester med virkning fra 1. januar 2027. Endringen gjelder både BankID Høy og BankID Biometri, og gjelder for alle forhandlere og kunder. Ifølge Stø er den nye modellen utformet basert på tilbakemeldinger fra kunder for å bedre reflektere kundenes bruksmønstre.
Den nye modellen erstatter transaksjonsbasert prising med et årlig abonnement basert på antall unike aktive brukere. Kundene vil kunne velge mellom to abonnementspakker: Standard og Pluss.
Begge pakkene inkluderer ubegrenset bruk av autentiseringstransaksjoner* og fjerner dagens skille mellom BankID Høy og BankID Biometri. Pluss-pakken er beregnet for virksomheter som er juridisk eller regulatorisk pålagt å innhente fødselsnummer fra sine kunder, eller som av andre årsaker har behov for funksjonalitet utover det som er inkludert i Standard-pakken.
For å tilpasse oss Støs nye kommersielle modell vil vi også innføre en brukerbasert prismodell for våre BankID-tjenester fra 1. januar 2027. Vår nye prisliste fremgår nedenfor. En av pakkene må velges for å kunne fortsette å bruke BankID Autentiseringstjenester fra januar 2027. Vi vil, basert på gjeldende bruksmønstre, velge pakken som passer best på vegne av våre kunder. Dette for å sikre at man ikke mister tilgang. I løpet av tredje kvartal 2026 vil vi sende dere informasjon om valgt pakke sammen med ytterligere veiledning om overgangen.
For å besvare vanlige spørsmål har vi inkludert Støs FAQ. Dersom dere har behov for ytterligere informasjon, kan dere kontakte deres vanlige kontaktperson hos oss.
* Enkelte unntak gjelder, disse er beskrevet i FAQ. Dersom deres virksomhet berøres av ett av disse unntakene, vil vi kontakte dere separat i løpet av høsten.
You can find out the new Pricing and FAQ here (In Norwegian ):
https://doc.ingroupe.com/developer/bankid-new-pricing
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Jun 30, 2026 - 16:17 CEST
Stø is introducing a new pricing model for BankID authentication, effective 1 January 2027.
The change applies to both BankID High and BankID with Biometrics, and affects all
resellers and customers. According to Stø, the new model is designed to better reflect
customer usage patterns and feedback.
The new model replaces transaction-based pricing with an annual subscription based on the
number of unique active users. Customers will be able to choose between two subscription
packages: Standard and Plus.
Both packages include unlimited use of BankID authentication* and remove the current
distinction between BankID High and BankID with Biometrics. The Plus package is intended
for businesses that are legally or regulatorily required to collect national identity numbers
from their customers, or that require functionality beyond what is included in the Standard
package.
To align with Stø's new commercial model, we will also introduce a user-based pricing model
for our BankID services from 1 January 2027. Our new price list is provided below.
To continue using BankID authentication from January 2027, you will need to select one of
the available subscription packages. Based on current usage patterns, we will select the
package that best fits each customer on their behalf. This is to ensure continued access.
During Q3 2026, we will send you information about the selected package, together with
further guidance on the transition. To help answer common questions, we have included
Stø's Frequently Asked Questions below. If you require any additional information, please
contact your usual account representative.
* Some exceptions apply. These are described in the Frequently Asked Questions below. If
your organisation is affected by one of these exceptions, we will contact you separately
during the autumn.
You can find out the new Pricing and FAQ here (In English):
https://doc.ingroupe.com/developer/bankid-new-pricing
På Norsk:
Stø innfører en ny prismodell for BankID Autentiseringstjenester med virkning fra 1. januar 2027. Endringen gjelder både BankID Høy og BankID Biometri, og gjelder for alle forhandlere og kunder. Ifølge Stø er den nye modellen utformet basert på tilbakemeldinger fra kunder for å bedre reflektere kundenes bruksmønstre.
Den nye modellen erstatter transaksjonsbasert prising med et årlig abonnement basert på antall unike aktive brukere. Kundene vil kunne velge mellom to abonnementspakker: Standard og Pluss.
Begge pakkene inkluderer ubegrenset bruk av autentiseringstransaksjoner* og fjerner dagens skille mellom BankID Høy og BankID Biometri. Pluss-pakken er beregnet for virksomheter som er juridisk eller regulatorisk pålagt å innhente fødselsnummer fra sine kunder, eller som av andre årsaker har behov for funksjonalitet utover det som er inkludert i Standard-pakken.
For å tilpasse oss Støs nye kommersielle modell vil vi også innføre en brukerbasert prismodell for våre BankID-tjenester fra 1. januar 2027. Vår nye prisliste fremgår nedenfor. En av pakkene må velges for å kunne fortsette å bruke BankID Autentiseringstjenester fra januar 2027. Vi vil, basert på gjeldende bruksmønstre, velge pakken som passer best på vegne av våre kunder. Dette for å sikre at man ikke mister tilgang. I løpet av tredje kvartal 2026 vil vi sende dere informasjon om valgt pakke sammen med ytterligere veiledning om overgangen.
For å besvare vanlige spørsmål har vi inkludert Støs FAQ. Dersom dere har behov for ytterligere informasjon, kan dere kontakte deres vanlige kontaktperson hos oss.
* Enkelte unntak gjelder, disse er beskrevet i FAQ. Dersom deres virksomhet berøres av ett av disse unntakene, vil vi kontakte dere separat i løpet av høsten.
You can find out the new Pricing and FAQ here (In Norwegian ):
https://doc.ingroupe.com/developer/bankid-new-pricing
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Jun 30, 2026 - 16:17 CEST