#arun_api

1 messages · Page 1 of 1 (latest)

dreamy meadowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1326425954867744789

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

gray ferry
#

Our recently onboarded customers want to use the latest web hook versions, but if I change the stripe.net.dll to latest old webhook is failing, how can I handle it without impacting the exsting customers who are using old webhook versions

frail tiger
#

Sorry it looks like you have multiple questions. Could we focus on each of them first? Regarding ApiVersion, which error message have you encountered?

gray ferry
#

46863 System.Runtime.Serialization.SerializationException: Type 'Stripe.StripeException' in Assembly 'Stripe | Financial Infrastructure to Grow Your Revenue , Version=41.4.0.0, Culture=neutral, PublicKeyToken=null' is not marked as serializable.
ERROR: Unable to process callback data posted from gateway

frail tiger
#

request id as req_xxx

gray ferry
#

Our recently onboarded customers want to use the latest web hook versions, but if I change the stripe.net.dll to latest old webhook is failing, how can I handle it without impacting the exsting customers who are using old webhook versions

#

can you please answer this

frail tiger
#

Could you elaborate a bit more on that? So you onboarded "customers" are your Connected Account, and you are setting up their connect webhook for them?

gray ferry
#

we are using stripe in our product

#

when we initially did the integration webhook was 2022 and i think we used stripe.net.dll version 41.1

#

now if we want to use the 2024 webhook version it is not supported for stripe.net.dll 41.1

#

without changing stripe.net.dll version, is there any option to use 2024 webhook?

frail tiger
#

No I believe with .NET, the SDK version comes with the webhook API version

gray ferry
#

can we make use of
// See your keys here: https://dashboard.stripe.com/apikeys
var _options = new WebhookEndpointCreateOptions
{
Url = "https://example.com/my/webhook/endpoint",
EnabledEvents = new List<String>
{
"payment_intent.succeeded",
"payment_intent.payment_failed",
},
ApiVersion = "2020-03-02",
};

frail tiger
#

No that's different

gray ferry
#

Is there any other option we can make use of ?

frail tiger
#

Unfortunately no. The SDK version is pinned with API version and you would need to upgrade SDK version for newer API version

gray ferry
#

why the below code is used
var _options = new WebhookEndpointCreateOptions
{
Url = "https://example.com/my/webhook/endpoint",
EnabledEvents = new List<String>
{
"payment_intent.succeeded",
"payment_intent.payment_failed",
},
ApiVersion = "2020-03-02",
};

frail tiger
#

This is to create a new webhook endpoint pinned to the ApiVersion 2020-03-02. You can specify other value here too, but it wouldn't be compatible with your SDK defined version

gray ferry
#

which SDK version is this compatible with?

#

with the new sdk version can i make use of this ?

frail tiger
#

I would recommend the latest SDK version of v47.2.0

#3036 This release changes the pinned API version to 2024-12-18.acacia.

gray ferry
#

with this approach no need to create webhook endpoint on dashboard, is that right ?

frail tiger
#

Yes it would be the same

gray ferry
#

ok

#

Is WebhookEndpointCreateOptions is compatible with 41.1 version ?