k3davis-charges | Stripe Developers | Page 1

autumn bobcat Apr 28, 2022, 12:35 PM

#

Hi! Can you share the two request IDs?

lusty quartz Apr 28, 2022, 12:36 PM

#

sure

ch_3KtWMzFnSqw89al60sEFtOyC
ch_3KtWPXFnSqw89al61maDeR5t

autumn bobcat Apr 28, 2022, 12:38 PM

#

This is the request that created the first charge: https://dashboard.stripe.com/test/logs/req_SJU1rNfC6AUgUJ
And this is the request that created the second charge: https://dashboard.stripe.com/test/logs/req_ibrTSQZIYlkaT1
As you can see, the idempotency keys you passed are different.

lusty quartz Apr 28, 2022, 12:41 PM

#

interesting, neither value is the one i thought i was setting. i'll have to look closer at that. i'm using the .net SDK and setting the idempotency key manually in the requestoptions for the charge. so either it's not passing the value i'm expecting upstream or setting that key in requestoptions isn't having the desired effect.

i'll dig more before asking any followup question - your pointing to the logs is actually broadly helpful to me, i didn't know i could see that detail. thanks!

autumn bobcat Apr 28, 2022, 12:44 PM

#

Yes let me know if you have more questions on this 🙂

#k3davis-charges