afenster | Stripe Developers | Page 1

waxen bisonBOT Nov 11, 2022, 8:44 PM

#

fervent drum Nov 11, 2022, 8:45 PM

#

What's the usecase for using the new version? You should be able to continue with the old version if you like

lapis star Nov 11, 2022, 8:47 PM

#

We want to switch to using the Payment Element. In the sample code it has a switch statement based on the PaymentIntent status. The old PaymentIntent statuses aren't in the switch statement.

I could modify the switch to look for the old statuses. But if I'm making something new, shouldn't I use the latest? Is there a problem with using the old one?

#

Is there a compliance issue with using the 2016 version? Am I missing out on any features? I'm 7 versions behind. I must be missing out on something.

fervent drum Nov 11, 2022, 8:53 PM

#

Yeah a ton has changed since 2016. But, if your organization isn't ready to migrate to a new version for whatever reason, then you will have to adjust your code to work with the older api version

#

I do recommend using the latest version

#

But I get that that's a business decision and comes with tradeoffs

lapis star Nov 11, 2022, 8:57 PM

#

Is it possible to run one version for new things: Terminal and Payment Element and another version for older things: Card Element?

#

Can we set the version in our code? Or is there only the one setting in the Dashboard that will apply to everything?

fervent drum Nov 11, 2022, 8:58 PM

#

Yeah you can set version on a per-request basis if you'd like: https://stripe.com/docs/api/versioning. Keep in mind that can make for some difficult-to-maintain code though

lapis star Nov 11, 2022, 8:59 PM

#

OK, I'll read through that. Thank you. Have a good weekend.

#afenster