#Kamesh
brittle sluice
gilded cobalt
Can you share what the issue you're facing? What are the expected and actual response?
cold cave
it's there in the chat linked above. want me to post again? thought it will be easier to refer
im happy to post again
gilded cobalt
I understand the issue is with the latest_charge and charges returned due to difference in API version
Have you updated the API version as suggested by alex? If so, what's the problem you're facing?
cold cave
i checked and we already passing the correct apiversion
gilded cobalt
Can you share an example request ID (req_xxx)?
cold cave
passing 2020-08-27
let me get that
I couldn't find the request. let me retry the request and get the request id. might take 10mins.
gilded cobalt
Sure! Sharing the request ID (req_xxx) will be helpful to understand what the issue is
cold cave
can you please check these?
req_ky3wJ9V2zaeWOk
req_cC8EJq1s4tLMjb
req_r7NoTgmEEl40b0
i can't see the response on stripe dashboard but it's likely one of these one's.
gilded cobalt
Stripe doesn't save response for GET request. Can you share the raw response that you received?
Based on the POST confirm request https://dashboard.stripe.com/test/logs/req_e95tDTJCW6E9Bu, I can see both charges and latest_charge have been returned
gilded cobalt
I can't find the GET request for the above two payment intents you shared. I'm able to see their charges and latest_charge in the confirm requests, e.g. https://dashboard.stripe.com/test/logs/req_sV1zeIBdXifqad
Moving forward, latest_charge is the recommend approach to get the charge ID
I'd recommend using latest_charge instead
cold cave
but we have other regions which doesn't return latest_charge, we cannot have separate code base for different regions. this is why we are trying to ensure we pass the default api version, but that doesn't seem to woprk
gilded cobalt
For the above example payment intents response, i can't find their corresponding request ID. Can you share the both request ID (req_xxx) and the response, so that I can double check everything is set up correctly? I'm unable to reproduce the behaviour mentioned
cold cave
sorry we were looking at it wrong. this is the event we received which sends latest_charge while other regons sends charges
we are not making a get call in this specific scenario
gilded cobalt
In https://dashboard.stripe.com/test/webhooks/we_1NgHI2AbyUDQHodHjBSA0zfe, the API version is default account API version with 2022-11-15. It's expected that charges isn't available in API version 2022-11-15 since it's removed: https://stripe.com/docs/upgrades#2022-11-15
You may create new Webhook endpoint with API version to 2020-08-27 using API: https://stripe.com/docs/api/webhook_endpoints/create#create_webhook_endpoint-api_version
cold cave
we add the stripe webhook from stripe dashboard. how can we change this from dashboard?>
I tried to create a new one, but not letting me select older version
gilded cobalt
API version can't be changed in an existing Webhook endpoint.
Dashboard doesn't support adding Webhook endpoint with older version. It can only be done with API.
cold cave
there is no other option? we don't have api integration for this scenario
gilded cobalt
I'm afraid there is no other way excepting creating Webhook endpoint with older API version using API
cold cave
Thanks