Pay with Vipps and MobilePay for WooCommerce

Vipps is currently only available in Norway (93 % user adoption in 2022) and Sweden. MobilePay is currently only available in Denmark and Finland (92 % and 59 % user adoption in 2025, respectively).

For issues with your WooCommerce installation, use the support forum here on wordpress.org. For other issues you should contact Vipps MobilePay.

This was the old default of this plugin until version 2.0. The newer default is now ‘processing’, but this also means that orders that are ‘processing’ will have their payment reserved, but not transferred to the merchant. You can still choose the status on-hold in the options screen.

If you choose on-hold, orders with this status will have the payment reserved, but not yet transferred to the merchant. The money must be ‘captured’ before they are actually transferred to the merchant. You are normally only allowed to do this at the same time as the order is shipped. You can ‘capture’ the money explicitly on the order screen; but the money will be captured automatically when the order is set to “Processing” or “Complete”.

If you use the default or choose “processing”, the same applies to this status: The order will be reserved, but not captured. You can do the capture manually, or it will automatically happen when the order is set to “Complete”. Please note that you should ensure that your workflow is then so that the order is captured just before the package is shipped.

There is an exception for orders where all items are both virtual and downloadable: These are not considered to need processing and will be captured automatically (and go directly to the ‘Complete’ status). It is possible to customize this property for your needs using the woocommerce_order_item_needs_processing filter.

Yes, you can do refunds, including partial refunds, using the standard WooCommerce mechanism (https://docs.woocommerce.com/document/woocommerce-refunds/). Additionally, if you cancel an order that was already captured, the money will be refunded for the whole order if the order is not too old. For older orders, you must use the refund mechanism explicitly. This is a safety feature. If automatic refund through the Vipps MobilePay API should fail, you will need to refund manually; in this case an error message to this effect will be displayed and the order annotated.

Some plugins add new features to products or entirely new product types to WooCommerce; which the ‘Express Checkout’ function may not be able to handle. It can be possible to fix this using hooks and filters, but if you choose this feature, express checkout will be done in a different manner which is very much more likely to work for a given plugin. The cost is that the process will be slightly less smooth.

It may be that the shipping method you are using some how does not work when calculated from the Vipps/MobilePay app, where the customer is somewhat anonymous. However, since version 1.4.0 this problem ought to be greatly reduced, so if you still have this problem, report this on the forum and we’ll try to fix it.

If you have shipping methods that add additional information on the ‘normal’ checkout page they will not be able to provide that information to Express Checkout plugin, since that page is bypassed. You may be able to add those options on a different page; but you may want to remove those options when using Express Checkout.

Formerly, there was a filter used to work around this, namely ‘woo_vipps_shipping_methods’. This still works, but if you use it, it will disable the ‘new’ shipping method calculation. You may still customize the Express Checkout shipping; the new filter is called ‘woo_vipps_shipping_rates’.

To be sure, you should test your shipping methods in Express Checkout before going live.

Yes, though you need to ensure that the order-id’s you produce like this are unique for your Vipps MobilePay account, and you currently have to use a filter in your themes’ functions.php file. We recommend using a prefix for your order ids, so a filter that will work with sequential order numbers would look like

add_filter('woo_vipps_orderid', function ($default, $prefix, $order) { return $prefix . $order->get_order_number(); }, 10, 3);

Yes, you do. Get it here .

WooCommerce Subscriptions and WooCommerce Memberships are able to work together for access to recurring memberships that unlock content.

WooCommerce Subscriptions is required in order to use Vipps/MobilePay recurring payments, but Memberships is not.

You can read about how WooCommerce Subscriptions and WooCommerce Memberships work together here .

This is because of the Norwegian law. You are not allowed to charge for a physical product before you ship it, without a valid reason to do so.

You can read about it here .

If you have a valid reason to do so you can use the “Capture payment instantly” option from the “Vipps/MobilePay recurring payments” settings in your product’s settings.

This is because when an order is charged in Vipps MobilePay it takes 2 days before the payment has been fully captured from the customer’s bank account.

After 2 days it will move to the “Processing” status. You can however change the behaviour of this by using the “Default status to give pending renewals” option in the plugin settings.

Alternatively you could look into using WooCommerce “Early renewals”: https://docs.woocommerce.com/document/subscriptions/early-renewal/ if ensuring the status of a charge is fully completed before a specific date is of up-most importance.

Ensure outgoing traffic to port 443 is open. This is used to communicate with Vipps MobilePay servers.

Yes, but you will need a separate account, and you will need to install a special test version of the Vipps/MobilePay app, available trough Testflight. For your test account, the keys will be at https://portal-test.vipps.no; you will configure these in the developer mode settings.

Contact Vipps MobilePay for access to the test app. This app must be installed on a device that does not have the normal Vipps/MobilePay app installed, or there will be conflicts.

To use test mode, switch “Developer mode” on. There you can input the test keys from portal-test.vipps.no and turn test mode on and off.

If this isn’t practical for your usage, we recommend that you “test in production” with a small amount, like 2 NOK. Just refund or cancel the purchase as needed.

WooCommerce 3.3.4 or newer is required PHP 7.4 or higher is required. An SSL Certificate is required.

There are several filters and hooks you can use to customize the behaviour of this plugin: * Filter: ‘woo_vipps_is_available’: Takes a boolean availability argument and the gateway and must return true or false * Filter: ‘woo_vipps_express_checkout_available’: Takes a boolean availability argument and the gateway and must return true or false. * Filter: ‘woo_vipps_cart_express_checkout_button’: Receives a complete button text and the URL needed to proceed to the express checkout page. * Filter: ‘woo_vipps_express_checkout_banner’: Receives a message with an express checkout button and an URL for the same, should return a message for the express checkout banner normally shown on the checkout page * Filter: ‘woo_vipps_buy_now_button’: Takes HTML for the button, and optionally product id, variation id, sku and if the button is to be shown as disabled by default * Filter: ‘woo_vipps_show_express_checkout’ – Takes a boolean, returns whether or not to show the express checkout button * Filter: ‘woo_vipps_show_single_product_buy_now’ – Takes a boolean and a product, returns true if the product should show a ‘buy now with vipps’ button * Filter: ‘woo_vipps_show_single_product_buy_now_in_loop’ – Like above, but especially for products shown in the loop – catalog pages, archives and so forth * Filter: ‘woo_vipps_spinner’: takes one argument which is a ‘wait’ spinner for certain pages * Filter ‘woo_vipps_express_checkout_shipping_rates’ which replaces the ‘woo_vipps_shipping_methods’. It takes a list of shipping methods, and order, and a cart. The format of the shipping methods is an array of ‘rate’ which is a WC_Shipping_Rate object, ‘priority’ which is an integer and the sort-order Vipps MobilePay will use to display the alternatives, and ‘default’, which is a boolean: This will be the default choice * Filter: ‘woo_vipps_default_shipping_method’ taking the default shipping method ID, a list of the shipping methods available (as a table from method id to WC_Shipping_Rate object) and the order. Return a shipping rate id, like ‘local_pickup:5’ * Filter: ‘woo_vipps_vipps_formatted_shipping_methods’. This will take an array of the methods to be sent to Vipps MobilePay, formatted as required by Vipps MobilePay. This is mostly for debugging. * Filter: ‘woo_vipps_shipping_callback_packages’: Takes the ‘packages’ from the cart used to calculate shipping in the shipping details callback * Filter ‘woo_vipps_express_checkout_final_shipping_rate’: Takes an WC_Shipping_Rate object, the order, and the shipping info from Vipps MobilePay. Must return a WC_Shipping