#ben_code
midnight obsidianBOT
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.
- ben_code, 13 hours ago, 24 messages
winter vigilBOT
👋 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/1256178386259152939
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
woven swan
hi, do you have the ID of the invoice this happens with , in_xxx ?
tender plover
Yes - once i advanced to like 3-4 days post due date, it triggered. But the invoice should get chargedd the day its due no?
"in_1PWawQS0VeKkc4dxyZw7HY85"
I dont recall having this problem the last time i did testing with test clocks
tender plover
yes, but i had to foreward the clock well beyond hte due date. Should the invoice not be generated as draft shortly ahead of due date, then on due date be charged?
woven swan
yes, but i had to foreward the clock well beyond hte due date. Should the invoic...
yes. That's what happened, no?
tender plover
e.g. was due 27th august, forwarded to 27th, was sitting as draft, didnt charge until 30th
no
it didnt finalise until 30th
woven swan
that's probalbly because your webhook is broken
tender plover
that isnt possible if a hook was never fired from stripe...
also, wehook is production code and works fine
woven swan
https://docs.stripe.com/invoicing/integration/workflow-transitions#finalized
We wait an hour after receiving a successful response to the invoice.created event before attempting payment. If we don’t receive a successful response within 72 hours, we attempt to finalize and send the invoice.
woven swan
no?
tender plover
no, invoice.created handled fine
woven swan
I was about to link that one , to show that it does not have success.
tender plover
it says 200
woven swan
https://coach.staging.xxxx.com/webhooks/stripe
tender plover
thats a diffferent environemnt
stripe developer mode cant differentniate between envrionetms, so anything in dev mode will hit any webook end point. But the ernd point i am currently testing on is the one i linked, which is local env
woven swan
but the event was sent to that URL
woven swan
it doesn't really matter what your code does, from our perspective we sent a webhook to that URL and it returned a 400 (with Could not find a matching user for this event), that counts as a failed delivery, and delays Invoice finalization
tender plover
so even if one of the endpoints fires a 200, youre saying any 4xx will cause the invoice to remain a draft?
as the dev mode doesnt allow us to maintain different end points for diff dev modes, its just one big dev mode for everything
you will see we have 4 end points setup, 1 is inactive (our dev env), one is for connect, one is my local (known shrimp) and one is staging
woven swan
so even if one of the endpoints fires a 200, youre saying any 4xx will cause the...
yes
if any of the endpoints does not return success, that counts as a pending delivery
tender plover
right ok, so thats less than ideal. I may ahve to turn the orthers off whilst i test
woven swan
yep or have them return a 200 when they 'ignore' a request they don't recognise