#williamkim

1 messages ยท Page 1 of 1 (latest)

snow adderBOT
marble shell
#

Yes you can make API requests for any version of the API, it is not restricted by your account's default version

#

You can also create a new webhook endpoint and specify that it should use the latest API version if you want to test with that before upgrading

jagged compass
#

So, is the API version 2017-12-14 still compatible with gem version 8.5.0 - 2023-03-30 ?

marble shell
#

Yes it should. Our changelog does not specify that the Ruby library is pinned to a certain version

#

We do do that for strongly typed languages like .NET where object structures are rigidly defined but as far as I can see our ruby library does not have that restriction

jagged compass
#

Speaking of the webhook endpoint, Stripe documentation says, "For webhooks, you can override the version of a single test webhook endpoint in your Dashboard." It also syas, "Change the version of a test webhook endpoint to the version you want to test." (https://stripe.com/docs/upgrades#how-can-i-upgrade-my-api)
But I can't seem to find find any spot in the Stripe dashboard that allows me to change the version of the existing webhook endpoints. Is it possible to change them to a version other than the newest version? Also, is it possible to create a new one with a version of my choice through the Dashboard?

marble shell
#

It is possible to create one with a new version of your choice in the dashboard. The choice will be a dropdown on the create endpoint page

#

Not sure on updating. Will check quickly

#

So I think you need to delete the old one and create a new one

#

Will make sure we correct that language about updating an existing one

jagged compass
#

The dropdown gives me only two choices: "Your current version" and "Latest API version". Could you confirm that I can select a version of my choice (I'd like a version in between them)

marble shell
#

For that you need to use the API

#

For some reason the dashboard only offers those two but if you create the endpoint via the API you can use any valid Stripe version

snow adderBOT
jagged compass
#

If I create a new webhook endpoint with a higher API version, will it receives events with the higher version, while the existing endpoints still receive the same events in the default version?
(In other words, if I have 2 webhook endpoints with different versions, will each endpoint receive the same webhook event in its own version?)

marble shell
#

Correct. If you don't specify a version, the endpoint will use your account's default. If you do specify a version, the endpoint will be pinned to that version regardless of your account's API version

#

So that endpoint will not affect the account version and the account version will not affect the endpoint

jagged compass
#

Just to clarify, if I create 2 webhook endpoints with different versions, they will receive the same webhook event in their own versions, right?

marble shell
#

Yes

#

We will generate the event in each version that you have an endpoint in

jagged compass
#

When I upgrade the default API version, Stripe Dashboard only allows me upgrade to the newest version. Is there a way to upgrade to a less-new version?
(Upgrading to the newest version is still overwhelming even after considering all the techniques we discussed above, because our current default version is too old. It would be really nice if we can upgrade progressively version by version.)

deep moss
#

There is not, no, though if you have a specific need for that you can write in to our support team for help with that, if you're unable to upgrade to the latest for some reason (SDK compatibility etc)

jagged compass
#

We're planning on implementing Direct debit services such as British BACS and Australian BECS. What is the oldest API and SDK version that Direct debit was supported?

snow adderBOT
azure wind
#

๐Ÿ‘‹ Hopping in here since synthrider has to head out - did you still need that latest question answered?

jagged compass
#

Yes, please

azure wind
#

There's no end of life that I know of for Card Element (it should still be supported for a while)

#

As far as I know you shouldn't need to be on a specific API or SDK version in order to use BACS or BECS - are you seeing specific errors when you try and use them on an older version?

jagged compass
#

I am just wondering if those services will still be implementable without upgrading our API & SDK versions. If there's no version-related constraints, then we would consider developing the services first, and then tackle on the upgrades later.

azure wind
#

Yeah as far as I know there shouldn't be any need for you to upgrade your API and SDK to implement those two payment method types

jagged compass
#

Thank you all for your great answers! You guys rock!