- This topic has 10 replies, 2 voices, and was last updated 4 years, 2 months ago by
.
-
Posts
-
Hi there,
Please refer to this video:
[loom.com/share/da0153ed66d74b1a841f932f34725ed5]
this is a live payment site and we have issues when customers chose the FPX option
There are 2 issues:
1. There is an error: “Error occured: URL: Code 0” when user clicks on the Pay button. We find that this error doesn’t prevent the user from completing the payment, Stripe will still process successfully. But there are occassions when the user will see this message after payment is done:
[share.getcloudapp.com/nOukZLA6]2. If the user choose to cancel the payment before it is processed (like in the video), user will STILL GET DIRECTED TO THE PAYMENT SUCCESS page… this is not right.
Could you please check on the 2 above and let us know how we can fix it.
thanks
TerenceHi Terence.
There is an error: “Error occured: URL: Code 0”
I couldn’t reproduce this on my test server. Though it shouldn’t let payment proceed if error occurred indeed, I’ll check what’s wrong here.
2. If the user choose to cancel the payment before it is processed (like in the video), user will STILL GET DIRECTED TO THE PAYMENT SUCCESS page… this is not right.
Yep, it’s not right indeed. However, it looks like you have improperly configured your checkout results page. As you can see on your video, there is an error displayed:
System was not able to complete the payment. Invalid payment amount received. Expected 339.09, got 0.00.In order to fix this, you need to put your success payment content inside
[accept_stripe_payment_checkout]shortcode like this:[accept_stripe_payment_checkout] Success! [/accept_stripe_payment_checkout]Hi Alex,
I don’t understand this part:
In order to fix this, you need to put your success payment content inside [accept_stripe_payment_checkout] shortcode like this:
[accept_stripe_payment_checkout]
Success!
[/accept_stripe_payment_checkout]Can you help to explain?
What I understand is this:
If the payment is successful then it will redirect to the Thank You page set inside each individual product.
If the payment fails then it should redirect to the Checkout Result Page URL under Global Settings.
Are you saying that – everything will redirect to the Thank You page whether the payment status is successful or failed?Teremce
Are you saying that – everything will redirect to the Thank You page whether the payment status is successful or failed?
That’s correct. And you should use shortcodes that are correspondingly displayed either or error or on success like explained here: https://s-plugins.com/customize-the-thank-page-message-of-stripe-payments-plugin/ (
Customize the Message on the Thank You Pagesection and below).Also, can you provide a link to the page with your product so I could have a closer look at your FPX issue? Also please disable Worldfence blocking other countries as I can’t seem to be able to access the website from your video because of it.
You can use this link:[beyondinsights.net/products]
Can you let me know which country you are accessing the site from, so I can whitelist from Wordfence.
thanksCan you disable all countries blocking for now? We have people from different countries in our team, plus country detection isn’t always accurate.
Thank you.
1. I can see you have updated FPX add-on to latest version, this is good. It should fix the issue with “Error occurred: URL: Code 0” on your site. Thank you for reporting it.
2. I can see you’re using some caching plugin. Generally, it’s not a good idea to cache payment popup URLs. If your caching plugin allows you to add exclusions, please add
?asp_action=*to the exclusions list. It should not cache, minify and combine payment popup page\scripts, otherwise your customers may experience issues with payment popup.3. Can you let me know which caching plugin you are using? We will try to add compatibility with it if possible, by telling it to not cache payment popup URLs internally.
4. Last, but not least – every time you make changes to plugin settings or products, or updating plugins, always clear all caches of your caching plugin. Expired cache can cause various issues at random, and not only with our plugin. To check if everything is working properly, access your site via Incognito (Private) browser mode as non-logged-in user.
Regarding #4, I figured it is W3 Total Cache plugin. We have added support for it in the upcoming Stripe Payments version 2.0.36, it should be released sometime next week. Make sure to update it when it prompts. It automatically clears W3TC plugin caches when you make changes to products or plugin settings. You still need to clear its cache when you update any plugin though.
- You must be logged in to reply to this topic.