API request to create a Charge

Here is what they said

I’m $$$$ and I work as a support engineer here at Stripe. I’m reaching to discuss a minor change we are rolling out which could impact your Stripe account for $$$$$

Today, when your integration makes an API request to create a Charge, its identifier ($$$$$$) 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 Balance Transactions or Payouts.
We’re going to make a change on our end so that all new objects on your account have the longer identifiers moving forward. This is in line with our policy of backwards compatible changes called out here [1] where we mention that our object identifiers can be up to 255 characters but we still wanted to give you a heads up before making the change.

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

I also wanted to clarify that the new behavior has already been enabled in Test mode on your account since February 25 without any issue. We recommend that you investigate how you store information from Stripe in your database and if any column storing resource ids such as charge or payout id could have a length limit that is now too short. 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.