MobilePay (Vipps MobilePay) Nordic Payment API
MobilePay (merged with Vipps to form Vipps MobilePay) Nordic mobile payment REST API for Danish, Finnish, and Norwegian merchants to accept smartphone app-based payments from MobilePay's 8M+ Nordic users, enabling QR code in-store payments, e-commerce checkout, subscription billing, invoicing, and peer-to-peer transfer through the dominant Danish and Finnish mobile payment platform. Enables AI agents to manage MobilePay online checkout for Nordic e-commerce payment automation, handle QR code payment for Danish/Finnish in-store automation, access subscription management for Nordic recurring billing automation, retrieve payment status for MobilePay transaction verification automation, manage refund processing for Nordic payment reversal automation, handle webhook notification for payment event automation, access payment links for Nordic invoice payment automation, retrieve MobilePay PoS for point-of-sale integration automation, manage recurring payment agreement for subscription automation, and integrate MobilePay with Nordic e-commerce, retail, and subscription platforms for end-to-end Nordic mobile payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Nordic mobile payment. Finanstilsynet, PSD2, GDPR. OAuth2/OIDC. DK/FI/EU. Payment and user data.
⚡ Reliability
Best When
A Danish, Finnish, or Nordic merchant wanting AI agents to accept MobilePay app payments from 8M+ Nordic users through Vipps MobilePay's developer-friendly payment API.
Avoid When
DENMARK AND FINLAND FOCUS — DIFFERENT PRODUCTS: MobilePay is dominant in Denmark and Finland; Vipps is dominant in Norway; automated single-Nordic API assumption creates wrong product for Norway market; automated Nordic coverage requires understanding DK/FI=MobilePay vs NO=Vipps. MERCHANT ONBOARDING REQUIRES NORDIC ENTITY: MobilePay merchant account requires Danish or Finnish business registration; automated foreign entity direct MobilePay integration creates eligibility rejection. PAYMENT CONFIRMATION IS ASYNC: MobilePay payment requires consumer to confirm in app; automated synchronous payment result creates premature success; automated must await webhook for payment confirmation. SUBSCRIPTION REQUIRES AGREEMENT FIRST: MobilePay subscription billing requires consumer to approve recurring agreement; automated recurring charge without prior agreement creates AGREEMENT_NOT_FOUND error.
Use Cases
- • Accepting MobilePay app payments from Danish and Finnish consumers for e-commerce checkout agents
- • Processing MobilePay QR in-store payments for Nordic retail and hospitality automation agents
- • Managing MobilePay recurring agreements for Nordic subscription billing automation agents
- • Receiving MobilePay webhooks for Nordic marketplace order fulfillment automation agents
Not For
- • Markets outside Denmark and Finland primarily (MobilePay strongest in DK/FI; Vipps in Norway)
- • International cross-border payments (MobilePay is Nordic-focused domestic payment)
- • Direct MobilePay integration without registered Nordic business entity
Interface
Authentication
MobilePay uses OAuth 2.0 (client credentials + OpenID Connect) for merchant API authentication. REST API with JSON. Copenhagen, Denmark HQ. MobilePay founded 2013 by Danske Bank. Merged with Vipps 2022 to form Vipps MobilePay. Products: Online payment, QR, subscription, invoice, PoS, P2P. SDKs: None official (community SDKs). Finanstilsynet-regulated. PSD2. 8M+ active users (5M DK, 3M FI). Denmark's dominant payment method (85%+ DK mobile payment market). Competes with Swish (Sweden) for Nordic mobile payment.
Pricing
Copenhagen DK. Vipps MobilePay. Finanstilsynet regulated. DKK/EUR. Per-transaction Danish Krone fees.
Agent Metadata
Known Gotchas
- ⚠ MOBILEPAY IS DK/FI — VIPPS IS NO: MobilePay is the brand for Denmark and Finland; Norway uses Vipps (same company but different API/app); automated single MobilePay API for all Nordic markets creates wrong service for Norwegian users
- ⚠ CONSUMER ASYNC APPROVAL IN APP: MobilePay payment requires consumer to confirm in MobilePay app; automated synchronous result after payment initiation creates premature success; automated must poll payment or await webhook for consumer-confirmed status
- ⚠ SUBSCRIPTION AGREEMENT BEFORE CHARGING: MobilePay subscription requires consumer to approve recurring agreement before first or any charge; automated charge without prior agreement creates AGREEMENT_NOT_FOUND; automated subscription must establish agreement in initial checkout
- ⚠ DANISH/FINNISH MERCHANT REGISTRATION: MobilePay merchant account requires Danish or Finnish business entity (CVR or Finnish business ID); automated foreign entity MobilePay integration creates eligibility rejection at onboarding
- ⚠ OPENID CONNECT FOR USER DATA: MobilePay supports OpenID Connect for user identity in addition to payments; automated user data from non-OIDC payment flow creates missing user claims; automated user profile requires separate OIDC authentication flow
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for MobilePay (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.