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 Telia
Operational
Swedish BankID
Operational
Norwegian BankID
Operational
Smart-ID
Operational
Mobile-ID
Operational
Buypass
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
Important Notice: Action Required for Upcoming Changes to BankID Norway by April 1, 2026 Apr 1, 2026 12:00-14:00 CEST
This message serves as an important update to the information previously shared regarding the sunset of the Norwegian BankID Signing Service and the rollout of the new BankID signing solution. We have received an extension to continue using the current BankID Server Signing service until April 1, 2026. This means that the BankID Server will remain fully operational during this period, and all services will continue to function as they do today. This extension provides InGroupe’s customers with sufficient time to implement the necessary changes on their end and ensure a smooth transition to the new signing infrastructure.
BankID has informed us that non-qualified signing certificates will be issued for transitional use until the migration to the new eSign APIs is completed. During this interim period, such certificates will be temporarily issued via the new Stø certificate authority (CA). For you this means that BankID will produce Advanced Electronic Signatures (AES) using non-qualified certificates for such cases. It is important to note that today’s AES is issued with a qualified certificate.
Please review the following changes and actions required to ensure a smooth transition.
1. Modernized User Interfaces
• BankID will discontinue support for iframe-based integrations: Customers currently using iframe must update their integrations.
• SDO format will remain supported: IN Groupe will generate SDO documents, and customers may choose between SDO or PADES formats according to their needs.
2. New Certificate Infrastructure
• BankID certificates will now be issued by Stø, replacing banks as the formal issuers.
• This transition simplifies issuance and opens new opportunities, such as enabling BankID for individuals without a Norwegian bank account.
• All BankID merchants will require new certificates. IN Groupe will manage the replacement process, although some customer involvement may be necessary.
• The Norwegian National Identity Number (NNIN) will be included in the public certificate as a custom extension, using the following Object Identifier (OID): 2.16.578.1.61.2.4
3. Migration to new BankID signing services
• A new BankID must be issued to utilize the new BankID signing service from Stø.
• New client credentials must be created, ref the above issuance of a new BankID. This BankID will have a related client that must be correctly configured by Stø upon request from IN Groupe. If a new certificate is issued, merchants will notice that their signature/seal in SDO documents is associated with a different certificate.
4. Ordering New BankIDs from Stø
• Some customers will need to new BankIDs, IN Groupe will assist customers in this.
• IN Groupe will contact individual customers as needed.
• Further instructions for other customer groups will be shared shortly.
We would like to emphasize that these changes are being implemented in line with the official guidelines and decisions issued by Stø, and as such, they fall outside of IN Groupe’s direct control. Nevertheless, please rest assured that we are fully committed to supporting you throughout this transition and will take every possible step to ensure a smooth and seamless experience.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Link to dev page - https://doc.ingroupe.com/developer/new-bankid-no-signing-service
Posted on Oct 28, 2025 - 14:52 CET
BankID has informed us that non-qualified signing certificates will be issued for transitional use until the migration to the new eSign APIs is completed. During this interim period, such certificates will be temporarily issued via the new Stø certificate authority (CA). For you this means that BankID will produce Advanced Electronic Signatures (AES) using non-qualified certificates for such cases. It is important to note that today’s AES is issued with a qualified certificate.
Please review the following changes and actions required to ensure a smooth transition.
1. Modernized User Interfaces
• BankID will discontinue support for iframe-based integrations: Customers currently using iframe must update their integrations.
• SDO format will remain supported: IN Groupe will generate SDO documents, and customers may choose between SDO or PADES formats according to their needs.
2. New Certificate Infrastructure
• BankID certificates will now be issued by Stø, replacing banks as the formal issuers.
• This transition simplifies issuance and opens new opportunities, such as enabling BankID for individuals without a Norwegian bank account.
• All BankID merchants will require new certificates. IN Groupe will manage the replacement process, although some customer involvement may be necessary.
• The Norwegian National Identity Number (NNIN) will be included in the public certificate as a custom extension, using the following Object Identifier (OID): 2.16.578.1.61.2.4
3. Migration to new BankID signing services
• A new BankID must be issued to utilize the new BankID signing service from Stø.
• New client credentials must be created, ref the above issuance of a new BankID. This BankID will have a related client that must be correctly configured by Stø upon request from IN Groupe. If a new certificate is issued, merchants will notice that their signature/seal in SDO documents is associated with a different certificate.
4. Ordering New BankIDs from Stø
• Some customers will need to new BankIDs, IN Groupe will assist customers in this.
• IN Groupe will contact individual customers as needed.
• Further instructions for other customer groups will be shared shortly.
We would like to emphasize that these changes are being implemented in line with the official guidelines and decisions issued by Stø, and as such, they fall outside of IN Groupe’s direct control. Nevertheless, please rest assured that we are fully committed to supporting you throughout this transition and will take every possible step to ensure a smooth and seamless experience.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Link to dev page - https://doc.ingroupe.com/developer/new-bankid-no-signing-service
Posted on Oct 28, 2025 - 14:52 CET
Sunset of Norwegian BankID Signing Service & introducing new BankID signing solution Apr 1, 2026 12:00-14:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Dec 19, 2025 - 13:42 CET
Dec 19, 2025 - 13:42 CET
Scheduled -
THIS NOTIFICATION APPLIES TO:
Customers of E-Signing
TIMELINE FOR CHANGE:
From: 31.12.2025
DESCRIPTION:
Norwegian BankID BankAxept AS is introducing a new BankID signing service, phasing out the current signing service based on the old ‘BankID Server’ technology. The solution supports signing multiple documents simultaneously and meets the strictest EU requirements for digital signing, qualified signing. IN Groupe is currently implementing this update in collaboration with Norwegian BankID.
CONSEQUENCES:
Customers will need to request a new BankID. All customers will be contacted directly by IN Groupe’s Customer Success team. Importantly, this update will not impact the signing process; customers will continue to experience the same signing flow and receive the same signature output - SDO.
NOTE:
Questions can be directed to support.esecurity@nets.eu
May 16, 2025 - 13:43 CEST
Customers of E-Signing
TIMELINE FOR CHANGE:
From: 31.12.2025
DESCRIPTION:
Norwegian BankID BankAxept AS is introducing a new BankID signing service, phasing out the current signing service based on the old ‘BankID Server’ technology. The solution supports signing multiple documents simultaneously and meets the strictest EU requirements for digital signing, qualified signing. IN Groupe is currently implementing this update in collaboration with Norwegian BankID.
CONSEQUENCES:
Customers will need to request a new BankID. All customers will be contacted directly by IN Groupe’s Customer Success team. Importantly, this update will not impact the signing process; customers will continue to experience the same signing flow and receive the same signature output - SDO.
NOTE:
Questions can be directed to support.esecurity@nets.eu
May 16, 2025 - 13:43 CEST
Sunset of BankID Open B2B service Apr 1, 2026 14:10-16:10 CEST
This notification applies to customers using BankID Open B2B service.
DESCRIPTION:
BankID Open B2B service will be discontinued and replaced by BankID B2B Signing on 1st April 2026.
CONSEQUENCE:
Customers will be required to generate a key pair, submit the corresponding public key in JWK format to IN Groupe Customer Success team, and integrate towards BankID B2B Signing.
Migration Plan for the customers:
• Deadline to submit the JWK securely to IN Groupe’s Customer Success team: 15th February’ 2026
IN Groupe will request a BankID client for BankID B2B Signing service using the provided JWK. Customers will receive confirmation once the JWK has been successfully registered.
• Testing & Verification: as soon as possible
Perform test transactions using BankID B2B Signing to verify successful integration: 1st March’ 2026. Report any issues to IN Groupe’s Customer Success team for resolution.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for BankID Signing B2B: https://developer.bankid.no/bankid-esign-provider/apis/b2b/v0/B2B-Bankid-Signer/
Posted on Dec 22, 2025 - 14:55 CET
DESCRIPTION:
BankID Open B2B service will be discontinued and replaced by BankID B2B Signing on 1st April 2026.
CONSEQUENCE:
Customers will be required to generate a key pair, submit the corresponding public key in JWK format to IN Groupe Customer Success team, and integrate towards BankID B2B Signing.
Migration Plan for the customers:
• Deadline to submit the JWK securely to IN Groupe’s Customer Success team: 15th February’ 2026
IN Groupe will request a BankID client for BankID B2B Signing service using the provided JWK. Customers will receive confirmation once the JWK has been successfully registered.
• Testing & Verification: as soon as possible
Perform test transactions using BankID B2B Signing to verify successful integration: 1st March’ 2026. Report any issues to IN Groupe’s Customer Success team for resolution.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for BankID Signing B2B: https://developer.bankid.no/bankid-esign-provider/apis/b2b/v0/B2B-Bankid-Signer/
Posted on Dec 22, 2025 - 14:55 CET
Additional Claims in BankID NO ID Tokens Jul 22, 2026 12:00-14:00 CEST
Update -
Incident Update: Change Deferral Notification
Status: Deferment of Changes
Overview:
As part of our ongoing system improvements, we had previously announced planned changes to certain attributes (as mentioned above). However, after further review, we have decided to defer these changes. The updates will not be implemented as initially planned.
What’s Changing:
The changes to specific attributes have been deferred and will be rescheduled for a future date.
We will notify you with more information, including pre-production and production deployment dates, in a forthcoming notification.
Next Steps:
Our team is working to finalize the revised timeline for these updates.
Customers will be informed of the new pre-production and production dates once they are confirmed.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to improve our services. Please stay tuned for further updates.
If you have any questions, please don't hesitate to reach out to our support team - support.esecurity@nets.eu
Thank you for your patience and continued support.
Feb 13, 2026 - 13:46 CET
Status: Deferment of Changes
Overview:
As part of our ongoing system improvements, we had previously announced planned changes to certain attributes (as mentioned above). However, after further review, we have decided to defer these changes. The updates will not be implemented as initially planned.
What’s Changing:
The changes to specific attributes have been deferred and will be rescheduled for a future date.
We will notify you with more information, including pre-production and production deployment dates, in a forthcoming notification.
Next Steps:
Our team is working to finalize the revised timeline for these updates.
Customers will be informed of the new pre-production and production dates once they are confirmed.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to improve our services. Please stay tuned for further updates.
If you have any questions, please don't hesitate to reach out to our support team - support.esecurity@nets.eu
Thank you for your patience and continued support.
Feb 13, 2026 - 13:46 CET
Scheduled -
We would like to inform you that we are adding additional claims to the ID tokens generated for BankID NO identifications. This enhancement is designed to provide more comprehensive information and to improve integration with your systems. Please find details on additional claims below:
acr: Appended new values to the existing acr claim using comma separation. Example- urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4
azp: Added as a new claim under the openid scope.
originator: Represented using the existing claim issuing_authority, available under the profile scope.
updated_at: Represented using the existing claim issue_date, available under the profile scope.
Sample ID Token After Update:
{
"sub" : "no_bankid:9578-6000-4-237729",
"birthdate" : "02.12.1921",
"amr" : [ "no_bankid" ],
"iss" : "https://www-ident-test.nets.no/oidc",
"pid" : "9578-6000-4-237729",
"no_bid_pid" : "9578-6000-4-237729",
"given_name" : "Haider",
"nonce" : "nonce22/12/2025",
"no_ssn" : "02122134760",
"ssn" : "02122134760",
"aud" : "MER2",
"acr" : "urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4",
"issue_date" : "1758613431",
"ssn_issuing_country" : "NO",
"azp" : "sis_nets-bankid-current",
"issuing_authority" : "CN=BankID - TestBank1 - Bank CA 3,OU=123456789,O=TestBank1 AS,C=NO;OrginatorId=9980;OriginatorName=BINAS;OriginatorId=9980",
"name" : "Test, Haider",
"exp" : 1766401188,
"iat" : 1766400288,
"family_name" : "Test",
"jti" : "26e28a1b42184ca48e9bbb4d5a944695"
}
These changes ensure consistency while providing additional information for improved integration and compliance.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Jan 20, 2026 - 15:10 CET
acr: Appended new values to the existing acr claim using comma separation. Example- urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4
azp: Added as a new claim under the openid scope.
originator: Represented using the existing claim issuing_authority, available under the profile scope.
updated_at: Represented using the existing claim issue_date, available under the profile scope.
Sample ID Token After Update:
{
"sub" : "no_bankid:9578-6000-4-237729",
"birthdate" : "02.12.1921",
"amr" : [ "no_bankid" ],
"iss" : "https://www-ident-test.nets.no/oidc",
"pid" : "9578-6000-4-237729",
"no_bid_pid" : "9578-6000-4-237729",
"given_name" : "Haider",
"nonce" : "nonce22/12/2025",
"no_ssn" : "02122134760",
"ssn" : "02122134760",
"aud" : "MER2",
"acr" : "urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4",
"issue_date" : "1758613431",
"ssn_issuing_country" : "NO",
"azp" : "sis_nets-bankid-current",
"issuing_authority" : "CN=BankID - TestBank1 - Bank CA 3,OU=123456789,O=TestBank1 AS,C=NO;OrginatorId=9980;OriginatorName=BINAS;OriginatorId=9980",
"name" : "Test, Haider",
"exp" : 1766401188,
"iat" : 1766400288,
"family_name" : "Test",
"jti" : "26e28a1b42184ca48e9bbb4d5a944695"
}
These changes ensure consistency while providing additional information for improved integration and compliance.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Jan 20, 2026 - 15:10 CET