If You Have Old Stripe Keys Make Sure to Update Them

Hey Patrick!

Good to hear from you, thanks for taking the time to type this out here.

Hopefully this isn’t a common issue.

Have a great one!

Hey @bftrick!

They’re still valid keys but they don’t work in this plugin.

I wanted to step in and double-check this – you have “rolled” the Stripe API Key and replaced them in the Stripe extension settings, your site is using the latest version of plugins but your customers are now seeing that message?

Did you get an email recently from Stripe about anything regarding your account?

Thanks,

Yep,

I recently rolled my Stripe API Key. ??

I received an email from Stripe a couple days before I noticed my site broke.

Today, when your integration makes an API request to create a Charge, its identifier (ch_12345678) has a length of 17 characters. This is specific to your Stripe account as other accounts already use a length of 27 characters instead. The same applies to other objects in the API such as Subscriptions or Payouts.

[If] you’re using a third-party platform or plugin with a recent version it should already support longer ids as this has been enabled on newer accounts for multiple years. The most common ones would be Spreedly, WooCommerce, WHMCS or WP Gravity Forms for example. If you’re not sure, we recommend that you contact their support team directly to confirm that this change wouldn’t impact you as they built your integration and would be better equipped to confirm.

They didn’t mention keys in the email so I didn’t bother updating them. And I know Woo has always been good about updating Stripe and I had the latest version myself. ???♂?

I just realized I missed a key point in the email:

This change will be rolled out on June 3. If you have any questions, please reply to this email and I’d be happy to follow up.

Since this broke last week it doesn’t have anything to do with the above email.

I haven’t received any other emails from Stripe recently. ??

Hey again @bftrick

Fantastic, that was the email I thought you may have received. And having the content of it here will make it searchable.

I feel this could have been communicated better with possible platform-specific details but knowing that is the email you received, we now know how to handle it for other customers, as my esteemed colleague said – we appreciate you reaching out.

And I know Woo has always been good about updating Stripe and I had the latest version myself. ???♂?

We do try our best ??

If everything is working as expected, please do mark this as Resolved, and I will also add a note to our documentation.

Edit – just noticed your followup. That isn’t ideal but I have seen a few other examples where merchants got that email, updated their keys, and it is working as expected.

Thanks,

Thank you!

*Resolved*