#jonathanbull
1 messages · Page 1 of 1 (latest)
Would the request ID be appropriate?
https://stripe.com/docs/api/events/object#event_object-request
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
ID of the API request that caused the event. If null, the event was automatic (e.g., Stripe’s automatic subscription handling). Request logs are available in the dashboard, but currently not in the API.
No that will be present if you are manually retrying yourself. That would only be null if it was a Stripe automatic retry
The only way to see the information you want is to look at the request in the Dashboard
If there is a source: "dashboard" there then you know it was created via a Dashboard action
This source information that you see when looking at a request in the Dashboard is Dashboard-only
So you can't get this via webhooks/API
Does the webhook event not contain the RequestID?
I'm sorry
I misread your initial question
Moving too fast.
So yes, you can look for whether there is a request ID in the Event for whether it was a Stripe-initiated request or initiated by your account via your API integration or the Dashboard.
So if the only way you retry these payments manually is via the Dashboard then that is a reliable way.
(I initially thought you were asking how to tell the difference between your API manual retries vs. Dashboard manual retries, sorry about that).
Great, thank you! And will the attempt_count on the payment_failed event increase by 1 every time we hit retry in the dashboard?
Thank you! And how about if the payment fails on an invoice screen hosted by Stripe? Will that increment the attempt_count?