#Mane
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
@eternal yew thanks. Can you check what I wrote, just to clarify to me ๐
yes looking into it, just bear with me for a sec
No worries, tyt
Hey! Taking over for my colleague. Let me catch up.
But I think there are cases when its "paid" initially and then after it fails.
Do you have an example ?
is that payout.updated only sent in case of additional changes to already existing payouts, something like refund.updated?
There is nopayout.updatedevent. you can find the list of all events here:
https://stripe.com/docs/api/events/types#event_types
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
So I am wondering what are the cases to trigger tht one
Ah sorry I missed that lol
It occures whenever a change is made on a the payout object
https://stripe.com/docs/api/payouts/object
So this is what I was asking about, if we have payout.paid for instance, can some days later come payout.updated that changes it status to failed?
Another example, if payout.failed for instance is sent, and there are no additional changes to the payout, there will be no payout.updated event for that one?
if we have payout.paid for instance, can some days later come payout.updated that changes it status to failed?
Quiet generic question, do you have an example that trigger the behavior above? when you getpayout.paidthen the payout is paid, when you getpayout.failedthe payout fails... What you want to check/prevent exactly here ?
Another example, if payout.failed for instance is sent, and there are no additional changes to the payout, there will be no payout.updated event for that one?
It should be like this yes.
Well I would like to detect async updates of payout. And trying to find out if there is same behaviour as on refunds. Refund can be success and then fail sometime later and refund.update changes that state. So I am just trying to know if same case can occur for payouts