Get started
Customization
FAQ
A collection of Frequently Asked Questions:
Why is Qliro not showing up on the checkout page after the plugin has been installed?
- Have you followed the installation, setup and configuration steps?
- Does the site use checkout blocks? This is currently not supported and the merchant needs to switch to use the classic checkout instead.
- Is logging enabled and what do the logs say after you visit the checkout page?
- Do you have the correct API credentials? Is testmode enabled/disabled?
- Is your Qliro account configured for the currency and language you are using?
Does the plugin support multiple currencies, languages and/or different market sites?
The short answer is yes. However, since none of these features are supported by WordPress or WooCommerce out of the box, the merchant needs to implement this functionality themselves first. This can be done by setting up entirely separate WordPress/WooCommerce installations, using WordPress Multisite, or installing a dedicated plugin.
Also, please be aware of that:
- If you are using separate sites or a multisite setup, and since Qliro does not allow the same merchant reference to be used more than once, tthe merchant must ensure that order IDs are unique across the different sites.
Read more under Order already exists below. - While the plugin itself has no limitations regarding currency, there can be limitations in the agreement you have with Qliro. Please contact Qliro to make sure this is correctly configured on the merchant MID.
- The plugin itself has no limitations regarding supported languages, it sends the language set in WordPress. You can read more about how language is handled here: Checkout language settings.
However, please note that Qliro does not support all languages.
Emails, our customers are getting too many or not getting emails at all?
The Qliro plugin does not handle the sending of emails. This is managed by WooCommerce together with their server or hosting environment.
Read more about this in the Troubleshooting order emails blog post.
Shipping options are not working as they should?
Do you experience the same issue when not using Qliro?
Try enabling another default payment method in WooCommerce and check if the issue persists.
If the issue remains, it is likely not related to the Qliro plugin, but rather to your shipping configuration or another part of your setup that requires further troubleshooting.
Why are the delivery options not updated?
In Qliro version 1.11.0 and earlier, there is a known issue that may prevent the delivery option from updating when the customer changes their address during checkout.
A fix is in development. In the meantime, you can apply the following workaround:
- Go to WooCommerce → Settings → Shipping → Shipping Settings → Shipping destination
- Select Default to customer shipping address.
- Save changes.
Why am I getting an “Order already exists” error?
Error Message: “There was a problem updating merchant reference in Qliro’s system. Error message: Order with reference ‘xxxx’ already exists.”
If you have different stores, for different markets for instance, but use the same Qliro MID it can result in the same order number existing in two different stores. This causes a problem since the order number can only exist once in Qliro’s system.
One way to solve this is to use a plugin like Sequential Order Numbers Pro for WooCommerce, or similar, where you can make sure each store has a unique order number.
Why am I getting an “Payment reference is incorrect” error?
Error Message: “PAYMENT_REFERENCE_IS_INCORRECT”
When changes are made to an order in the Qliro Merchant Web the transactionID gets updated. These changes will not be synced to the WooCommerce order. This means that the order in WooCommerce and Qliro order will no longer have the same PaymentTransactionId and will result in the error above if/when the merchant then try and capture the order via WooCommerce.
If this happens you need to disable the order synchronization in the Qliro metabox on the WooCommerce order, and instead handle the orders manually.
Why do I get a Timeout error?
Error Message: “Frontend JS 123456789: Timeout error | Timeout when placing the WooCommerce order”
The parameter MerchantOrderValidationTimeoutInSeconds is a value in Qliro’s system that is set individually for each account. The default setting is 30 seconds, but it can be adjusted to other values.
Qliro for WooCommerce assumes that MerchantOrderValidationTimeoutInSeconds is exactly 30 seconds. If this is not the case, there is a risk of encountering the aforementioned error message.
If you suspect that the timeout is set to something else than 30 seconds you need to contact Qliro to ensure that the number of seconds is correct.
Why do I get a “MerchantTermsUrl” error?
Why do I see the error “The MerchantTermsUrl field is not a valid fully-qualified http, https, or ftp URL” on my checkout page?
This means that you have not set a terms and condition page in WooCommerce.
Go to WooCommerce → Settings → Advanced and then go to the Page Setup section and make sure you have set a Terms and Condition page there.
If you do have set a page there, go and check (under your Pages section in the WordPress dashboard) that your page that contains your terms and condition information has the Status: Published.