Vipps Authentication
Feature Detail
Description
Vipps Authentication integrates Norway's most widely used mobile payment and identity app as a login option for the Meander mobile app. Similar to BankID, it follows an OAuth/OIDC flow and can return verified identity data including personnummer. Vipps is particularly well-known among younger demographics and is perceived as lower friction than BankID for mobile-first users. The feature covers the redirect flow, token exchange, account linking, and fallback scenarios.
User Flow
Analysis
Vipps was explicitly named alongside BankID in all three workshops as a preferred first-login method. Its widespread adoption in Norway means a significant share of peer mentors will already have it installed, reducing onboarding friction. Like BankID, Vipps login can supply personnummer to improve membership record quality across organisations. The monthly cost (350-750 NOK) is intended to be distributed across participating organisations, making it financially viable. Offering both BankID and Vipps maximises coverage across user demographics.
Vipps Login uses the Vipps MobilePay Login API (OpenID Connect). The Flutter app opens the Vipps app or falls back to a browser-based flow using deep links for the redirect. The backend handles the authorisation code exchange and maps the Vipps sub-claim to a Meander user. Shared implementation patterns with BankID authentication reduce duplication; a common OAuth service layer in the backend handles both providers. The monthly Vipps fee must be tracked per organisation for billing. Sandbox/test environment is available from Vipps for development and QA.
Components (36)
Shared Components
These components are reused across multiple features
Service Layer (9)
Data Layer (12)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.