#kemal-idempotencykey
1 messages · Page 1 of 1 (latest)
Unfortunately I don't think it is possible for you to look payments up that way. Do you have the ID for the payment intent or something?
our use case is to check on status of requests that we didn't get response on
without attempting to make charge if if didn't go through already
If you make the call again with the same idempotency token, we will send you the response again
if stripe never received the request we would end up with fresh charge
is that correct ?
is there any way to prevent it ?
Ah, understood.
Trying to think of what you can do here
Can you explain the use case a bit more?
Like is this the general response you are thinking of for calls that time out and whatnot?
we have automated and end user payment flows, they could be triggered simultaneously
we could prevent making another attempt by tracking what's is currently pending
but have a problem with cleanup
if we clean up after let's say 2mins, we would like to know if charge gone through without actually making it
If you have not heard back from us in 30 seconds, that call has failed
We hard fail requests after 30 seconds.
Are you seeing cases like this at the moment?
we have seen request last 60 sec in dev env. We werent sure this will happen on production or not
thanks for your help
Do you have a request ID on that?
not at the moment.
it was a while back
i ll contact again if i face again same issue
Hey one sec @tame zealot just to clarify: idempotency keys only apply for 24h
after that it would run the request again as if new
but no you cannot retrieve by idempotency key used
so just to be clear: for the clean up shortly after as you mentioned, (eg, 2 minutes) then this is fine, using the idempotency key will be safe to re-submit
but the next day, for example, that is not the case
NP!
regarding this, are you sure those were hanging waiting for Stripe, vs waiting for your own server? the same should apply in test and live mode
i ll have a look more on our end