Betal med Vipps og MobilePay for WooCommerce

Ofte stilte spørsmål

I hvilke land kan jeg bruke Vipps/MobilePay?

Vipps er foreløpig bare tilgjengelig i Norge (93 % bruker det i 2022) og Sverige.
MobilePay er for tiden bare tilgjengelig i Danmark og Finland (92 % og 59 % bruker det 2025, respektivt).

Hvordan kan jeg få hjelp hvis jeg får problemer?

Hvis du har problemer med WooCommerce-installasjonen din, bruk brukerstøtteforumet her på wordpress.org. For andre problemer kan du ta kontakt med Vipps MobilePay.

Hvorfor blir ordre satt til På vent og ikke til Behnadler eller Fullført?

Dette var den gamle standardverdien før versjon 2.0. Den nye standardverdien er nå ‘Behandler’, men dette betyr også at ordre som er «Behandler’ vil ha betalingen reservert, men ikke overført til beutikkinehaveren. Du kan fortsatt velge statusen ‘På vent’ på skjermen for innstillinger.

Om du vekger På vent vil ordre med denne statusen ha betalingen resververt, men ennå ikke overført til butikkinnehaveren. Beløpet må beslates før det kan overføres til butikkinnehaveren. Du har normal bare lov til å gjlre dette på samme tid som odren sendes. Du kan eksplisitt belaste beløpet på ordreskjermen, men pengene vil uansett bli belastet automatisk når ordren blir satt til ‘Behandler’ eller ‘Fullført’.

Om du velger standard eller «Behandler» gjelder det samme for denne statusen. Ordrebeløpet vil bli resevert, men ikke belastet. Du kan belaste manuelt eller det vil automatisk bli belastet når ordren blir satt til «Fullført». Merk at du bør passe på at arbeidsflyten din er slik at ordrebeløpet blir belastet like før pakken sendes.

Det er et unntak for ordre hvor alle elementene er både virtuelle og nedlastbare. Disse anes ikke å trenge behandling og vil belates automatisk (og gå direkte til statusen ‘Fullført’). Det er mulig å tilpasse denne egenskapen til behovene dine ved å bruke filteret ‘woocommerce_order_item_needs_processing’.

Kan jeg refundere ordrebeløp eller deler av dette med Vipps/MobilePay?

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.

Hva er ‘kompatibilitetsmodus’ i innstillingene?

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.

Hvorfor blir frakten min feil vwed bruk av hurtigkassen?

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’.

For sikkerhets skyld bør du teste fraktmetodene i Hurtigkassen før løsningen publiseres.

Jeg vil gjerne bruke sekvensielle ordrenummer på Vipps MobilePay i stedet for ordre-id-er i WooCommerce gjennom utvidelsen for sekvensielle ordrenummer. Støtter denne utvidelsen dette?

Ja, men du må sørge for at ordre-id-ene du produserer er unike for din Vipps MobilePay-konto, og du må for tiden bruke et filter in filen functions.ph i temaet ditt. Vi anbefaler å bruke et prefiks for dine ordre-id-er slik at et filter som vil virke med skeskvensielle ordrenummer vil se ut som

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

Do I need to have a license for WooCommerce Subscriptions in order to use recurring payments?

Ja, det gjør du. få den
her.

Does the recurring payment part of the plugin work with the WooCommerce Memberships-plugin?

WooCommerce abonnementer
og
WooCommerce medlemskap
kan virke sammen for tilgang til gjentakende medlemskap som åpner innhold.

WooCommerce abonnementer er nødvendig for å bruke Vipps/MobilePay gjentakende betalinger, men medlemskap er ikke.

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

When I use recurring payments, why do I have to capture payments for physical products manually?

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.

When I use recurring payments and a renewal happens, why is the order on hold?

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.

Etter 2 dager vil den flyttes til status «Behandler». Du kan imidlerid endre oppførselen dil dette ved å bruke innstillingen «Standard status å gi til ventende fornyelser» i innstillingene for utvidelsen.

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.

Brannmur-porter

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

Tilbyr Vipps MobilePay et testmiljø for Vipps MobilePay for Woocommerce?

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.

Kontakt Vipps MobilePay for tilgang til test-appen. Denne appen må ionstalleres på en enhet som ikke har den vanlige Vipps/MobilePay-appen installert, eller blir den konflikter.

For å bruke testmodus må «Utviklermodus» slås på. Du kan så legge inn testnøkler fra portal-test.vipps.no, og slå testmodus på og av.

Om det er praktisk for din bruk anbefaler vi at du «tester i produksjoin» med et lite beløp, f.eks kr 2. Refudner bare elelr kanseller kjøpet etter behov.

Hvilke krav stilles?

• WooCommerce 3.3.4 eller nyere er påkrevet
• PHP 7.4 eller høyere er nødvendig.
• Et SSL-sertifikat er påkrevet

Filters and Hooks for customization

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_Rate object which will be added to the order.
* Filter: ‘woo_vipps_country_to_code’: Takes a country code and a country name. Should return a two-letter ISO-3166 country code from a given country name
* Filter: ‘woo_vipps_show_capture_button’: Takes a boolean and an order and returns whether or not to show the capture button in the backend
* Filter: ‘woo_vipps_captured_statuses’: Returns a list of the statuses for which Vipps MobilePay should try a capture when transitioning to them.
* Filter: ‘woo_vipps_transaction_text’: Takes a transaction text and an order object, must return a text to be passed to Vipps MobilePay and displayed to the user along the lines of «Please confirm your order»
* Filter: ‘woo_vipps_special_page_template’: Takes a (complete) template path as returned by locate_template and the ID of the Vipps MobilePay special page, should return a new template path (using locate_template or similar).
* Filter: ‘woo_vipps_order_failed_redirect’: Takes an empty string or an url and an order id. If URL is returned, go there on cancelled or failed orders.
* Filter: ‘woo_vipps_product_supports_express_checkout’: Takes a boolean and a product, returns true if the product can be bought with express checkout
* Filter: ‘woo_vipps_cart_supports_express_checkout’: Takes a boolean and a cart, returns true if the cart can be bought with express checkout
* Filter: ‘woo_vipps_express_checkout_supported_product_types’: Returns a list of product types (as strings) that can be bought with express checkout
* Filter: ‘woo_vipps_orderid’: Takes default Vipps MobilePay orderid, the order prefix, and an order object. Must return an unique (at Vipps MobilePay) order ID with 30 chars or less. Default is the prefix + orderid, e.g. ‘Woo364’.
* Action: ‘woo_vipps_shipping_details_callback_order’: Takes an order-id and the corresponding vipps order id. Run at the start of the shipping methods callback.
* Action: ‘woo_vipps_restoring_cart’: Takes an order and a saved cart contents array, ran after the order has failed or is aborted
* Action: ‘woo_vipps_cart_restored’: Runs after the cart has been restored after the order has been aborted of failed
‘ Action: ‘woo_vipps_cart_saved’: When redirecting to Vipps MobilePay, the cart is saved so it can be restored in case the order isn’t completed. This action is ran after this has happened.
* Action: ‘woo_vipps_before_redirect_to_vipps’: Takes an order-id, called at the end of process_payment right before the redirect to Vipps MobilePay
* Action: ‘woo_vipps_before_create_express_checkout_order’: Takes the cart to do express checkout for, run before the order is created
* Filter : ‘woo_vipps_create_express_checkout_cart_contents’: Takes a cart contents array from which an express checkout order will be created . Should return a like array.
* Action: ‘woo_vipps_express_checkout_order_created’: Takes an order ID, run right after an express checkout order has been created, but before it is processed’
* Action: ‘woo_vipps_before_process_payment’: Takes an order-id, called at the start of process_payment
* Action: ‘woo_vipps_wait_for_payment_page’: Run on the page shown on return from Vipps MobilePay
* Action: ‘woo_vipps_express_checkout_page’: Run on the express checkout page, before redirect to Vipps MobilePay
* Action: ‘woo_vipps_set_order_shipping_details’: Takes an order object, shipping details from Vipps MobilePay and user details from Vipps MobilePay. Runs after shipping details have been added to the order on return from express checkout.
* Action: ‘woo_vipps_callback’: Runs when Vipps MobilePay does the callback on a successful payment, takes Vipps MobilePay data as input. Useful for logging/debugging the callback.
* Action: ‘woo_vipps_express_checkout_get_order_status’: Takes the order status returned by Vipps MobilePay – called when the Vipps MobilePay callback hasn’t happened and we need the order status. Useful for logging.
* Action: ‘woo_vipps_vipps_callback’: Is ran when the Vipps MobilePay callback happen, with the decoded and raw POST from Vipps MobilePay. Useful for logging.
* Action: ‘woo_vipps_shipping_details_callback’: Is ran when Vipps MobilePay does the shipping details callback on express checkout. Takes decoded and raw POST from Vipps MobilePay, and the callback args. For debugging.
* Action: ‘woo_vipps_shipping_details_before_cart_creation’: Run after order is updated but before a cart is created to do shipping calculations. Takes an order, The order-id at Vipps MobilePay and the callback arguments from Vipps MobilePay
* Filter: ‘woo_vipps_transaction_text_shop_id’: This is used to identify your shop in the transaction texts sent to Vipps MobilePay (and shown to the user). Default is home_url(), but there is a length limit, so this filter allows you to keep it short.

Kortkoder

• [woo_vipps_express_checkout_button] will print the express checkout button if valid
  • [woo_vipps_express_checkout_banner] will print the express checkout banner normally shown on the checkout page for non-logged-in users
  • [woo_vipps_buy_now sku= id= variant=] prints a «buy now» button given a SKU or an (product or variant) id. Just the SKU is sufficient.