#lakshya-webhook-deserialization

1 messages ยท Page 1 of 1 (latest)

floral blaze
#

What does "when deployed" means? What changes when you deploy? Which version of the library do you use? Is it a different webhook endpoint? Does it have the same API version set?

sand smelt
#

when deployed as in we deploy on remote server and version and everything is same. The difference is that we use different keys on deployed application.

floral blaze
#

what does "different keys" mean? Different Stripe accounts? If so, are they on the same API version?

sand smelt
#

yes.

#

same stripe version just different account

floral blaze
#

what does "same stripe version" mean though? That sentence can mean multiple things really, that's why I said API version because it's what matters

sand smelt
#

So we use stripe-java and the version is "20.72.0" , I guess this what you mean right ?

floral blaze
#

it is not what I mean but that's part of the confusion. You are using stripe-java which is the client library for your code. The library is pinned to a specific API version which indicates the behaviour of each API request you make.

#

The problem is likely an API version mismatch between the 2 Stripe accounts. One is on the latest 2020-08-27, but the other one must be on an old/different version and it's causing issues.
What you want is to make sure that when you create a webhook endpoint you explicitly set the correct API version matching your library's API version so in your case 2020-08-27: https://stripe.com/docs/api/webhook_endpoints/create#create_webhook_endpoint-api_version

sand smelt
#

ohh, I see maybe that might be a reason, I'll check with my manager quickly

#

can you tell, where I find the existing version on dashboard

floral blaze
sand smelt
#

ok, so I need to just make sure both of the accounts we use has same version

#

anyway if we can update or change this version

#

so if they're different we can quickly change them

floral blaze
#

you can change it in the Dashboard to the latest, but this could impact your live integration if you're not careful

sand smelt
#

ok I see.

#

Thanks

#

Also how it could impact live integrations ?

#

any particular things I need to take care of

floral blaze
#

๐Ÿ˜…

#

It's hard to help without knowing anything about what you know about your own Stripe integration unfortunately ๐Ÿ˜ฆ

#

The API version you are going to change is impacting the entire account, in Live mode and Test mode. This will change the format of all events (which is why your current code doesn't work since it expects version B but that account is on version A) and change default behaviour of some products. Our upgrades API doc https://stripe.com/docs/upgrades covers every single breaking change

#

so you don't want to just click that button without fully grasping the scope of the change for your overall integration for each account

#

But if you use stripe-java everywhere, it means all your API requests already use the specific version associated with that library and they wouldn't be impacted. If you don't have any other integration right now and the only thing broken is webhooks then changing the default version should be mostly fine

sand smelt
#

Okay, I see.