surreal_webhooks

[manic lily]

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

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

[rancid lance]

What's the goal? You just want to prevent a customer from creating multiple checkout sessions?

[eternal cloud]

Basically if there is a network issue between my apps response and the webhook receiving the response, webhook will retry and extra products will be created for users without payment

[rancid lance]

Oh you're not talking about the idempotency key set when creating a checkout session? You're trying to prevent duplicate webhook processing? Not sure how an idempotency key factors into that

You could just cache event id's

[eternal cloud]

Yeah exactly. So no idempotency key is sent in a checkout session webhook request? I thought it odd though since it is sent in a payment intent webhook request

Hmm okay I could use another unique id to cache it. I already have a 32 bit nonce but with the volume of traffic it's possible that could be repeated. The evnt ID will 100% always be unique, never repeated?

[rancid lance]

correct

event id's are unique

that idempotency key comes from the event's creation request

id the request your app makes

But event id is the best way to handle this caching

it'll always be populated

[eternal cloud]

Okay that should work, i'll use this approach. thank you!

One sec

Im looking at the session object