#awais_webhooks

1 messages ¡ Page 1 of 1 (latest)

visual turtleBOT
#

👋 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/1264841005329289339

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

rugged bone
signal frigate
#

Hi there, these two events were generated for two different invoices, but these two invoices are for the same customer and I believe that's why your customer received two emails.

rugged bone
#

what is the solution? i mean same user have subscribed a plan and when payment fails it will alwasy do the same on 3rd day it will trigger 3 webhook for 3 invoices? i need on3 webhook on every day , is there any other webhook which can help me with my needs?

signal frigate
#

I don't see a problem here, the retry works as intended, your customer received two emails because they have two payment failures from two different invoices/

rugged bone
#

and how can i limit the stripe that if an invoice is not clear or paid then do not generate other to avoid multi webhook to trigger?

#

all i want from stripe is to send only a single payment failed webhook every day in either by limiting the invoice to create or tell me if i can achieve this my implementing another webhook

signal frigate
#

Looks like you are not clear on how subscriptions and invoices work.

#

These are two different invoices generated by two different subscriptions, and one of these two invoices wasn't generated as the result of payment failure of the other invoice.

rugged bone
#

i have just started working on stripe

signal frigate
rugged bone
#

these can be 2 different invoices but not 2 different subscriptions

signal frigate
#

Wait, you are right, let me take a closer look.

#

Ok, yes these invoices are from the same subscription, and they were generated daily because the subscription interval is daily.

#

in_1Pet3yIQVJgQbJIf0w84y9qe was created at 2024-07-21 06:16:07 UTC
in_1PeWXMIQVJgQbJIfhqu851ER was created at 2024-07-20 06:12:56 UTC

#

The billing_reason for both of these two invoice is "subscription_cycle"

rugged bone
#

these 2 invoice were created on july 21 2024 according to my stripe dashboard

#

this is the invoice you are telling me it was generated on July 20

signal frigate
#

Check the UTC time

rugged bone
#

its only 4 minutes gap

#

o do not think converting it into utc will change it to 20 and 21

visual turtleBOT
signal frigate
#

No, you should check the inovice.created event, not the invoice.payment_failed event.

#
rugged bone
#

ok thank you