#jedesache_webhooks-paymentintent
floral gobletBOT
đ 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/1270417065852928042
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
halcyon cloak
jedesache_webhooks-paymentintent
@dense elk payment_intent.succeeded is the canonical Event that indicates whether the PaymentIntent has completed successfully or not. For ACH you also have payment_intent.processing that indicates the PaymentIntent is in processing and we're waiting to see if the underlying payment succeeds or fails
dense elk
The problem (I think) with that is if I listen to .processing then I'll get charges that may not actually succeed on cards, and if I listen to .succeeded, the cards will be successful, but the payouts with ACH included in them will already be generated.
halcyon cloak
You really ought to listen to both Events and handle the sync vs async payment methods that way
dense elk
Or does payment_intent.processing only exist for ACH and I need to listen to both? I may be getting myself confused thinking about the status in the webhook events.
Okay. I'll give the process some more thought and re-review some past events to see if I can spot the pattern to follow.
halcyon cloak
sure thing!