#enforcedcastle
1 messages · Page 1 of 1 (latest)
Just focusing on the error message for a second - that error means that there's something wrong with the way you're generating idempotency keys and that would be something you need to fix on your end
I'm coming into this post subscription flow creation, but I can see the idempotency key is being created with sub_id:user_id:sub_period_end_date. What are best practice for creating the idempotency key?
We have a little bit of guidance on that here (https://stripe.com/docs/api/idempotent_requests)
Relevant excerpt:
How you create unique keys is up to you, but we suggest using V4 UUIDs, or another random string with enough entropy to avoid collisions. Idempotency keys can be up to 255 characters long.
Thanks for the documentation, and do all idempotency keys expires after 24 hours? it says they're elligible to expire but doesn't say with certainty that they do actually expires.