Vipps integration,
built and kept working.
Vipps MobilePay is how Norwegians pay. We connect it to your website, your member system or your Telegram bot. Then we make sure it keeps working when something goes wrong.
- Products
- ePayment, Recurring
- Handled
- Webhooks, refunds
What we connect.
Vipps MobilePay has several products. Most projects need two or three of them.
- Vipps ePayment for one-off payments, such as event tickets and donations.
- Vipps Recurring for subscriptions and memberships, charged on a schedule.
- Webhooks: Vipps tells your system when a payment succeeds or fails. We check the signature on every message.
- Refunds: ticket refunds, and stopping a subscription with a refund.
- Payment inside a Telegram bot: the member picks a plan, accepts the terms and continues in Vipps.
Where payments break, and what we do.
Most payment problems come from rare cases. We plan for these before we write code.
The 20 000 NOK ceiling
Vipps Recurring has a documented ceiling of 20 000 NOK. Larger amounts go on an invoice instead. At NCUA, companies pay by invoice, as the sales terms say.
Duplicate webhooks
Vipps can deliver the same message more than once. We ignore the repeats, so one payment is booked once.
Failed charges and retries
When a charge fails, the member gets a message and Vipps retries for a few days. If our system cannot process a message, it tells Vipps, and Vipps sends it again.
Duplicate subscriptions
The database blocks a second subscription for the same member. We catch double ticket payments and show them to the team.
Refunds
Ticket refunds and stop-and-refund for subscriptions run from the admin panel. The audit log shows who did what.
Test and production keys
We build against the Vipps test service first. Production keys go in when Vipps approves your agreement. A self-test script runs 23 checks on the NCUA payment flow.
How a project runs.
- 01
Agreement and keys
We tell you what Vipps needs from your business. The agreement is between you and Vipps. It is the slow part and we do not control it.
- 02
Design the payment flows
We decide which Vipps product fits each payment: one-off, monthly, or invoice for large amounts. We write down the edge cases before we code.
- 03
Build and test
We build with test keys, test every flow, and check what happens when a webhook arrives twice or a charge fails.
- 04
Go live and keep it working
We switch to production keys, watch the first real payments, and stay available for monitoring and version updates.
In production: Nordic Club UA
Vipps live at NCUA.
Result: the club saves 10 hours of admin a week.
At Nordic Club UA, a Ukrainian business community in Norway, members pay with Vipps Recurring. Guests pay for event tickets with Vipps ePayment. The platform also takes donations. Before launch, we tested Vipps with real money.
We built the platform together with the NCUA team and Vasyl Kravchuk. We keep building it.
Need Stripe, Klarna, BankID or accounting systems next to Vipps? See our Nordic integrations page. For a full member system around the payments, see membership platform. The whole platform is described in the Nordic Club UA case.
Questions we get.
Do I need a Vipps agreement first?
Yes. Vipps MobilePay has to approve your business and give you access to its APIs. We tell you up front what is needed. The agreement is between you and Vipps.
How long does it take?
It depends on the Vipps agreement and approval, which are outside our control. The build is usually the short part and the agreement takes longer. We tell you up front what to expect.
Can customers pay monthly?
Yes. Vipps Recurring charges on a schedule. At NCUA, one membership tier is paid monthly on an annual contract.
What about Apple Pay and Google Pay?
They are not separate projects. They come with a card payment provider such as Stripe, once that is in place.
Who holds the keys?
You do. The keys belong to your own Vipps account. We set them up on the server and keep them out of the web page.
What happens if Vipps changes the API?
APIs change over time. After go-live we can keep the integration working: monitoring, version updates and the fixes that follow. Tell us if you want that.
Need Vipps connected to your system?
Tell us what you sell and how you charge. We will tell you which Vipps products fit.