#jose-checkout-idempotency
low troutBOT
Hello! We'll be with you shortly. 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.
- jose332211, 5 hours ago, 14 messages
- jose332211, 1 day ago, 19 messages
hearty sun
jose-checkout-idempotency
low troutBOT
hearty sun
@fair sorrel that is expected. The Event will only have the idempotency key if it's a direct result of the API request that created it. With Checkout when you get checkout.session.completed it's well after the Checkout Session creation happened
fair sorrel
I'm trying to handle idempotency with session complete checkout events. so the best way to handle it is with the event id?
or how can I get it at checkout session complete?
opaque spindle
Hello! I'm taking over and catching up...
fair sorrel
ok
opaque spindle
Can you explain in more detail what you mean by "I'm trying to handle idempotency with session complete checkout events."? Idempotency doesn't really apply in that situation. Are you trying to deduplicate webhook requests from us? If so, you can use the Event ID to deduplicate.
opaque spindle
You can use the Event ID for that. When a webhook comes in check to see if you've already processed that Event ID or not.
The evt_ ID is the Event ID.
opaque spindle
Happy to help!