#emng_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1273046011350093937
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
๐
I recommend testing with test clocks in this case: https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage
You can create a test clock, then a customer and subscription within this clock, then advance the time on the clock to see the subscription cycle. This will trigger webhook events related to subscriptions and invoices
Great, I'll take a look. thanks! Last question, is there anything on the subscription object that will tell me that this is a recurring payment?
Not sure I follow
A Subscription is the umbrella for recurring payments. Theres a 1 to many relationship between Subscriptions and Invoices, and each Invoice is tied to a single payment
Can i differentiate payment 1 from 2?
When you receive an invoice.paid event, the payload will include an Invoice object. subscription on that Invoice object will have a Subscription ID (so you know it's tied to a parent subscription) or it will be null (if it's a one-off Invoice)
Each Invoice is its own object with its own ID. Each Invoice is tied to a single PaymentIntent (also its own object with is own ID)