#Mane

1 messages ยท Page 1 of 1 (latest)

still thistleBOT
eternal yew
#

๐Ÿ‘‹ happy to help

merry wagon
#

@eternal yew thanks. Can you check what I wrote, just to clarify to me ๐Ÿ™‚

eternal yew
#

yes looking into it, just bear with me for a sec

merry wagon
#

No worries, tyt

sullen yoke
#

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 ?

merry wagon
#

So I am wondering what are the cases to trigger tht one

sullen yoke
sullen yoke
merry wagon
#

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?

sullen yoke
#

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 get payout.paid then the payout is paid, when you get payout.failed the 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.

merry wagon
#

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