#๐Ÿ’ช๐ŸฆŠ

1 messages ยท Page 1 of 1 (latest)

wide oxideBOT
lapis field
#

Can you provide the event IDs (evt_123) that you are looking at here?

#

Not immediately sure why this would happen but can look in to it

mighty holly
#

evt_1LkZWz2YEAMYCphp3qVfV6tX

#

wait

#

this is how they all come in

#

would you like all of them?

#
evt_1LkZWz2YEAMYCphp8Lf3LJvM - UPDATED
evt_1LkZWz2YEAMYCphp9KA4Z6yY - PAID
evt_1LkZWz2YEAMYCphp3qVfV6tX - FAILED```
lapis field
#

Thank you, having all the IDs helps here. I will look in to this in a minute

oak forge
#

Hello! Just hopping in since Pompey has to head out

mighty holly
#

ah okay. So I can't really be sure that the payout succeeded when the .paid comes through

oak forge
#

You can check the status of the payout you get back from that event, which should tell you whether is succeeded or failed

mighty holly
#

oh. So technically I don't need to listen for payout.failed. and can just determine whether it failed or not from the payout object returned in payout.paid?

#

*edit

oak forge
#

Just to be safe I'd still listen for payout.failed (I think there may be some edge cases where the Payout may first say paid and then move to failed)

mighty holly
#

so are you saying that payout.failed CAN appear without payout.paid appearing first?

#

because what I'm trying to do is send an email saying that the payout is successful or not

#

and If I get a payout.paid first and send that the payment is successful, but then it fails...

#

Hm. Okay Ill do a different approach I'll send an email saying something like "Payment has been initiated" and then if I receive a payout.failed I will send a second one saying it failed

#

cover all bases like this. thank you

oak forge
#

Yeah - sorry this behavior is a bit odd. Your approach should definitely work (and optionally, you could also send an email with payout.paid but the messaging will be more like - this is when your payout is expected to be paid out, but isn't guaranteed yet)

mighty holly
#

the webhook with account.external_account.updated does occur

#

but, the account... isn't disabled?

#

unless this is to do with the fact that I am in dev mode?

oak forge
#

Yeah, I believe it's because you're in test mode

mighty holly
#

right okay