Pay Later messaging missing from Cart page with V2.2.1

Hello @simplecv

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

I was not able to check this myself, but I reviewed the release notes and there were 2 enhancement items that could affect the Pay Later messaging:

• Enhancement – Pay Later button and message get hidden when product/cart/checkout value is outside of range?#1511
• Enhancement – Update Pay Later amount on the cart page and checkout when total changes?#1441

So first, I would advise you to check the Pay Later documentation from PayPal for your country and find out if your products are within the range for using Pay Later. You might be checking this for products that are outside the Pay Later range.

If that is not the case, we would like to hear back from you to take another look. If you don’t want to share any details of your site via this public forum, you can also open a private engagement with us.

Pending your response.

Kind regards,
Joost

Hello and sorry if I join the conversation but I encountered the exact same problem and I also performed the rollback where everything is ok.

If the pay later message disappears from the cart page because it doesn’t fit the parameters added with version 2.2.1, why does it appear on the payment page?

Hi Joost,

I have sent staging login credentials via the private engagement link that you posted above so you can easily replicate the issue.

• This reply was modified 1 year, 3 months ago by simplecv.

Hello @simplecv

Thank you for providing additional details on this case. We will be looking into this and coming back to you when we figure out what could be causing this. It might need to get a fix for next release, so currently the best option is to revert to the version 2.1.0.

Kind regards,
Joost

Hello,

We have a fix ready for resolving this issue, this will be included in the next release (2.3.0) if no issue come up during testing.
We have a package available if you want to test this, but I believe since you waited as long as you have, you probably reverted to 2.2.0 in the meantime.

There is also the possibility to test the latest beta version that is available here, to see if that resolved the problem for you.

I would advise you to update to 2.3.0 when it becomes available in around 2 weeks. I will close this thread as there is not much more we can do for this at the moment. If the next release does not resolve the issue for you, please open a new thread, so we can take another look.

Kind regards,
Joost

Thank you Joost!

Yes, we have reverted to 2.1.0 to fix the issue. I will now wait to update to 2.3.0.