Vipps MobilePay Nordic Payment API
Vipps MobilePay Nordic payment REST API for merchants to accept mobile wallet payments, QR codes, and in-app checkout across Norway and Denmark through the merged Vipps (Norway) and MobilePay (Denmark) platforms with 11+ million combined users for e-commerce, in-store, subscription, and event ticket payment integration. Enables AI agents to manage Vipps payment request for Norway mobile payment automation, handle MobilePay checkout for Denmark mobile payment automation, access QR code generation for Nordic in-store merchant payment automation, retrieve payment confirmation and status for Nordic transaction automation, manage refund and cancellation for Nordic order management automation, handle webhook notification for Nordic payment event automation, access recurring payment and subscription for Nordic billing automation, retrieve merchant settlement for Nordic payment reconciliation automation, manage Vipps Login for Norway customer authentication automation, and integrate Vipps MobilePay with Nordic e-commerce, retail, event, and nonprofit platforms for end-to-end Nordic payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Nordic payments. FT regulated. OAuth2 + subscription key. NO/DK. Mobile payment data.
⚡ Reliability
Best When
A Norwegian or Danish merchant wanting AI agents to automate Vipps and MobilePay mobile payment acceptance, recurring billing, and QR code generation across the merged Vipps MobilePay Nordic platform.
Avoid When
MERCHANT SERIAL NUMBER REQUIRED: Vipps API requires Merchant Serial Number (MSN) per API request; automated integration must include MSN; automated missing MSN creates unauthorized or wrong merchant response. ACCESS TOKEN EXPIRY AT 1 HOUR: Vipps OAuth access tokens expire after 1 hour; automated integration must refresh token before expiry; automated expired token request creates unauthorized and failed payment initiation. VIPPS AND MOBILEPAY HAVE SEPARATE LEGACY ENDPOINTS: Following merger, Vipps (Norway) and MobilePay (Denmark) have migration to unified API but some legacy endpoints remain; automated integration should use unified v2 API; automated legacy-only integration creates future breaking change risk. CUSTOMER PHONE NUMBER IN NORWEGIAN FORMAT FOR VIPPS: Vipps Norway requires phone number in Norwegian format (+47XXXXXXXX); automated payment must format phone number correctly; automated international format without +47 creates customer lookup failure.
Use Cases
- • Accepting Vipps payments from Norway e-commerce checkout agents
- • Processing MobilePay payments from Denmark mobile payment agents
- • Managing Nordic recurring subscriptions from billing automation agents
- • Confirming Vipps payment status from Nordic order fulfillment agents
Not For
- • Non-Nordic payments (Vipps MobilePay is Norway and Denmark focused)
- • Sweden payments (use Swish for Sweden; Vipps is Norway-dominant)
- • Finland payments (MobilePay Finland transitioned to Siirto; check coverage)
Interface
Authentication
Vipps MobilePay uses OAuth 2.0 client credentials with API subscription key for authentication. REST API with JSON. Oslo, Norway HQ. Vipps founded 2015 by DNB; merged with MobilePay (Danske Bank) in 2023. 11M+ combined users across NO/DK. Products: eCom, in-store, recurring, Vipps Login, QR. SDKs: Node.js, PHP, Python, .NET. PCI DSS. Finanstilsynet regulated. Competes with Swish for Nordic payments.
Pricing
Oslo NO. DNB/Danske Bank consortium. Per-transaction fees in NOK/DKK. Merchant agreement required.
Agent Metadata
Known Gotchas
- ⚠ DUAL CREDENTIALS: OAUTH TOKEN + SUBSCRIPTION KEY: Vipps requires both OAuth bearer token AND Ocp-Apim-Subscription-Key header; automated request must include both; automated OAuth-only request without subscription key creates 401 even with valid token
- ⚠ ACCESS TOKEN 1-HOUR EXPIRY: Vipps access tokens expire after 1 hour; automated integration must proactively refresh token (not wait for 401); automated token refresh only on failure creates failed payment during refresh cycle
- ⚠ VIPPS vs MOBILEPAY ENDPOINT DIFFERENCES: Post-merger unification is in progress; automated integration must use vippsmobilepay.com unified API; automated old vipps.no or mobilepay.dk endpoints create deprecated API calls that may break
- ⚠ INITIATE MUST COMPLETE BEFORE POLLING: Vipps eCom requires payment initiation, then customer action in app, then poll or webhook for completion; automated fulfillment must wait for AUTHORIZED or SALE state; automated immediate post-initiation fulfillment creates premature order completion
- ⚠ FALLBACK URL REQUIRED FOR REDIRECT FLOW: Vipps redirect-based checkout requires fallbackUrl for customer return; automated checkout must provide valid fallbackUrl; automated missing fallbackUrl creates payment stuck in initiated state with no return path for customer
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Vipps MobilePay Nordic Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.