#Sinduri
1 messages · Page 1 of 1 (latest)
They're now omitted by default, yep. You'll need to make an additional API call to retrieve the Charge and 'expand' that field.
it's fine for other events, but when the event itself related to refund why you guyz omitted the refund data?
It's an API optimisation: https://stripe.com/docs/upgrades#:~:text=2022-11-15-,Charge,but for performance reasons we recommended against doing so unless needed.,-The charges property
One more thing to ask I am a plugin developer, and we're passing the stripe version upto which we are compatible to avoid compatibility issues happening for live customers when there is a version change from Stripe's end
All server side and client side API requests are working fine then, but for webhook events the crash with latest Stripe API version
Is there any method to override using the API version in the customer's stripe dashboard for webhook events?
I suspect your webhook(s) are fixed to a specific version and aren't using your account default version. Can you share an example?
The scenario is, We have developed a Stripe plugin for WooCommerce, As of now our plugin is compatible with 2022-08-01. Thus we are passing this version in all our API calls to override the API version in our customers Stripe dashboard
Can you share a webhook ID (we_xxx)?
Is there any option to override the default version in Customer Stripe dashboard for webhook events
Our plugin has 10k+ active install in WordPress platform itself. Our plugin only compatible upto 2022-08-01. If any customers with latest API version using our plugin, then webhook events would not work
Well, you shouldn't be creating webhooks for your connected accounts. You should be using a Connect webhook: https://stripe.com/docs/connect/webhooks
But I can't really advise anything further with an example of the issue you're facing
You'd specify the api_version when creating the webhook: https://stripe.com/docs/api/webhook_endpoints/create#create_webhook_endpoint-api_version
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
But again, a specific evt_xxx example would help here
okay, this sounds great
one more concern, If we create webhook endpoint with version X and then bring compatibility with latest Y version, then how can we update the version of the already created webhook endpoint
Hi! I'm taking over this thread.
then how can we update the version of the already created webhook endpoint
If you created a webhook endpoint with an API version explicitly set, you won't be able to change the version later. Instead you'll have to create a new webhook endpoint.
If your webhook endpoint use the default API version of your account, then updating your default API version will automatically update the webhook endpoint version.
Okay, thank you