Authentication / log in

1. What is changing

We are moving from the old BankID Server solution, NBID Server, to the new BankID OIDC solution, NBID OIDC. Because of this, some of the information, data fields, you previously received from BankID will look a little different.

The new solution does not include every field that existed in the old one. For example, certain certificate details or older types of unique identifiers are no longer part of the new BankID standard.

2. Who is affected

You are affected if your service uses Norwegian BankID for authentication, in particular if:

• You use an iframe to run the BankID log in flow, or
• You use 3D Secure, 3DS, with BankID
• You use Norwegian bankid for authentication

3. What this means for you

3.1 Changes to data fields in the response

Some data fields will no longer be available. The new solution does not include every field that existed in the old one. For example, certain certificate details or older types of unique identifiers are no longer part of the new BankID standard.

If your system depends on fields that are not provided in the new solution, you will need to update it to use the newer fields.

3.2 Iframe integrations

If your service uses iframe to run the BankID log in flow:

• This will no longer be supported going forward
• You will need to either switch to a redirect based flow, or
• We can help move you to DTP, which is the only platform where iframes will still be supported

Please contact us if you use iframe so we can help you find the best solution.

3.3 3D Secure, 3DS, authentication

If your service uses 3D Secure, 3DS, with BankID, this change will affect you.

• The 3DS log in flow depends on an embedded BankID log in, iframe
• This is only available on our new DTP platform
• The old NBID Server will no longer be supported

To keep 3DS working, you will need to move to the NBID Embedded flow, iframe, on DTP. Without this change, your 3DS log in flow will stop working.

If you are currently using NBID 3DS, please contact us so we can help you with the transition.

4. Actions required

Use this quick checklist:

• Your system uses data fields from the BankID response
  • Identify which fields you depend on
  • Check whether they are still available in the new solution
  • Update your system to use the newer fields where needed
• You use iframe for BankID log in
  • Decide whether to move to DTP or switch to a redirect based flow
  • Contact us so we can support you with the change
• You use BankID with 3DS
  • Plan to move to the NBID Embedded flow on DTP
  • Contact us so we can help you with this transition

Changes need to be completed within the cross consumption period and before 1 April 2026 to avoid disruption.