Skip to content
Vipps Checkout to Kustom, plus PHP 8.2

Vipps Checkout ends 30 April. PHP 8.2 ends 31 December. We handle both in one job.

If your WooCommerce store runs Vipps MobilePay Checkout, it has to move to Kustom Checkout (Kustom is the Swedish company that bought Vipps Checkout) before 30 April 2027. If it runs PHP 8.2, security fixes stop on 31 December 2026. We test both changes on a copy of your store, make the switch when Kustom gives the go-ahead, and upgrade PHP in the same pass, at a fixed price.

First: does this apply to your store?

What is being discontinued is Vipps MobilePay Checkout, the full hosted checkout where Vipps runs the whole payment page. If Vipps is one of several payment methods in your normal WooCommerce checkout, Kustom says the 30 April deadline does not apply to you. Not sure which you have? Look at your checkout: if Vipps takes over the entire step, with address, shipping and payment choice, that is Checkout. The PHP date applies to everyone. You can see your PHP version in WordPress under Tools, Site Health, the Info tab and Server, or in your host's control panel. If it says 8.2 or lower, it is time to plan the upgrade. Send us your store's address and we will check both for free.

Two deadlines, one job

Both dates are set by someone else. What you control is when and how the changes happen, and that they happen on a copy first.

Vipps Checkout is discontinued on 30 April 2027

Vipps MobilePay sold its Checkout product to the Swedish company Kustom in March 2026. Kustom says stores that want to keep offering Vipps after 30 April 2027 must have switched to Kustom Checkout by then. Stores move in batches, and Kustom emails an onboarding invitation when it is your store's turn.

Vipps stays, the checkout around it changes

Your customers can still pay with Vipps in Norway and MobilePay in Denmark and Finland. What changes is the checkout around it: it takes on Kustom's look, with cards and Klarna alongside. Kustom says your current pricing does not change.

A new counterparty and two sources of payouts

Kustom AB becomes the contract party for the checkout, and Stripe processes payments after the switch. For a limited period you receive payouts from both Vipps MobilePay AS and Kustom AB, depending on when each payment started. Worth telling your accountant before it happens.

PHP 8.2 gets its last security fix on 31 December 2026

After that date the PHP project fixes no new security holes in 8.2. PHP 8.3 is supported until the end of 2027, 8.4 until the end of 2028 and 8.5 until the end of 2029. Your store works the day after just as it did the day before, but new holes are no longer closed by PHP itself.

October showed why it matters

On 21 October 2026 PHP fixed two critical flaws that could let an attacker run code on the server without logging in, rated 9.2 out of 10. The fix shipped in 8.2.35 and newer. PHP 8.1 and older got no fix from the PHP project, only from hosts that patched it themselves.

One test pass covers both

Each change needs a test on a copy of the store with a full purchase, shipping and the order email. Done separately, you pay for two test passes and two windows of risk. Done together, it is one.

What the move to Kustom actually involves

For a simple store the switch itself is installing a plugin, entering credentials and testing. The work sits in the details around it. These are the points from Kustom's own WooCommerce guide, and what we watch for.

Kustom moves stores in batches and asks you not to start until you have received an onboarding invitation by email. Until then, Vipps Checkout keeps working as usual. What you can do now is take stock: which PHP version the store runs, which plugins touch the checkout, and how shipping is set up.

The plugin is Kustom Checkout for WooCommerce, built and supported by Krokedil. Kustom recommends running the whole switch twice: first on a staging copy with playground (test) credentials, then on the live store with production credentials. The store needs WordPress 5.0, WooCommerce 9.7.0 and PHP 7.4 or newer, and HTTPS. While we test on the copy, the live store keeps taking orders through Vipps as usual.

If you want customers to pick a carrier and pickup point inside the checkout, as many stores do in Vipps Checkout, Kustom uses a feature called the Kustom Shipping Assistant. It is built into the plugin, but your Kustom account first has to be activated for it with a transport management system (TMS), and every shipping zone still needs an ordinary WooCommerce shipping method. This step can take time, so we check it in the free review.

On the live store we disable Vipps Checkout only after a real order has come through Kustom. Switch it off earlier and the store is left without a working payment method. The Vipps plugin stays installed and active, just not as a payment method, because it is what lets you capture, refund or cancel the orders placed through Vipps before the switch.

Orders from before the switch, including their refunds, are handled in the Vipps portal as before. Everything from the switch onwards lives in the Kustom portal. For a while you work in two portals, until the older orders have aged out.

Kustom itself says connected systems such as ERP and accounting tools may need to be re-integrated, and that stores with custom discount rules or shipping logic may need adjustments. With a new counterparty and two sources of payouts for a while, your accountant should know what is coming. Custom integrations and accounting connections are priced after the free check, because their scope varies too much for a fixed starting price.

If you use Vipps Express Checkout or Vipps Recurring, your move follows a separate path: Kustom asks those stores to contact Kustom support rather than follow the standard steps, and for now those payments still flow through Vipps MobilePay. Vipps MobilePay Login is not affected and stays with Vipps MobilePay.

Why do the PHP upgrade in the same pass

PHP is the language WordPress, WooCommerce and your plugins are written in. The switch itself is a setting in your host's control panel. What takes time is finding the code that does not cope with the new version.

PHP 8.1 has had no security fixes since 31 December 2025. PHP 8.2 gets its last on 31 December 2026. PHP 8.3 is supported until 31 December 2027, 8.4 until 31 December 2028 and 8.5 until 31 December 2029. For most stores, 8.3 or 8.4 is a sensible target now.

Some hosts charge to keep expired PHP versions running instead of moving customers over. The Norwegian host Uniweb, for example, charges NOK 80 a month per hosting account on an expired version, and switches the service on automatically. PRO ISP says PHP 8.2 will get security updates through its extended PHP support after 31 December 2026, and still recommends 8.3 or newer. At NOK 80 a month, two years of that fee costs about the same as an upgrade.

The current version of the Vipps plugin for WooCommerce requires PHP 8.0, and Kustom's plugin requires PHP 7.4. A store still on 7.4 cannot even update its Vipps plugin. Since we are in the store anyway to change the checkout, it makes sense to move PHP to a version with years of support left.

WordPress and WooCommerce themselves usually cope with the change. What stops is a theme or plugin nobody has updated in a long time, custom snippets in the theme, and older shipping and payment extensions. So we run the copy on the new PHP version with the error log on, click through a full purchase, and fix what the log shows before we switch the live store. If there are many errors, we tell you and price them before doing anything extra.

If your host has already switched and the store shows a white screen or "There has been a critical error on this website", that is an urgent fix, not a planned upgrade. We handle it under PHP bug fixing, and our guide to the WordPress critical error shows what you can do yourself in the meantime.

How we work

Five steps. You know the price before anything happens, and the live store keeps taking orders throughout.

1

Free check

You send the store's address. We check whether it runs Vipps Checkout or Vipps as a payment method, which PHP version it is on, and which plugins, shipping setup and connections are affected. We respond within 30 minutes during business hours.

2

Fixed price in writing

You get a number, what is included and what is not. Custom integrations and accounting or ERP work are priced separately, so you can leave them out. Nothing starts until you say yes.

3

Copy and test

We create or use a staging copy, move it to the new PHP version, fix what the error log shows, install the Kustom plugin with playground credentials and run the full purchase with shipping and the order email.

4

Switch on the live store

Once Kustom has sent the invitation and the test passes, we repeat it on the live store in an agreed, quiet time window. Vipps Checkout is disabled only after a real order has gone through Kustom.

5

Afterwards

You get a short summary of what changed, where old and new orders live, and what your accountant should know. If you want someone to keep the store updated from here, that is what our WooCommerce care plans are for, from €129 a month.

Fixed prices for the two jobs

Starting prices for a standard WooCommerce store. The free check tells us where yours lands, and you get the number in writing before we begin.

PHP upgrade

For stores and sites that only need to move up from PHP 8.2 or older
From € 199
  • Theme, plugins and custom code checked against the new PHP version
  • Tested on a staging copy with the error log on
  • Errors the test finds fixed, priced upfront if there are many
  • The switch at your host at an agreed time
  • Same starting price as PHP bug fixing

Kustom move

From Vipps Checkout to Kustom Checkout
From € 349
  • Kustom Checkout for WooCommerce installed and configured
  • The whole switch tested on a staging copy first
  • Shipping checked, with the Shipping Assistant where your account is activated
  • A real order through Kustom before Vipps Checkout is switched off
  • A summary of where old and new orders and payouts live

Both together

The Kustom move and the PHP upgrade in one pass
From € 449
  • Everything in both packages
  • One staging copy and one test pass for both changes
  • PHP moved to a version with years of support left
  • The live switch done in the same time window

All prices exclude VAT. Custom integrations, accounting and ERP, Vipps Express and Recurring are priced after the free check.

You only pay for work we can complete and verify

Free check before any quote, fixed-price scope before any work, and nothing switched off on the live store until the new setup is confirmed with a real order. If part of the job depends on Kustom, Vipps MobilePay or your host rather than on your store, we tell you plainly before going further instead of billing you for the search.

Questions about Vipps Checkout, Kustom and PHP 8.2

Yes, if your store uses Vipps MobilePay Checkout and you want to keep offering Vipps after 30 April 2027. Kustom says stores must be on Kustom Checkout by then. If Vipps is a normal payment method in your WooCommerce checkout, the deadline does not apply to you.
Kustom asks stores to wait for an onboarding invitation by email and moves them in batches. You can prepare now: check the PHP version, the shipping setup and which plugins touch the checkout, so the switch itself goes quickly when the invitation arrives.
Kustom says your current pricing does not change. What changes is that Kustom AB becomes your counterparty, Stripe processes the payments, and for a while payouts come from both Vipps MobilePay and Kustom.
The store keeps working, but after 31 December 2026 the PHP project fixes no new security holes in 8.2. Many hosts then charge for extended support, NOK 80 a month at Uniweb for example, or move you to a newer version on their schedule rather than yours.
For most stores, 8.3 or 8.4 is right now: 8.3 is supported until the end of 2027 and 8.4 until the end of 2028. Which one is safe for your store is decided by the test on the copy, because your plugins and theme set the limit.
Then your move follows a separate path. Kustom asks those stores to contact Kustom support, and for now Express and Recurring payments still flow through Vipps MobilePay. We price that part after the free check.
Then it is urgent, and we handle it as a fix under PHP bug fixing, from €199. If the store runs Vipps Checkout, we do the Kustom move afterwards, once it is stable.
Yes. For a first Vipps setup, adding Express, or fixing a Vipps integration that does not work, see Vipps MobilePay for WooCommerce. This page only covers the move away from Vipps Checkout and the PHP deadline.
Free check

Send us your store's address and we will check both deadlines

We check whether the store runs Vipps Checkout, which PHP version it is on and what is affected, then send you a fixed price in writing.

  • A personal reply from a developer, not an auto-responder
  • Free assessment, no obligation
  • Fixed price in writing before work starts
  • We tell you if your store needs none of this

Describe your store

Include the store's address, whether you use Vipps Checkout, Express or Recurring, and whether Kustom has invited you yet.





    Two dates, one job

    Do it on your schedule, not the deadline's.

    Free check and a fixed price in writing. We respond within 30 minutes during business hours.

    Chat on WhatsApp