





Upcoming changes to Norwegian BankID
What is changing?
Norwegian BankID is upgrading their signing solution and the current option will be discontinued. As part of this change, all authentications for signing must transition to their new solution NO BankID Qualified Electronic Signatures (QES)
This change affects all processes using Norwegian BankID for authentication to sign in our eSign platform (API, Online, GO, Flow, Integrations, Forms). Authentication for viewing and accessing archived documents with Norwegian BankID will remain available and it can be combined with Norwegian BankID QES when signing.
We are working to make this transition as smooth as possible. However, a few changes will be required and it’s important to review your workflows and processes to ensure everything continues to run smoothly. For detailed guidance on the steps you need to take, see the next sections:

What do I need to do?
Once the new QES solution is enabled, please familiarise yourself with it and update any existing drafts or templates that currently use Norwegian BankID for authentication to sign to use the new QES method.
The new QES option will be enabled for accounts on December 1 2025 and old authentication to sign option will be disabled for all accounts on January 12 2026. From that date, it will no longer be possible to start signing new documents with the old method.
If you use NO BankID via an API integration with Scrive, please update the authentication method to NO BankID QES before the deadline to ensure a seamless experience. The new method will be included in the API documentation and available for use from December 1, 2025.
- Pending documents created with the old method can still be signed until January 31 2026. - From February 1 2026, support for authentication to sign with Norwegian BankID will be fully removed. Any remaining pending documents at that time will need to be withdrawn, updated to use QES, and sent again for signing. 
 
- Already signed documents are not affected. 

What’s different about the QES solution?
Here are the key points to know:
- Add attachments before signing starts: All attachments must be added before you start signing. You can’t request or add more attachments after that. 
- All signatories must use compatible authentication: Everyone signing the same document needs to use QES. Supported options, if enabled on your account, currently are Scrive QES, itsme QES, Swisscom QES, Smart-ID QES. 
- Sign each document separately: With Norwegian BankID becoming a QES solution, signing a bundle is no longer supported. Each signature will now be processed separately. 
- Hide personal number option limitations: You can choose to “Hide your personal number on the verification page only”, but it will not be possible to use “Hide personal number from verification page & evidence log” when a party signs with QES - Learn more about this functionality here: Add parties & party settings 
 
- Fields on the document: - Parties set as “viewers” can’t have placed fields placed if others sign with QES. 
- When signing with QES methods or using Flow, the sign date field is not supported 
- Make sure text fields are large enough to fit the content. If the text doesn’t fit, it will still be stored and visible in the evidence log, but may be cut off in the PDF view. - Learn more about this functionality here: Adding fields to document 
 
 

When is this happening?
- New QES option enabled: December 1 2025 
- Current Norwegian BankID authentication to sign option removed: January 12 2026. 
- Transition period for pending documents: Until January 31 2026 - From February 1, 2026 the option to sign documents with Norwegian BankID will be fully removed. Any remaining pending documents must be withdrawn, updated to use QES and sent for signing again. 
 
These dates are preliminary and may still change. We will provide updates if changes occur.

Why is this happening?
- We’re implementing this change to ensure compliance with Norwegian BankID’s updated requirements for electronic signatures. This transition is an industry-wide requirement, not a decision we are making individually. The move to QES ensures: - Compliance with EU and national regulations 
- Stronger legal assurance for signed documents 
- Higher trust and security standards for all users 
 
