#yb-stora_webhooks

1 messages · Page 1 of 1 (latest)

untold dewBOT
#

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

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

scarlet dust
toxic gulch
#

any idea why i don't see them in the invoices?

scarlet dust
toxic gulch
#

ack! 👍 i assume it's no longer recommended to manage invoice states by listening to payment intent events?

scarlet dust
#

Generally, you should only need to listen to invoice.* events

#

Now since multiple PaymentIntents can be associated with the invoice, it gets trickier

toxic gulch
#

got it. i wanted to listen to invoice.updated only but i observed some weirdness. look at this invoice for example (in_1TMr4jRGCWPnlEBEAIq1a6rS). it has two invoice.updated events. one where the invoice status went straight from draft to paid without hitting the open (finalized) state. that seems weird

#

so my question is: are we guaranteed an invoice.updated event for at least the transition to paid status? i may be tempting the gods here tbh

scarlet dust
#

At first, it seems like a weird race condition to me but to identifiy if the invoice was paid or not, you should just listen to invoice.paid event instead

#

Looking internally, an internal source confirms that draft to paid is indeed possible (so not a race condition as I assumed earlier)