#dariodjuric
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- dariodjuric, 3 days ago, 5 messages
Yes, evt_1OIWjbD11gJy8IX8NA6sMgTD
This event happened on the Connected account that's still on "2022-11-15"
How can we make sure that the connected account is also upgraded?
You might need to ask Stripe Support to upgrade it for you: https://support.stripe.com/?contact=true
What if we have many connected accounts? Can they be upgraded all at once?
I think so.
What about newly connected accounts, will they also use the old version or the new one?
I think it depends on the version of the Platform account at the time of the creation.
Hi there 👋 thank you for raising this, I don't think the behavior here looks right, and would have expected that Event to be sent to your endpoint after being rednered with the API version specified on the webhook endpoint. The screenshot you shared appears to be one of our dashboard views, did you see the same structure of the Event when it actually made it to your endpoint, or did your server receive the same content you're showing in the screenshot?
As my teammate mentioned the Connected Account is on a different API version, so the Event would be generated in multiple versions, and I'm a little uncertain how that gets represented in the dashboard views.
Hi @native dune , I don't have the exact payload, but the backend SDK did raise the following exception after receiving that event:
Received event with API version 2022-11-15, but Stripe.net 43.5.0 expects API version 2023-10-16.
I was expecting that the event would have the version specified on the endpoint.
I increased log level and I see the payload now:
{
"id": "evt_1OIXMiD11gJy8IX8Ev15LXaV",
"object": "event",
"account": "acct_1L09meD11gJy8IX8",
"api_version": "2022-11-15",
"created": 1701439608,
"data": {
"object": {
"id": "ca_Nhr4aMTuKaW5Egfg4t8RRP5svEJqIYXn",
"object": "application",
"name": null
}
},
"livemode": true,
"pending_webhooks": 2,
"request": {
"id": null,
"idempotency_key": null
},
"type": "account.application.deauthorized"
}
Thank you, I don't think that's the right behavior from our end, but am getting a teammate to double check.
Thanks
We found this in the meantime: https://github.com/stripe/stripe-apps/issues/928
It could be related.
Thank you, relaying that to my teammates.
Yup, that is the issue, and it is with our teams, I'm pushing on that now but it will likely take time for us to resolve.