Safe API version to upgrade to

  • Resolved monkeywrench2

    (@monkeywrench2)


    4 months ago

    Hi,

    I’m on the latest version of this plugin v. 3.3.92. In the workbench on the stripe dashboard I see that they have an upgrade available (latest: 2025-08-27.basil). I’m on 2022-08-01.

    I haven’t made any customizations to the plugin. So, is it save to upgrade to the latest version, or is there a version, other than the latest, that is a safer bet?

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Clayton R

    (@mrclayton)

    3 months, 4 weeks ago

    Hi @monkeywrench2

    Thank you for contacting Payment Plugins. You can safely upgrade to 2025-08-27 if you like but it will also not hurt to remain on your current version 2022-08-01.

    If you do upgrade, I always recommend performing a few test mode transactions for peace of mind.

    Kind Regards

    Thread Starter monkeywrench2

    (@monkeywrench2)

    3 months, 3 weeks ago

    Thanks for your reply. Based on your response, that it’s safe to upgrade to the current version, I tried to do this by upgrading to the new API on the stripe dashboard and then recreating new webhooks with the plugin from the API Settings tab.

    This however created webhooks for the same API version 2022-08-01 as before. Upon looking into it, I found that this version is explicitly set in “class-wc-stripe-api-settings.php” (and some other php files of the plugin).

    Am I supposed to change the explicitly set version in these php files of the plugin? This doesn’t seem quite right to me. Is there a document where you explain how to perform a proper upgrade of the API for your plugin?

    Thanks

    Plugin Author Clayton R

    (@mrclayton)

    3 months, 3 weeks ago

    Hi @monkeywrench2

    If you use the Stripe plugin to create your webhooks then it will use the API version that’s coded in the plugin. If you want to upgrade your webhooks to the latest version then I recommend manually creating them.

    Is there a particular reason you’re wanting to upgrade the webhook version that is being used?

    Kind Regards

    Thread Starter monkeywrench2

    (@monkeywrench2)

    3 months, 3 weeks ago

    Hi @mrclayton

    No particular reason. I just noticed that we were 3 years behind on updates and thought maybe there are some security or other improvements that could be worthwhile.

    As to your advice to create them manually. I did that on stripe dashboard. But I don’t see a way to bring them into your plugin. It has the “Create Webhook” button but no way of supplying the webhook_id to the plugin.

    So, unless you have some insights for me on how to accomplish this, I’ll stick with the current version.

    Thanks

    Plugin Author Clayton R

    (@mrclayton)

    3 months, 3 weeks ago

    Hi @monkeywrench2

    If you scroll down on the API Settings page you will see the option to insert the webhook secret. That is what the plugin uses to process the webhook notifications.

    Kind Regards

    Thread Starter monkeywrench2

    (@monkeywrench2)

    3 months, 3 weeks ago

    I temporarily upgraded to (latest: 2025-08-27.basil) and used the old webhooks (version 2022-08-01) in test mode. Everything appears to be fine and I didn’t get any errors.

    Does this mean, I don’t have to upgrade the webhooks and can simply change the default API version on the stripe dashboard? Or is it advisable to recreate the webhooks for the new version?

    Thanks

    Plugin Author Clayton R

    (@mrclayton)

    3 months, 3 weeks ago

    Hi @monkeywrench2

    Does this mean, I don’t have to upgrade the webhooks and can simply change the default API version on the stripe dashboard?

    Changing the default version in the Stripe dashboard affects future plugins that you create I believe. The webhook created by the Stripe plugin dictates which API version is used.

    Or is it advisable to recreate the webhooks for the new version?

    I would just leave it as it is and let the plugin manage it’s webhooks API version.

    Kind Regards

    Thread Starter monkeywrench2

    (@monkeywrench2)

    3 months, 2 weeks ago

    Hi @mrclayton

    Thanks for all your advice. I have decided to do just that, leave it as it is and let the plugin manage it’s webhooks API version.

    Best regards

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.