caits._35113 | Stripe Developers | Page 1

hello! unfortunately not, in this doc we mention that

https://stripe.com/docs/upgrades#what-changes-does-stripe-consider-to-be-backwards-compatible


This includes adding or removing fixed prefixes (such as ch_ on charge IDs).

You can safely assume object IDs we generate will never exceed 255 characters, but you should be able to handle IDs of up to that length. If for example you’re using MySQL, you should store IDs in a VARCHAR(255) COLLATE utf8_bin column (the COLLATE configuration ensures case-sensitivity in lookups).```

The other bit which you can look out for is the prefix i.e. `fctxn_`

every object has it's own prefix e.g. PaymentIntents will start with `pi_`, SetupIntents will start with `si_`

API upgrades

Keep track of changes and upgrades to the Stripe API.

#caits._35113