A recent support request had me debugging and chatting with the Stripe team. The result of that chat revealed an important integration note that I’m sharing with you: Keep your version of the Stripe API up to date in your Stripe dashboard.


Paid Memberships Pro is always tested and integrated on the latest API release – which Stripe provides updates for roughly every quarter. We are now specifying the latest Stripe API version in our API calls in the code, but Stripe will continue to send webhook messages in the format based on the API version set in your Stripe Dashboard. Every time you update Paid Memberships Pro, you should log into your Stripe Dashboard and check if there is an API upgrade available.

It’s easy to update your Stripe API version, here’s how:

  1. Log into Stripe
  2. Go to Account Settings –> API Keys
  3. Click on the “update available” button and then “Yes” to update to the latest version.

For more information on the specific case we saw coming up: The older version of the API would ignore trials in the API calls if the user had already completed their trial (which for Stripe on PMPro is the period of time between the initial payment – if there is any – and the first subscription payment date). We are using “trials” as a way to delay when the subscription starts, especially if you are using prorating code or the Subscription Delays add on. The newer version of the API will respect those trials even if the user had an earlier trial on the Stripe side already.

Comments (10)

What if it warns that upgrading might break the current integration? Do I need to do something with PMPro AFTER updating my API on Stripe? (Yeah, I’m new at this…can you tell? 🙂 )

We should mention something about that warning. They mean that things might stop working if PMPro is not updated to support the new API version. The ideal process would be to update PMPro first, and then any time you update PMPro update the API version in Stripe. If you see a Stripe API update, but no PMPro update, it’s best to wait for PMPro to update first.

Hope that makes sense.

It should be noted that both Stripe and PMPro will do their best to make things reverse compatible to avoid issues if the API calls or versions are off, but things sometimes come up like what happened in this case.

I have recently updated but not sure if this Stripe update was activated by that update or if I need to wait for a further update from PMPro… I have is this the one that I should be waiting for before I update stripe?

Hi Jason, I get the same warning. Do I just “upgrade” or will it break it and if it does what do I have to do to fix it? It is all working fine at the moment! Thanks

I think you should upgrade. PMPro works on the current latest version of the API, and even if you aren’t having problems now, being on the latest version could save you from problems later.

How about a message in the admin to remind us to check this after an update to PMPro? One less thing to forget!

Leave a Reply

Your email address will not be published. Required fields are marked *