Vipps Integration Service
Component Detail
Service Layer
medium complexity
backend
0
Dependencies
0
Dependents
2
Entities
0
Integrations
Description
Backend service that orchestrates the Vipps Login OAuth/OIDC flow on behalf of the mobile app. Exchanges authorization codes for verified identity claims and maps them into Meander-native auth tokens.
vipps-integration-service
Sources & reasoning
Vipps is paired with BankID throughout §1.3, §5 Phase 2 and the priority matrix (Fase 2). Vipps MobilePay is already an active subprocessor for authentication. Phase 2's source name is 'Core Product' (§5 Fase 2 - Kjerneprodukt), so target_release uses that verbatim.
-
docs/source/likeperson.md · line 27En viktig bieffekt: Vipps-innlogging kan returnere personnummer tilbake til medlemssystemene
-
docs/source/likeperson.md · line 287Vipps login-kostnad (350-750 kr/mnd) fordeles mellom organisasjonene - avtal modell.
-
docs/source/Subprocessors.md · line 9Vipps MobilePay AS | Autentisering (innlogging via Vipps). Returnerer verifisert identitet til Meander.
Responsibilities
- Exchange Vipps authorization code for ID and access tokens
- Validate ID token signature, issuer, and audience claims
- Extract verified identity (name, fødselsnummer, phone, Vipps-ID) from claims
- Issue Meander-native auth tokens for downstream session use
- Propagate fødselsnummer back into membership systems when missing
Interfaces
exchangeAuthCode(code: string, state: string): VippsIdentity
issueMeanderToken(identity: VippsIdentity): AuthToken
syncFodselsnummerToMembership(vippsId: string, fnr: string): void
Related Data Entities (2)
Data entities managed by this component