We work in your timezone - UK / Europe / Canada / Gulf London Dublin Toronto Dubai
Home / Sweden / BankID Integration
Sweden

Add BankID to your app — login, identification and signing, done properly

Swedish users expect BankID — for logging in, proving who they are and signing what matters. Meridianstacks handles BankID integration for your app: we integrate BankID login, identification flows and document or action signing into your existing web or mobile product, or build the app around it. Senior, fluent-English engineers work your business day — your matched hub is Johannesburg (UTC+2), the same clock as Stockholm in summer and never more than an hour out — with a fixed price in SEK, milestone billing and full code ownership. If you want to integrate BankID in Sweden without the local-agency price tag, this is the page.

In short

BankID integration means giving your app the flows Swedish users already trust: login (authentication), identity checks and signing. Doing it properly involves a relying-party agreement and certificate arranged through a bank or authorised partner (held in your name — we guide you through it), building against the official test environment first, and implementing both the animated QR flow and the same-device flow. Meridianstacks delivers this as a fixed-price engagement: a single BankID login or signing integration into an existing app (Focused tier) at 65,000–135,000 kr, full identity and signing flows (Standard tier) at 135,000–265,000 kr, or an app built around BankID (Full tier) at 240,000–465,000 kr — ex moms, billed by milestone, roughly 40–70% below local agency rates.

What's actually involved

What BankID integration really means, technically

It is more than calling an API. These are the six pieces that separate a solid BankID integration from a fragile one — and we do all of them.

Relying-party access & certificate

Access to BankID is provided via banks and authorised partners, and the relying-party agreement and certificate sit in your company's name. We guide the application, prepare the technical details it asks for, and handle certificate and environment setup so the commercial step never becomes a technical blocker.

Test before production

BankID has a dedicated test environment with test identities. We build and QA every flow there first — end to end, on real devices — then switch to production once your agreement and production certificate are in place. No experiments on live users.

The animated QR flow

When users start a flow on one device with BankID on another, they scan an animated QR code that refreshes continuously while the flow is live — the current secure-start pattern users recognise. We implement it correctly, including expiry and retry behaviour.

Same-device autostart

When the user is already on the phone that holds their BankID, the app should open directly and return them to your app afterwards. That means autostart links, app-switching and return handling that behave properly on both iOS and Android — the part most integrations get subtly wrong.

Signing, not just login

Signing binds a verified identity to a specific text or document the user sees and approves in their BankID app. We implement the visible signing text, the evidence your system stores, and where signing fits in your product — contracts, consents, approvals, high-value actions.

Edge cases & fallbacks

Cancelled attempts, timeouts, a BankID on a different device than expected, users starting two flows at once. We handle the awkward paths with clear, plain-language messages — because this is exactly where users abandon a half-done integration.

Common use cases

Where BankID earns its place in your product

Member portals

Associations, unions, housing cooperatives and communities where members log in with BankID instead of yet another password — higher trust, fewer support tickets, and identity you can actually rely on.

Bookings & appointments

Clinics, advisers and service businesses that need to know the person booking is who they say they are — identity-verified bookings, no-show accountability and secure access to personal booking history.

Fintech-lite onboarding

Lending-adjacent, insurance-adjacent and savings products that need strong identity assurance at signup. We build the BankID identification flow; where regulated KYC applies, we scope against your compliance requirements rather than guessing.

Contract & document signing

Agreements, consents and approvals signed in-app with BankID — the user sees what they are signing, approves it themselves, and your system keeps the evidence. Fewer PDFs over email, faster deals.

What we need from you

Five things, and we handle the rest

BankID projects stall on paperwork and unclear ownership, not on code. Bring these five things and the engagement runs clean.

  • A signatory — the relying-party agreement must be in your company's name; we guide the application, you sign it
  • Repo & staging access — your codebase and a staging environment we can deploy to
  • The flows you want — login, identification, signing, or all three, and where they sit in the product
  • Your user model — how a verified BankID identity should map to your existing accounts
  • A copy decision-maker — someone who signs off the visible signing texts and consent wording users will see
Typical timeline

For a Focused integration into an existing app. The provider agreement runs in parallel — it never blocks the build.

  • Week 1 — Scope & provider route — flows agreed, application guided, fixed SEK quote
  • Weeks 2–3 — Build in test — flows implemented against the BankID test environment
  • Weeks 3–5 — Signing, edge cases & QA — real devices, awkward paths, plain-language errors
  • Final week — Production & handover — certificate switch-over, monitoring, docs to you

Focused integrations run 3–6 weeks; full identity + signing flows 6–10 weeks; an app built around BankID 9–14 weeks.

Pricing

What BankID integration costs

EngagementWhat it coversTypical weeksFixed price in SEK
Focused — single integrationBankID login or signing added to your existing web or mobile app3–665,000–135,000 kr
Standard — identity & signingFull BankID identity and signing flows across your product6–10135,000–265,000 kr
Full — app built around BankIDA new web or mobile product with BankID at its core9–14240,000–465,000 kr

Prices published from our Open Price Book (v1.0 · July 2026 · next review October 2026). All prices exclude VAT.

Ex moms, quoted as a fixed price in SEK before work begins, billed by milestone — you pay for delivered, accepted work. Any fees your bank or BankID provider charges for relying-party access are separate and set by them, not by us. Taking payments too? We integrate Swish alongside BankID — one team, one fixed quote.

Security posture

Identity is the one feature you can't half-build

A BankID integration touches the most sensitive thing in your product: who your users are. Our posture is simple — see as little as possible, store even less, and be able to show your lawyer exactly what happens to every byte.

  • We never see users' security codes — nobody but the user's own BankID app does; your system receives only the verified outcome of the flow
  • Data minimisation — we store only the identity attributes each feature genuinely needs, with defined retention for signing evidence
  • GDPR by design — signed Data Processing Agreement, Standard Contractual Clauses for any data transfer, and documentation your DPO can actually use
  • Secrets handled properly — certificates and keys live in a secrets store, never in the repository or a shared drive
  • Audit-friendly logging — logs that help you answer questions later without leaking personal data now
Why teams pick us for this

Senior engineers own the integration end to end — you meet them before you commit. We work your hours from Johannesburg's clock, so a flow reviewed in your morning is fixed by your afternoon, not next week. And everything is handed over: code, certificates configuration, runbooks and documentation, in your repository, under your name.

Milestone billing means the risk stays with us: you approve each delivered stage before paying for it.

Questions & answers

BankID integration — FAQ

How much does BankID integration cost?
Adding a single BankID login or signing flow to an existing web or mobile app (our Focused tier) is 65,000–135,000 kr. Full identity and signing flows across your product (Standard tier) run 135,000–265,000 kr, and a new app built around BankID from the ground up (Full tier) is 240,000–465,000 kr. Every engagement is quoted as a fixed price in SEK, ex moms, and billed by milestone — you pay for delivered, accepted work. Any fees your bank or BankID provider charges for relying-party access are separate and set by them, not by us.
How long does BankID integration take?
Adding BankID login or signing to an existing app typically takes 3–6 weeks. Full identity and signing flows across a product run 6–10 weeks, and a new app built around BankID takes 9–14 weeks. One honest caveat: your relying-party agreement with a bank or authorised provider has its own lead time, which is outside our control — so we build against the BankID test environment in parallel and switch to production once your agreement and certificate are in place.
Do we need our own agreement with a bank or BankID provider?
Yes. Access to BankID as a relying party is provided through banks and authorised partners, and the agreement needs to be in your company's name — it is not something an agency can lend you. What we do is guide you through it: we help you pick the route that fits your case, prepare the technical details the application asks for, handle certificate setup and environment configuration, and keep development moving against the test environment while the paperwork completes.
Can you add BankID login to our existing app?
Yes — that is our most common BankID engagement. We integrate the authentication flow into your existing web or mobile app alongside whatever login you have today, such as email and password or social login, so current users are not disrupted. Your backend receives a verified identity from the completed BankID flow, and we map it cleanly to your existing user accounts, including the first-time account-linking step.
What is the difference between BankID login and BankID signing?
Login (authentication) confirms who the user is so you can start a session or step up security for a sensitive action. Signing binds the user's verified identity to a specific text or document — the user sees what they are approving in their BankID app and confirms it themselves, and your system stores the resulting evidence. Signing is the right tool for contracts, consents and high-value actions; login is for everyday access. We implement both, and they often ship together.
How do the QR code and same-device flows work?
When the user is on a different device from their BankID — say, your website on a laptop — they scan an animated QR code that refreshes continuously during the flow; this is the current secure-start pattern and it is what users expect. When the user is already on the phone that holds their BankID, the app opens directly via an autostart link and returns to your app when done. We implement both, plus sensible handling of the awkward cases: cancelled attempts, timeouts, and app-switching quirks on iOS and Android.
Do you ever see or store users' BankID security codes?
No — and neither does your app. The security code is entered only in the user's own BankID app; your system, and we, never see or touch it. What your backend receives is the outcome of the flow: a verified identity and, for signing, the evidence of what was signed. We design for data minimisation — store only the attributes the feature genuinely needs, define retention periods for signing evidence, and document it all for GDPR, with a signed Data Processing Agreement covering our work.
Where are your engineers based?
Our engineering is anchored by hubs in Africa's three tech capitals — Lagos (UTC+1), Johannesburg (UTC+2) and Nairobi (UTC+3) — with some engineers working from other cities on the same clocks. That span means we staff your project from the hub that matches your day: Lagos runs 0–1 hour from London and Dublin, Johannesburg mirrors Central and Northern Europe, and Nairobi sits one hour from Dubai. English is an official language in all three countries.
Can you integrate Swish payments at the same time?
Yes. Swish integration is a natural companion to BankID work, and we frequently scope the two together so your users can identify themselves and pay in the ways they already trust. If payments are on your roadmap, mention it on the scoping call and we will quote both in one fixed price in SEK.
How do we get started?
Book a free 30-minute scoping call in your hours. We look at your app, agree which flows you need — login, identification, signing or all three — and give you a straight answer on scope, the provider agreement you will need, timeline and a fixed price in SEK. No obligation to commit on the call.

Get a fixed quote in SEK.

Book a free 30-minute scoping call with a senior engineer — in your hours. A straight answer on the flows you need, the provider agreement, timeline and cost for your BankID integration.

Book a free scoping call →
Related

Keep reading