srkishy-disputed-refunds | Stripe Developers | Page 1

solemn stream Jul 5, 2022, 6:06 PM

#

Do you have an example request ID?

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

wicked siren Jul 5, 2022, 6:07 PM

#

Yup, /req_MrEHAbTBOtItNY

solemn stream Jul 5, 2022, 6:20 PM

#

How is the refund being created? Via the dashboard or via the API?

wicked siren Jul 5, 2022, 6:20 PM

#

Via the API

solemn stream Jul 5, 2022, 6:22 PM

#

Okay, let me dig on this a bit and get back to you

#

Can you confirm that you are using idempotency keys when creating refunds?

https://stripe.com/docs/api/idempotent_requests?lang=python

Stripe API reference – Idempotent Requests – Python

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

I think the issue is that the API is interpreting the request as a "replay" of a previous refund creation, as opposed to a new refund altogether

wicked siren Jul 5, 2022, 6:27 PM

#

Yeah, we're using idempotency keys

#

Hmmmm, that would make sense as to what's happening, was hoping since the initial creation failed it would allow it to succeed later

solemn stream Jul 5, 2022, 6:29 PM

#

This is news to me as well, but as I'm looking at the request, that seems to be the reason the 2nd refund isn't succeeding.

wicked siren Jul 5, 2022, 6:32 PM

#

Ok, I confirmed I was able to create the refund through the API, I'll try changing the idempotency key

#

Ok, confirmed changing the key works. Definitely not an ideal flow for us as currently we make an order on our side to track the refund, and the idempotency key we use is attached to that order.

#

But, assuming that's not going to be changed anytime soon, we'll try to find another way to handle it, thanks for the help!

#srkishy-disputed-refunds