#nobody_api-behavior
jaunty lindenBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1282850206727147521
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
pastel pecan
I currently use webhooks for payment intent confirming and refunding, but the docs don't make it super clear which events are async?
wraith silo
@pastel pecan do you have a more detailed question (if so, best to put it in the original form so taht we can know your real question)
pastel pecan
Gotcha
wraith silo
We don't really document much around what is async and what isn't.
pastel pecan
Yeah i can see that lol
wraith silo
What's your real question?
pastel pecan
I mean I would just like clarification on the general rules. For instance i create connected accounts, do i need a webhook for that?
Is it just payment is async?
wraith silo
A lot of this is much easier done by just testing than guessing
Creating an Account is synchronous, like anything payment. But then things can happen async after, such as identity verification, additional requirements, etc.
There's no account.created Event since the creation is synchronous, but as a Connect platform you definitely should have a Connect WebhookEndpoint to listen to Events on connected accounts and specifically listen for account.updated which are triggered async when new requirements are needed, things are verified, etc. see https://docs.stripe.com/connect/webhooks
nobody_api-behavior
pastel pecan
ok interesting thanks ill do that. Its just a bit frustrating because i implemented refunding synchronously and then realized after the fact that it's probably asynchronous
wraith silo
Refunds are mostly synchronous, as in their creation succeeds/fails synchronously. But then they can fail asynchronously. We do document this clearly I think here: https://docs.stripe.com/refunds#failed-refunds
pastel pecan
Yeahh exactly. Just to confirm my understanding, charge.refunded will fire when the refund sucessfully processes, and charge.refund.updated fires when it fails?
If so then i should be good thanks
wraith silo
not really. charge.refunded will fire when the Refund is created. We don't know if it succeeded yet, we won't know until days later usually. If it were to fail (which is rare) then charge.refund.updated is sent
pastel pecan
that's so confusing 😭
charge.refunded is fired when a refund is created, not refund.created
but ok i'll just listed in charge.refund.updated thx
wraith silo
refund.created is special and hapens for what we call "out of band refunds" without an original Charge.
jaunty lindenBOT