Pay Later Messaging

Hello,

Thank you for reaching out to us, we are here to help.

I reviewed your site and the checkout process, and for me the Pay Later button is showing up under the PayPal button when you select our paymnet method. In this case the Pay Later option also often appears when you click on the PayPal button, but this is controlled/decided by the PayPal server and our plugin does not have much control over this. Our plugin can only block certain payment methods from appearing, the rest is controlled by PayPal.

There is however an issue with the checkout via our plugin: when I press the PayPal or Pay Later button, I get an error (Something went wrong.?Please try again or choose another payment source.) and can’t continue to process the payment. This error does not tell me much, but you might get more details via the plugin logs.

In order to get the error logs from our plugin, you will need to enable “logging” on our plugin’s settings. You can enable logging here: WooCommerce > Settings > Payments > PayPal > Connection > “Logging”.

After you have done this, the next time you encounter this error, a log should be added to your logs here:
– WooCommerce > Status > Logs > select “woocommerce-paypal-payments…” in the dropdown and click on view.

We could take a look at these logs as well if you want, but they might contain sensitive details that you should not share on a public forum. If you want, please open a ticket with our service desk. You can find the instruction for this here: https://paypal.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well)

And in regard to Pay Later, please see this document for the general details on this payment option.

Kind regards,
Joost

Hi Joost,
thanks for your email. There is actually no problem in the order process. The real problem (which emerged today after the plugin update) is that the messages like “fill in the data“ “set the purchase conditions flag“ etc. have disappeared. The translation templates have disappeared, there is nothing left. In fact, if you fill in the mandatory fields (highlighted in red including the tax code) and flag the acceptance of the conditions, the payment proceeds. Has anything changed with the update? Do you have any feedback?

Thanks

Hello @marga451

There is not much of these missing flags that we see, we are only seeing the error notification “Aggiungi i tuoi dati. Leggi e accetta i termini e le condizioni per procedere con l’ordine.”
There were no huge changes made that should impact you in the way you describe. You can find the change list here, please take a look. I could be related to this bug, but that should only impact the blocks checkout.

In your situation, our next step would also be to perform conflict testing and see what is causing this issue. A full conflict test is done to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behavior persists.

Here’s a guide that explains the steps in more detail: How to test for conflicts. Best would be to create a staging site and avoid this affecting your live site or cause any damage to it.

Please let us know if you find out what plugin is causing the issue, so we could possibly see if we reproduce it. If you can’t get any results out of this, you might want to open a private engagement, so you can share your logs, system report and findings with us more easily.

Please let us know how this goes.

Kind regards,
Joost

Hi Joost,

Thanks for your suggestions. But until today’s update everything was fine. Today we also updated the woocommerce plugin: could it be a coincidence? Though the STRIPE gateway plugin had no problem even after Woocommerce update. However we have a staging site and will do more tests. If we find that the problem persists, I will contact you directly.
Thanks and kind regards,

Margherita

Hello @marga451

No, I’m sure your idea is correct, that one of these updates is causing the problem. However, a change in our or the WooCommerce plugin can cause a plugin conflict with any other plugin. An existing situation from other plugins, can become visible after changes made in our or the WC plugin.

We still think a conflict test is the best first action to take.

Let us know if you want our support on this.

Kind regards,
Joost

Hello,

Since we did not receive any response or follow-up questions from you, we will assume you got this working to your requirements. If you still have any more questions for us, please open a new thread, because we will mark this one as resolved.

Kind regards,
Joost