Integration
BankID integration
Login, identification and signing with Norwegian BankID in your own apps, set up with OpenID Connect and a .NET backend.
If your users need to log in with BankID, prove who they are or sign something, OpenID Connect does the work. It can go straight to BankID or through a provider that bundles several eIDs, and which fits best depends on volume and what else you need.
Production needs an agreement. Until that's in place, everything is built and tested against a test environment. I set up the flow, connect it to your users and make sure national ID numbers and other personal data are only stored where they're actually needed.
What BankID can be used for
- Login to customer portals and business systems
- Secure identification when registering new customers
- Signing agreements and documents
- Age verification
- Customer due diligence under anti-money laundering rules, where required
Access and setup
There are two ways in: a direct agreement with BankID, or a provider such as Signicat or Criipto that puts BankID and other eIDs behind one interface. Both use OpenID Connect, so the code itself ends up fairly similar. The choice is mostly about price, volume and whether you need eIDs from several countries.
Most of the thinking goes into what happens to a user who already exists, and how the privacy side is handled.
Common questions
- Do we need our own agreement with BankID?
- Either with BankID directly or with a provider that has one. Going through a provider is often quicker to get started.
- Can you store users' national ID numbers?
- It can be done, but only when you have a lawful basis for it. Many solutions get by with a fixed ID from BankID without storing the national ID number at all.
- Does it work with BankID on mobile and the app?
- Yes. The user gets the same options as anywhere else, with the BankID app or a code device.