General information
- Callbacks
- Checkout blocks in WooCommerce
- Checkout language
- Embedded checkouts in WooCommerce
- Guide to troubleshooting in WooCommerce
- How to prepare a support ticket
- Optimizing your checkout when using an Iframe-based checkout
- Pending payment orders and held stock
- Rollback – Undo plugin and WordPress updates
- Troubleshooting the checkout flow
- Vipps, MobilePay and Swish payments
- WP-Cron and pending or cancelled orders
- FAQ
Vipps, MobilePay and Swish payments
Ensure the correct update of the payment status
The customer is supposed to return to the browser after completed purchase in Vipps, MobilePay or Swish. When buying via mobile phone some customers don’t fulfill this step. In this case, the order status in Woo is updated to Processing (or Completed) via a callback from the payment service provider (PSP) to WooCommerce.
It’s important that callbacks from the payment service provider (PSP) to your store doesn’t get blocked by security or caching plugins. Make sure that requests to https://yourdomain.com/wc-api/ isn’t blocked. You can read more about this here.
Missing tracking data
When the customer doesn’t return back to the store after a completed purchase in another app, tracking data reported to Google Analytics, Facebook and other systems will not be done correctly. This is not something we can solve from the plugin, since it is the customer being redirected to the Thank you page that is the actual trigger for sending tracking data to the external system.
Pending payment or cancelled orders for successful payments
This issue primarily occurs on mobile devices. When a customer selects Swish (used in this example), MobilePay or Vipps as their payment method, they’re prompted to open the Swish app to authorize the payment, which they then confirm using their BankID app. After the BankID confirmation, the customer is redirected back to the Swish app. Some customers then close the Swish app, ending the purchase journey before returning to the browser where the checkout and thank you pages are displayed. This results in an incomplete order.
To address this, our WooCommerce plugin has a built-in callback function. When the payment service provider (PSP) sends a callback to the store, this function automatically updates the WooCommerce (WC) order status.
The issue occurs when the merchant’s store blocks callbacks from the Payment Service Provider (PSP). As a result, the plugin’s callback function is never triggered, which causes the WooCommerce order to remain in a Pending payment status. Depending on the setup in WC, around the hold stock feature, it can also set the WC order to cancelled.
Scheduled actions and WP-Cron not working
If you have made sure callbacks are not blocked by your site and still are experiencing for example pending or cancelled orders in WooCommerce for successful payments. The WP-Cron is WordPress’s way of handling scheduled tasks.
When scheduled actions and WP-Cron are not working several critical issues can arise, primarily impacting order management and synchronization between your WooCommerce store and the payment service provider (PSP).
Read more about this in WP-Cron and pending or cancelled orders section.