What Is a BankID Integration?

A BankID integration is the connection that lets your service use Swedish e-ID – to identify who a user is and to collect legally binding signatures. Instead of its own passwords and paper signatures, the service relies on BankID, which a majority of Swedes already have on their phones. Here’s what the integration actually does and what’s required to get started.

Identification and signing – two different things

The first thing to understand is that BankID is used in two fundamentally different ways, and an integration often handles both.

• Identification answers the question who is this? The user proves their identity, typically to log in or start a service. The result is a confirmation that the person with a specific personal ID number has identified themselves here and now.
• Signing answers the question do you approve this? Here the person is linked not just to their identity but to specific content – the text of a contract, the amount of a payment. The signature is legally binding and is stored as evidence of what was approved.

The difference matters when defining requirements. “Logging in with BankID” isn’t enough if you need to be able to show afterward that a customer actually approved a specific contract – then it’s a signature you need, not just identification.

What’s required to get started

A BankID integration isn’t purely a technical build. Three parts need to fall into place.

1. Agreement through a bank or reseller. You can’t connect to BankID entirely on your own. Either you sign an agreement directly with a bank, or you go through a reseller that offers BankID as a service. The reseller route is most common for smaller and mid-sized companies since it’s faster and has lower requirements to get started.
2. Technical integration with the BankID service. Your service connects to BankID’s interface to start identifications and signings, show QR codes, and receive the responses. That includes handling the cases that don’t go as planned – interrupted signings, timeouts, users who change their minds.
3. Test environment before going live. Before anything goes live, a test environment with test BankID is used, which behaves like live BankID but without real identities. There the whole flow is trialed so it holds up before real users encounter it.

Typical use cases

The BankID integration shows up everywhere a Swedish service needs to know who the user is or needs a binding approval. Three patterns are especially common:

• Onboarding. A new customer identifies with BankID at registration. The service immediately knows who the person is, without forms to fill in and check manually.
• Payment approval. The user signs to approve a payment or a purchase, which provides both reassurance and a traceable record of the approval.
• Contract signing. Employment contracts, insurance policies, subscriptions – documents that once required pen and mail are signed directly in the service with a few clicks.

A concrete scenario

A company launches a digital service where customers sign up for a subscription online. At registration the customer identifies with BankID, so the company knows with certainty who they are without a manual ID check. When the terms need to be approved, a signature is done with BankID – and the company gets evidence that holds up if the agreement is ever questioned.

To build it, they signed an agreement through a reseller, had a development partner connect the service to BankID, and tested the whole flow in the test environment first. From decision to going live, the integration took a handful of weeks, with most of the time spent making interruptions and error cases feel smooth for the user.

Part of a bigger flow

A BankID integration rarely stands alone. It’s tied together with the rest of the service – customer records, payments, contract archives – and becomes one piece in a broader integration effort. At Weapp we’ve built BankID into digital services like Sejfa, where secure identification is the very core of an insurance service for young adults.

Thinking about adding BankID to your app or service? Get in touch and we’ll go through which agreement route and which flow – identification, signing, or both – fits you.