Zip Co Limited

Hi @davefx

We have just released an update to the plugin to address any issues that may have been present with order post_types.

If you have any questions please reach out to us directly at [email protected]

Thank you.

Hi David,

Thanks for your feedback.

We are currently in the process of updating our Woocommerce plugin to support HPOS.

There should be an update available in the coming weeks.

If you have any further questions feel free to reach out to us on [email protected]

Hi again and thanks for opening another request.

I see you have since reached out to our support team directly.

We can further troubleshoot this in your support ticket as it is a much more efficient method of communicating.

Thank you

• This reply was modified 1 year, 11 months ago by Zip Co Limited.

Hi there,

Thanks for raising this issue with us.

We have been unable to replicate the error you are facing on your staging site and the menu works as expected.

Can you please reach out to [email protected] for further assistance.

Hi @saurabhdemos

Please reach out to [email protected] to request support from our integrations team if this issue persists.

Thanks

Hi Carl

Thanks for getting in touch.

Have you upgraded to the latest version recently? We have made several upgrades and improvements to our Woocommerce plugin, we suggest updating your module with the latest version to benefit from these changes.

Please let us know how it goes.

Regards

Hi @synapseworldwide1

This error message usually cause by incorrect Merchant Private Key to your environment, for example production API key used to sandbox, or sandbox API key used in production, could you double check if API key is the correct one?

Do you have log from the server? please send those information to [email protected] so that we could help identify the cause of issue? Thanks

From the log, it looks like your system place order twice:
02-06-2021 @ 15:49:27 – 25970
02-06-2021 @ 15:49:27 – Checkout session started
02-06-2021 @ 15:49:27 – total:175.00
User place order ID 25970 with order total $175
then
02-06-2021 @ 15:49:28 – 25971
02-06-2021 @ 15:49:28 – Checkout session started
02-06-2021 @ 15:49:28 – total:175.00
Just 1 second later place order ID 25971 with same total $175
But the second order do not have full customer information or order item information, I think the issue is more on the checkout side not related to the plugin as we could not prevent double place order.

Hi @sanziam

From the log I could see the issue is about the CheckoutId reference, as we launching globally all checkout ID from different region or API will be prefixed like ‘au-‘ or ‘us-‘ or ‘nz-‘ but somehow the previous order saved in database with a different checkout ID for example AU will be “co_xxxxxx”

02-06-2021 @ 15:50:11 – CheckoutId: au-co_******************, Result: approved
02-06-2021 @ 15:50:11 – total:175.00
02-06-2021 @ 15:50:11 – shipping:0
02-06-2021 @ 15:50:11 – items:0

from the log we could see that the original order is partially loaded, only total value is correct but the items total value is 0, indicated the order is not being saved completely when the checkout happened.

You could load the order back like this case $order = new WC_Order(25971);
if the order is not completely saved in database then it will missing information.

From the log

02-06-2021 @ 15:50:11 – Charge request sent for order (25971)
02-06-2021 @ 15:50:30 – Charged successfull with id (au-ch_******************)
02-06-2021 @ 15:50:30 – Charge process after controller

You are getting success charge so payment is success with charge ID au-ch_xxxxxx which indicate the pay in Zip end is success too, the issue you had I think is something during save order to database might be broken, not really related to Zip plugin, but might be something changed like reference key prefix “au-” it will be good to check with any other plugin that monitor order place events.

Hope this helps

Hi @galapogos01

If you have upgraded your plugin to the latest 2.3.0 then you should have a new setting in the Zip payment “Widget Region” and “Display Widget Mode”, then select correct region like Australia, in the “Display Widget Mode” you could select inline/iframe when you select inline you could use your CSS to override the Zip Widget to customized to fit your branding.

More technical, you will need to provide the following code if you are building your own plugin or complete custom build. Display iframe mode has advantage for not having your CSS to change the inside style, you could modify the outside wrapper CSS to set the height or widget the iframe will auto adjust that. But you could also choose inline code and use your own CSS to adjust the style.

<script type="text/javascript">
    var zip_widget_merchantId = '<ENTER YOUR ZIP PUBLIC KEY HERE>';
    var zip_widget_env = '<ENVIRONMENT (production or sandbox)>';
    var zip_widget_region = '<ENTER YOUR REGION CODE LIKE au,uk,nz,gb,us>';
    var zip_widget_product_widget = '<css selector insert into that element>';
    var zip_widget_cart_widget = '<css selector insert into that element>';
    var zip_widget_display_inline = '<ENTER true/false>';
</script>
<script defer async type="text/javascript" src="https://static.zipmoney.com.au/lib/js/zm-widget-js/dist/zip-widget.min.js"></script>

More guide please reference to https://zip-online.api-docs.io/v1/conversion-optimisation/widgets it is a bit old but it will be updated soon. Thanks

• This reply was modified 3 years, 9 months ago by Zip Co Limited.

Hi @galapogos01

Thanks for getting in touch.

Can you please provide the url of your website?

I’d be happy to assist with this – there are a few ways we can change the size nd placement.

Thanks

Hi @sanziam ,

Could you please try to upgrade the plugin to version 2.3.1 we just released a hotfix version for this issue, deal to our new implementation to support global products, we introduce the new API key validation function, but it was a mistake that we put the key in URL, instead should be a Post data which will not get affected by URL encoding. Please do try the upgraded version, and let us know if there is any issue.

Thank you for your reporting.

Hi @rocketmen
Thank you for finding the typo, but actually that zip_order_button.js is not used in checkout, the real file used is order_button.php instead.

Thanks

Hi, @smgdarien
We have checked on the custom plugin warranty-and-returns as it is paid plugin that we do not have its source to reproduce the error on our end, do you have the conflicting plugin package that you could send it to [email protected]

We will also like to know your current zip plugin version that you are using. From the conflict you described seems the error is only happening in the customer try to submit “Request Refund” which normally is not official WooCommerce functions, (as only store owner could perform refund in admin backend) We suspect the issue might be related to the warranty-and-returns method don’t know how to handle Zip refund or loading the payment method title with error.

All in all, to better understand the error we need to access to the source code or your dev environment to check the log, please do contact our support team and we will try to find a solution for you. Thanks

Hi Jason,

Our latest update we are loading zip-widget.min.js by using defer. We believe this will not block the PDP rendering.

Thanks