🏠 Overview › 🧩 Components ›🧩 Vipps Gateway

Vipps Gateway

Component Detail

Infrastructure medium complexity backend
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

Outbound integration gateway encapsulating all HTTP calls to the Vipps Login API. Manages credentials, endpoints, retries, and rate limiting for the Vipps environment.

Feature: Vipps Authentication

vipps-gateway

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

  • Manage Vipps API client credentials and environment configuration
  • Execute authenticated requests to Vipps token and userinfo endpoints
  • Apply retry, timeout, and circuit-breaker policies on Vipps calls
  • Log and emit metrics for Vipps API latency and error rates
  • Rotate and cache Vipps JWKS keys for token validation

Interfaces

requestToken(code: string): VippsTokenResponse
fetchUserInfo(accessToken: string): VippsUserInfo
getJwks(): JwksKeySet