lucynoodles20 | Stripe Developers | Page 1

velvet bobcatBOT Mar 6, 2023, 3:49 PM

#

random narwhal Mar 6, 2023, 3:52 PM

#

Hi 👋

We only expose the idempotency key in the Logs section of the Dashboard.

#

What requests are you interested in tracking?

split bolt Mar 6, 2023, 4:02 PM

#

I see. Okay, we can probably design another way to monitor it. I'll decide with my team if that's necessary.

Looking to monitor for creation of Payment Intents. We have retry logic that occasionally results in double charges. We want to add idempotency keys to prevent that but also want to make sure that this doesn't accidentally result in suppressing legitimate retries.

random narwhal Mar 6, 2023, 4:05 PM

#

Okay and is there a reason you wouldn't just log this in the response to the API call to create the PI?

split bolt Mar 6, 2023, 4:06 PM

#

What do you mean? My understanding is that the info is in the header, which is not something we currently touch in the main logic

random narwhal Mar 6, 2023, 4:09 PM

#

Well you can programmatically set the idempotency key directly in the API request: https://stripe.com/docs/api/idempotent_requests

split bolt Mar 6, 2023, 4:09 PM

#

I meant in Stripe's response. Whether it is a replay is in the header

#

We can log it yes

#

Was just checking to see if it's already there in the dashboard

random narwhal Mar 6, 2023, 4:14 PM

#

I just tested this myself with the Python client library. I can print all the headers by writing payment_intent.last_response.headers.

split bolt Mar 6, 2023, 4:20 PM

#

I haven't yet figured out how to do this in Rails

random narwhal Mar 6, 2023, 4:22 PM

#

We have an example of how to access the response object using stripe-ruby here: https://github.com/stripe/stripe-ruby#accessing-a-response-object

#lucynoodles20