If you sell to Norwegian customers, they expect Vipps at checkout — and increasingly expect to log in with it too. Meridianstacks is a team of senior engineers, anchored by hubs in Africa's three tech capitals, that handles Vipps integration for your app: ePayment and checkout, recurring agreements and Vipps Login, implemented against Vipps MobilePay's official APIs — into the web or mobile app you already have, or built into a new product from day one. Your matched hub is Johannesburg (UTC+2) — the same clock as Oslo in summer and never more than an hour out. You get a fixed price in NOK before work starts, you pay against milestones — for delivered, accepted work — and you own all the code.
To integrate Vipps in Norway you need a merchant agreement with Vipps MobilePay (in your company's name — we guide you through it), API keys, a build against their test environment, and correct webhook and capture handling in production. Meridianstacks does the entire technical side: a single Vipps payment or login integration is NOK 70,000–135,000 on our Focused tier, payments + login + recurring agreements is NOK 135,000–270,000 on our Standard tier, and a product built around Vipps is NOK 245,000–475,000 on our Full tier — fixed price in NOK, milestone billing, GDPR/EEA compliant, and you own all the code.
A Vipps integration is not a plugin you switch on. It is a payment system woven into your order flow, and the difference between a solid one and a fragile one shows up on day one of real traffic. This is the work.
Vipps ePayment / Checkout puts the payment method Norwegians reach for first into your checkout — on web and in mobile apps, one-off or recurring.
Vipps Login is OpenID Connect: customers authenticate with the Vipps app and you receive a verified name, phone number and email — no passwords to store, far less sign-up drop-off, far fewer fake accounts.
Most clients start with one and add the other once they see the numbers. We build both against the same user and order models, so adding the second is an extension, not a rebuild.
Clinics, salons, guides and venues taking a deposit at booking. Vipps reserve-then-capture fits perfectly: reserve at booking, capture at confirmation or arrival, release automatically on a valid cancellation.
Recurring agreements the member approves once in the Vipps app, then automatic monthly charges — with retries, pause and cancellation flows handled properly, and the member able to see the agreement in their own app.
Vipps as the primary payment method in a custom storefront, with cards as fallback behind the same checkout — one order flow, one refund path, one reconciliation.
Norwegian-market SaaS or content products billed through Vipps recurring agreements, with plan changes, proration logic and dunning built into your billing engine rather than bolted on.
Vipps Login as the front door of your product — verified Norwegian users in two taps, real names and phone numbers instead of throwaway emails, and no password-reset support queue.
A marketplace, booking platform or member app designed from day one around Vipps payments and login — the Full tier, where the integration is the architecture, not an afterthought.
Vipps Login verifies who is holding the phone. BankID proves who they are. For flows that need legally strong identification in Norway — financial onboarding, signing, age- or identity-critical steps — BankID is the established eID, and it pairs naturally with Vipps Login: Vipps for everyday sign-in, BankID as a step-up when the stakes rise. We integrate BankID through its OpenID Connect ecosystem against the same user model as your Vipps Login, so customers get one coherent identity, not two parallel accounts. If your product needs it, we scope it in the same engagement.
The merchant agreement, its terms and Vipps MobilePay's own fees sit between you and Vipps MobilePay — we don't resell, mark up or sit in the middle of that relationship, and we think you should be wary of anyone who does. Our engagement is the engineering: everything from API keys to a reconciled production integration, quoted as a fixed price in NOK and billed by milestone.
A 30-minute call to map your checkout, user flows and which Vipps products you need. You get a fixed price in NOK, a timeline and your senior engineers. Week 0.
We guide your Vipps MobilePay application (or plug into your existing agreement), request the right API products and set up secure key handling. Runs in parallel with the build. Weeks 1–2.
Payment and login flows implemented end-to-end against the merchant test environment — including failure paths, timeouts and cancellations, not just the happy path. Weeks 1–3.
Idempotent webhook handling, the capture policy that fits your business, refunds, and reporting that matches your settlement. Weeks 2–4.
Production keys, controlled live test payments, monitoring and alerts, then launch. Weeks 4–6 on the Focused tier; longer tiers phase payments live first, then login and recurring.
You own the code and repos. We can stay on a light monthly retainer to add card fallback, subscriptions or BankID step-up as you grow.
Payments and login touch personal data by definition, so the compliance posture is part of the engineering, not a memo afterwards.
Repositories are client-controlled from day one and the contract assigns all source code and IP to you in full. If we part ways, you keep a working, documented integration — not a dependency on us.
| Engagement | What it covers | Typical weeks | Meridianstacks (fixed, NOK) |
|---|---|---|---|
| Focused — single integration | Vipps ePayment at checkout or Vipps Login, into your existing app, with webhooks, capture flows and reconciliation | 3–6 | NOK 70,000–135,000 |
| Standard — full Vipps feature set | Payments + Vipps Login + recurring agreements as one engagement, with card fallback wiring and a unified order flow | 6–10 | NOK 135,000–270,000 |
| Full — product built around Vipps | A new booking, membership or commerce product designed around Vipps payments and login from day one | 9–14 | NOK 245,000–475,000 |
Prices published from our Open Price Book (v1.0 · July 2026 · next review October 2026). All prices exclude VAT.
Indicative ranges; every engagement is quoted as a fixed price in NOK before work begins, and you pay against agreed milestones — for delivered, accepted work. Vipps MobilePay's own merchant fees are set by them and paid directly under your agreement; we don't quote or mark up third-party fees.
Book a free 30-minute scoping call with a senior engineer — on your working day. An honest answer on which Vipps products you need, the timeline and the cost.
Book a free scoping call →