#ade_error
spare mapleBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1257768396456722523
đ Have more to share? Add details, code, screenshots, videos, etc. below.
dense gale
Hello! Looking...
gloomy bridge
thanks
spare mapleBOT
dense gale
You seem to be reusing that idempotency key for many different requests.
gloomy bridge
yes , the best practise here is confusing , we tie the idempotency keys to the payments
i think thats wrong ,
so we should tie it per request
dense gale
That's not the correct approach. Idempotency keys are designed to be tied to specific requests, not payments.
gloomy bridge
okay great thank you
dense gale
Have a look here for more info: https://docs.stripe.com/error-low-level#idempotency
Also note that the Stripe Node library will automatically generate idempotency keys for you and use them to safely retry requests if you enable network retries: https://github.com/stripe/stripe-node?tab=readme-ov-file#network-retries
gloomy bridge
okay great
dense gale
That approach is recomended over generating and using your idempotency keys, unless you have an advanced or unusual use case.
gloomy bridge
yea that make sense