Alexander_ | Stripe Developers | Page 1

onyx spearBOT Feb 8, 2023, 2:47 PM

#

hidden night Feb 8, 2023, 2:48 PM

#

Hello 👋
I believe the PaymentIntent API did exist at that point
According to upgrade log, I can find it referencing PaymentIntent on 2014-12-17 API version
https://stripe.com/docs/upgrades#2014-12-17

API upgrades

Keep track of changes and upgrades to the Stripe API.

restive beacon Feb 8, 2023, 3:01 PM

#

I saw it too but it seems to have been added retroactively. E.g. see the docs from 2015 https://web.archive.org/web/20150905230552/https://stripe.com/docs/upgrades (v2014-12-17 doesn't mention PaymentIntents)

#

also in 2018 they didn't mention PaymentIntents at all (only Charges API) https://web.archive.org/web/20180624201208/https://stripe.com/docs/quickstart

whereas in 2019 intents appear https://web.archive.org/web/20190625003128/https://stripe.com/docs/payments/payment-intents

hidden night Feb 8, 2023, 3:10 PM

#

Ah hmm let me see if there's a better source

hidden night Feb 8, 2023, 3:28 PM

#

Okay looks like you're right, some portion of it was added retroactively.
Looking at stripe-node sdk, we added PaymentIntent support in 2018
https://github.com/stripe/stripe-node/blob/master/CHANGELOG.md#620---2018-06-28

Going back to your original question

Or should I pass the latest version when using this API? Thanks in advance.
Some parameters may only be available in the latest version.
You'd likely see something similar to following screenshot on the API ref

restive beacon Feb 8, 2023, 3:32 PM

#

that's exactly what's bugging me, I see this message for charges for example

#

but nothing for SetupIntent. For PaymentIntent I have

#

but I never see message like "unsupported for versions below X". Also just got a setup_intent.created webhook on my test account with v2017 in the payload 🤷‍♂️

#

I wonder if I should use a different version for intents or not

hidden night Feb 8, 2023, 3:37 PM

#

As far as I know, it shouldn't break anything per se (as long as you don't update the API version)
If there are any breaking changes/unsupported parameters then you'd likely see it on the ref. If there's none, that means the API should work fine with your current API version.

restive beacon Feb 8, 2023, 3:41 PM

#

yeah I prefer to avoid updating the global version now, so I'm choosing between v2017 for intents vs using the latest for intents and v2017 for everything else (maintaining both)

#

it looks like there's no imminent risk of using v2017 for intents (and may be easier than maintaining two versions)

hidden night Feb 8, 2023, 3:42 PM

#

Yup, that makes sense.

restive beacon Feb 8, 2023, 3:44 PM

#

thanks for the support 🙇‍♂️ this channel is amazing, keep rocking!

#Alexander_