[alexanderfoxc]

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 Page section 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.

[alexanderfoxc]

Hi.

I tested it on my iphone and it seems to work on safari but not on chrome or Brave.

Is Apple Pay working on Chrome or Brave on other sites? I think Apple Pay only works on Safari, this is default requirement from Apple. Crhomimum-based browsers will use Payment Request API instead. Credit card info needs to be saved in browser in order for it to work.

Thank you for pointing it out though, we will add this info for APM add-on.

when I click on “Apply” a different currency, i get redirected to a 404 – not found error.

Can you provide a link to the page with your product so I could have a closer look?

[alexanderfoxc]

Hi 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]

[alexanderfoxc]

Please install current testing version of Stripe Payments plugin (2.0.36t3) https://s-plugins.com/testing-version/

This should fix your issue.

[alexanderfoxc]

Very old API versions may not support SCA-related stuff etc. Is there an option to downgrade to 2020-03-02 or 2019-12-03 versions?

[alexanderfoxc]

Does this mean i need to rollback until you support the newer version?

For now – yes. We will add support for the latest API version shortly. It’s currently being tested. Usually not many people are upgrading API version right after it is released, that’s why we assumed we have some time to test the changes first 😉

[alexanderfoxc]

Thank you.

I was unable to reproduce the issue on my test server though.

Can you go to your Stripe Dashboard here https://dashboard.stripe.com/developers and let me know which API versions are displayed on top of the page?

[alexanderfoxc]

Hi.

Are you using latest versions of both Stripe Payments and Subscriptions add-on? Check for updates via WP Dashboard just to make sure you are.

Can you also provide a link to the page on your site where your subscription product is that shows this error?

[alexanderfoxc]

Thank you for your website URL.

Looks like you’re using SG Optimizer plugin which seems to be conflicting with our plugin. There were several similar reports lately and we’re still investigating this.

To clear its cache, you need to press the Purge SG Cache button in your top admin bar.

[alexanderfoxc]

No worries at all, glad you have this fixed now 🙂

[alexanderfoxc]

Hi.

As a quick solution (and not much of a proper though), you can disable Security Token check on plugin settings page: Stripe Payments -> Settings, Advanced Settings tab, look for “Disable Security Token Check” option at the bottom of the page. Enable it, then save settings. Make sure to clear your caching plugin cache if you use any.

Now it would be good to figure out WHY it’s happening. Can you provide URL to your website? If you don’t want to do this publicly, please get in touch with us via contact form.

[alexanderfoxc]

Hi Elle.

Perhaps you haven’t enabled coupons usage for your product. Please have a look at this documentation, go to Handling Coupons for Different Products section. It shows how to specifically enable coupons for your product.

Also, please make sure the subscriptions addon and the main Stripe payments plugin are up to date.

[alexanderfoxc]

I’m not sure why the webhooks weren’t working. Perhaps you changed API keys after webhooks were created? Or changed signing secrets in the settings. It would show error in the log though if you did. We never had such situation in the past. Few other issues related to webhooks that our customers had were caused either by their server config that was blocking webhooks from Stripe or by improper manually configured webhooks (when those were created via Stripe Dashboard by the customer instead of using “Create Webhook” buttons on add-on settings page).

Create a plan in test mode in the plugin, but make it “daily for 3 days” instead of monthly. Then create a product with this test plan and make a test purchase using one of these test cards: https://stripe.com/docs/testing#cards. It should automatically “end” itself in 3 days, you can see that by watching the subscription on Subscriptions page of the plugin.

If test mode webhooks are working, then, most likely, Live webhooks would be working as well. When you have a first live purchase, just find the subscription on Subscriptions page of the plugin and see if events are properly populated (e.g. “regular payment made” should be right after “subscription created” event). Just look how it goes with your daily test plan, same events should be there for your live plan (except that it would happen monthly, not daily).

[alexanderfoxc]

Try to re-create webhooks.
`
Go to Stripe Payments -> Settings, Subscriptions tab. Click Delete Webhooks button, also click Clear Cache button. Then create webhooks for both live and test modes. Then send another test webhook from Stripe Dashboard. Make sure to select customer.subscription.updated webhook type. Then check logs.

If nothing in logs, we need to log in and check your site. Would be nice if you have a staging website.

[alexanderfoxc]

Your server might be blocking requests that look suspicious.

Check your server logs and see if POST from Stripe is not getting blocked by the server config. Here’s how the log entry looks in my Nginx server access log:

POST /?asp_hook=test HTTP/1.1″ 200 0 “-” “Stripe/1.0 (+https://stripe.com/docs/webhooks)

Also, do you have any WP security or firewall type plugins installed on your site? If yes, can you disable those and try to test the webhook again?

[Author]

Posts