User Interface medium complexity mobile
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

Mobile screen presenting the Vipps sign-in option to first-time users. Initiates the Vipps Login flow, handles app-switch return, and surfaces success or error states back to the user.

Feature: Vipps Authentication

vipps-login-screen

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.

  • En viktig bieffekt: Vipps-innlogging kan returnere personnummer tilbake til medlemssystemene
  • Vipps login-kostnad (350-750 kr/mnd) fordeles mellom organisasjonene - avtal modell.
  • Vipps MobilePay AS | Autentisering (innlogging via Vipps). Returnerer verifisert identitet til Meander.

Responsibilities

  • Render Vipps-branded login button alongside BankID option
  • Trigger Vipps app-switch via deep link and handle return callback
  • Display loading, success, and error states during authentication
  • Forward returned identity payload to the Authentication Module
  • Provide fallback messaging when Vipps app is not installed

Interfaces

startVippsLogin(): void
handleVippsCallback(authCode: string): Promise<AuthResult>
showError(error: VippsAuthError): void