#timmy_error
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1289130752146931792
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi! Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support site 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.
Sorry, I can't find this request ID. Here the response received from Stripe Create Payment Intent API is
{"message":"This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate.","type":"invalid_request_error","code":"lock_timeout"}
Or do you have the PaymentIntent ID?
Or can you share with me your merchant ID? you can find it from the Stripe Dashboard -> Settings ->Account Details
acct_1EBdKlB02sbMzSSP merchant ID
Do you know when this error occured?
2024-09-23 04:41:18 UTC+0
Ok, found the request, let me take a look
OK! Thanks
Why do you need to charge the customer many times?
What's the use case?
We provide the partner the service saving the card in advance and charge directly later. And the partner may charge many times in a short time. Is the use case not permitted?
many times in a short time
How many, and in how short time?
Approximately.
But I also don't think that you can charge the customer while another charge is in progress.
At most, 2-3 requests can be made in a minute.
Yeah, this might cause a problem. If it's the same customer, why wouldn't you charge them once for the total of their purchases?
I'm not sure the partner operates in actually. But from our Log Dashboard, I found many requests were made in a short time.
So, we should avoid the new charging request before the previous one finishes ?
Yes, if it's the same customer.