#jorgezb28 - retried payouts
1 messages · Page 1 of 1 (latest)
yes, for now the count will be enough
as you can see in the attached image we have two
Ok
Also what's the reason you want that info?
Would it be better for your use case to get notified about a retry in real-time?
we are working on a dashboard for our clients, so they want to know if the payout has retries and how many. They don't have access to stripe, just our company
for now we are good to know the count of retries but will be great to know the details of them as well, you know, like a nested object in json payout
There's not a direct way to query this with the API
There are some workarounds though
One moment
You could use webhooks to listen to the payout events (failed, succeeded, etc.) and build this data yourself: https://stripe.com/docs/api/events/types#event_types-payout.canceled
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Something to note is that when a payout is retried, a new payout object is created (with a different id)
You can tie it back to the original payout by using this call: https://stripe.com/docs/expand/use-cases#charges-in-payout
One of the balance transactions will be type:payout and linked to the original one. So you can sort of work things out by looking at that
ah great, and how can I get balance transactions? can we get it with an api call?