You're moving your WooCommerce store from Vipps Checkout to Kustom Checkout. This guide walks through it start to finish.
Your customers keep Vipps. It's one of the payment options inside Kustom Checkout, so shoppers who prefer paying with Vipps carry on doing exactly that.
What they gain is everything alongside it. Kustom Checkout is a complete checkout rather than a single payment method, so the same flow also offers cards, invoice and pay-later options. Instead of Vipps or nothing, your customers pick what suits them — and the checkout itself is built to keep them moving rather than sending them off to a separate payment page. That's the main reason to make the move: this is an upgrade to your checkout, not a swap of one payment button for another.
Behind the scenes, your store talks to Kustom instead of talking to Vipps directly, and Kustom handles Vipps along with everything else — one agreement, one payout. You'll manage orders in the Kustom Merchant Portal rather than the Vipps portal.
One thing to expect: your checkout will look different, because the payment step is now Kustom's rather than Vipps's. Worth mentioning to anyone who answers customer questions for you.
Most of it is copying two values from one screen into another. If you can install a WordPress plugin, you can do the rest.
One thing may need someone more technical: checking your store meets the requirements. There are minimum versions of WordPress, WooCommerce and PHP. The first two are easy to find yourself. PHP is usually your web host's business, and if you've never heard the term, that's the moment to ask whoever maintains your site. You will also need to check that you're using compatible plugins and themes, Krokedil lists them here.
Your checkout page itself is no obstacle either way — Kustom Checkout works with both the Classic Shortcode block and the newer WooCommerce Checkout block, so you don't need to change how your checkout page is built.
You'll go through the same steps twice: once on a staging site to prove the setup works, then again on your live store.
| Where | Credentials | |
|---|---|---|
| First pass | Your staging or test site | Playground (test) |
| Second pass | Your live store | Production (live) |
That's the whole shape of it. Everything below is written once and applies to both passes — the only differences are which portal you fetch credentials from, and which set of fields you paste them into.
If you have a staging or test environment, always start there. It's the safest way to catch a misconfiguration before it can reach a real customer, and it means your live store carries on taking orders untouched while you work.
If you don't have staging access, put your site into maintenance mode while you run through the steps on your live store. You usually won't need long — but a misconfigured checkout found by a real customer costs more than a few minutes of planned downtime.
Wait for your invitation. Don't begin until Kustom has emailed to say it's your turn — merchants are moved across in batches. If you haven't had an email yet, you will. If you're not sure, ask at support@kustom.co.
Then check these four:
- You've got your onboarding email and your Kustom account login
- Your store meets the technical requirements
- You've been through the WooCommerce setup checklist
- Your shipping methods are set up in WooCommerce under WooCommerce → Settings → Shipping
Unsure about any of it? Email support@kustom.co before you change anything. Much easier than unpicking it afterwards.
What you're doing: collecting the two values that let your store and Kustom recognise each other.
Think of them as a username and password, but for your shop rather than for you. Kustom has two separate environments, and they're genuinely separate accounts — separate logins, separate keys.
| Log in at | |
|---|---|
| Playground, for your staging pass | portal.playground.kustom.co or create an account |
| Production, for your live pass | portal.kustom.co |
Once you're in:
- Go to Developers → API
- Click Generate new
- Copy the Key ID and the Password somewhere safe. Keep the tab open or paste them into a note. You'll need both in the next step. Treat the password like any other password — don't email it around.
The plugin uses different names for these: Key ID is the API Username, and Password is the API Password.
If you can't see the Developers tab, your user account doesn't have permission for it. Ask whoever set up your Kustom account to fetch the keys for you or to give your account admin rights.
What you're doing: adding Kustom Checkout to your store.
Install Kustom Checkout for WooCommerce from WordPress.org or the WooCommerce Marketplace, the same way you'd install any WordPress plugin.
Then go to WooCommerce → Settings → Payments → Kustom Checkout → Manage and tick:
- Enable Kustom Checkout
- Enable Test Mode — on your staging pass. Leave it unticked on the live pass.
- Log debug messages
That last one keeps a record of what the plugin is doing. You'll probably never look at it, but support will ask for it if anything goes wrong, so it saves a round of emails.
Now paste in your keys. There are two pairs of fields, and which pair depends on the pass you're on:
| Pass | Fields |
|---|---|
| Staging, with playground keys | Test Kustom API Username and Test Kustom API Password |
| Live, with production keys | Production Kustom API Username and Production Kustom API Password |
Save changes.
Kustom Checkout shows customers the shipping methods configured in WooCommerce → Settings → Shipping — if nothing is set up there, your checkout will have no shipping options.
Add at least one shipping zone with a shipping method and price for each country you deliver to. If that's all you need, you're done with shipping.
If you want carrier options and pickup points inside the checkout — the way Vipps showed them — that's a separate, free add-on plugin: Kustom Shipping Assistant. It pulls shipping options from your transport management system (nShift, for example) and displays them directly in the Kustom checkout. One thing to know:
You still need at least one ordinary WooCommerce shipping method in every zone where you use it — the assistant sits on top of your WooCommerce shipping, it doesn't replace it. Read more on how to set it up here.
What you're doing: checking Kustom works before real customers meet it.
Place an order as though you were a customer.
On your staging pass no real money moves — you're in test mode, so it's play money. You can use Kustom's sample customer data, and the checkout has a Test Data tab with test payment details.
On your live pass this is a real order with a real payment method. Keep it small, and refund it afterwards.
Either way, four things to look for:
- the Kustom checkout appears when you reach the payment step
- your shipping options appear, at the right price
- you can complete the payment and land on the usual thank-you page
- the order shows up in WooCommerce
If something doesn't work, don't push on. Contact Krokedil support and mention that debug logging is on — the logs live in WooCommerce under Status → Logs.
What you're doing: confirming the order reached Kustom, not just your own store.
Log in to the portal for the environment you're working in and check the order is there for the right amount. The statuses should line up like this:
| WooCommerce | Kustom |
|---|---|
| Processing | Authorized |
| Completed | Captured |
If the order is visible and the amounts match, that pass is done.
If you've been working in staging, everything so far proved the setup — but it proved it on a site your customers don't use. Go back to Step 1 and repeat the whole sequence on your live store, with three differences:
- fetch your keys from portal.kustom.co instead of the playground
- paste them into the Production fields, not the Test ones
- leave Enable Test Mode unticked
Then the test purchase in Step 3 is a real one. That's the point: it's the only way to know your production keys are right.
No staging environment? Then this was your only pass, and it's worth doing inside a maintenance window.
What you're doing: retiring the old checkout, now that the new one is proven.
On your live store, go to WooCommerce → Settings → Payments and disable Vipps Checkout.
Do this last, after Kustom is live and you've seen a real order arrive. If you switch Vipps off any earlier, your shop is left with no working payment method.
Disable it as a payment method, but leave the plugin installed and active.
It's still doing a job. Orders placed before today went through Vipps, and the plugin is what lets you refund or cancel them. Delete it and those older orders might break.
Off, not gone.
That's it. Kustom Checkout is live on your store.
Anything bought before the switch stays with Vipps. You'll find those orders in the Vipps portal and handle refunds and cancellations there, just as you always have.
Everything from the switch onwards lives in the Kustom Portal.
So for a while you'll have two portals to think about — one for old orders, one for new. That's expected, and it resolves itself as the older orders age out.
Plugin — an add-on for WordPress. Kustom Checkout is one; so is Vipps.
Staging — a copy of your store that customers can't reach, used for testing changes before they go live. Not everyone has one.
API keys — the Key ID and Password from Step 1. They let your shop and Kustom recognise each other. Treat them like passwords.
Test mode — a plugin setting that lets you try the checkout with play money. This is separate from WooCommerce's own Site Visibility setting, which is unrelated.
Kustom Portal — Kustom's site where you view orders, refunds and payouts. portal.kustom.co is the real one; portal.playground.kustom.co is for practice.
Playground — the practice version of Kustom. Nothing there is real.
Kustom Shipping Assistant — an optional add-on plugin that shows your carrier's delivery options and pickup points inside the checkout. Needs activating by Kustom before it works.
Something's wrong with the plugin, or the checkout won't load → Krokedil support. Kustom provides technical support through Krokedil, who build and maintain the plugin.
This covers stores that meet the technical requirements. If yours is below the minimum WordPress, WooCommerce or PHP version, updating comes first.
Questions about your account, your move to Kustom, payments or payouts → support@kustom.co.
If you're not sure which, email support@kustom.co and they'll point you the right way.
WooCommerce is open source, so your store is yours to configure — which also makes it your responsibility to keep your platform version, theme and other plugins in a supported state. Occasionally another plugin will conflict with the checkout.
Read more here, or talk to support@kustom.co before going live if you're unsure about your setup.