#blingus_webhooks
flat solarBOT
👋 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/1257778552238243881
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
zealous junco
Hello
Some payment methods like bank debits (ACH, SEPA etc) are considered delayed notification payment methods. So it may take upto 3-4 business days to complete the payment.
dense verge
right, i am just learning that 🙂
zealous junco
That's alright 🙂 In such cases, the webhook events you listen for depend on your usecase.
Like invoice.paid is generated when the invoice is marked as paid after the payment is complete/succeeds
dense verge
so i used the stripe cli with stripe trigger invoice.paid
I am wondering how to connect that with a test subscription so I can make sure I setup my webhook to update the correct subscription object
on my own backend
just to see the shape of the data
zealous junco
each invoice.paid event has Invoice object as the payload.
If it is a subscription invoice then the object should have a subscription parameter that will contain the subscription ID
dense verge
is there a way to test that? also, I currently have a live customer with an incomplete subscription, a failed payment, and an open invoice- is stripe going to continue to try to charge them until it goes through?
thank you for that invoice doc, looked at it but didnt connect it to my trouble
i think i understand the invoice paid, only thing i am wondering is how the failed payment works- just so i can craft my access rules
zealous junco
I think the issue is that Stripe CLI might only be triggering invoice.paid for a one-time invoice (not for a subscription)
I'd recommend creating a test subscription and using a test clock to simulate forward timing movement
https://docs.stripe.com/billing/testing/test-clocks
That should allow you to change state and trigger various webhook events for a subscription
dense verge
and i found her activity log with objects (new to stripe, forgive me :)) and I think i see what I can do
zealous junco
All good 🙂
dense verge
I think the issue is that Stripe CLI might only be triggering invoice.paid for a one-time invoice (not for a subscription) - yes exactly
i def did that on initial setup, i just didnt realize some of the payments would have a lifetime outside of checkout
but i think i see enough of the data shape to handle these events
so, thank you!