Mane

[waxen sundial]

Can fire if a Payout is reversed, for example: https://stripe.com/docs/connect/payout-reversals#webhooks

[lofty grove]

Thanks, I see. But for instance if there is not reversal, then for normal lifecycle of paoyout its not being sent or?
Basically what I am asking is, if I get payout.created event, will there be payout.updated event when it turns to "paid" or "failed" - or update is not for that, and I should listen in addition to payout.paid, and payout.failed events?

And payout updated is only for reversals, when it updates original payout with something like canceled most likely

[waxen sundial]

I'm not sure, you'd need to test it. I suspect no as the payout.paid event is sufficient

[lofty grove]

Mhm, this is what I noticed and wanted to double check. Can I maybe somehow force "update" over stripe dashboard for payout?

[waxen sundial]

I guess you'd just trigger a reversal of a test payout

[lofty grove]

And what about pending state, and switching from paid to failed as stated in the docs?
"Current status of the payout: paid, pending, in_transit, canceled or failed. A payout is pending until it is submitted to the bank, when it becomes in_transit. The status then changes to paid if the transaction goes through, or to failed or canceled (within 5 business days). Some failed payouts may initially show as paid but then change to failed"

if it was paid, is then payout.failed sent to switch it to the failed?

[waxen sundial]

Yes

[lofty grove]

and for pending, is it payout that is created, payout.created with status "pending" or something else is how its set to pending? Since I noticed payout.created mostly being "in_transit"

[waxen sundial]

Some Payouts are created ahead of when they're actually sent, which is what the pending status reflects

[lofty grove]

Aaah i see

[waxen sundial]

i.e. we create the objects ahead of when they're sent in 'batches'

you probably won't see that in test mode

[lofty grove]

Ok, thank you