#dorian_subscription-webhook-events
sonic sequoiaBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- dorian_paymentintent-subscription, 4 days ago, 6 messages
- dorian6730_best-practices, 6 days ago, 5 messages
rain sierraBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1254923557721477121
đ Have more to share? Add details, code, screenshots, videos, etc. below.
simple quest
Hi there
burnt wharf
Hi
simple quest
You should see payment_intent.processing prior to payment_intent.succeeded
burnt wharf
Ah ok thanks
Another mod recommended listeing for invoice.paid for subscription payments. But if I listen to both invoice.paid and payment_intent_succeeded, I would be double processing wouldnt I?
rain sierraBOT
simple quest
You'd have to compare the two events to make sure you don't double process. The payload for invoice.paid will include an Invoice object, with a payment_intent ID. The payload for payment_intent.succeeded will include a PaymentIntent object, with an invoice ID