arnav_best-practices

[empty pine]

👋 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/1481871029499592836

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[chilly yarrow]

I have done more research and it seems that for card payments there is no fee when an 'insufficient funds' error is hit

However for BECS payments there is a fee of $2.50 when there is insufficient funds

If you could also determine if there are any fees for PayTo transactions when the insufficient funds error is hit.

[vestal plank]

Hi! This channel is focused on developers and technical questions. We don't have the expertise in fees. You can reach out to our support team and they will be able to assist you better for this: https://support.stripe.com/contact

[chilly yarrow]

oh ok, thanks for the support link

I have another developer related question. Currently I am doing testing and encountering a bunch of 429 errors, is there a way I can increase the concurrent request limit from stripe ?

At the upper end I will be processing 5000 invoices in a day and would like to schedule them to all go out at the same time. Currently I am just spreading it out accross the day but I was wondering if it is possible to increase the limits on my stripe account

[vestal plank]

Can you give me a request ID (starts with req_) where you got a 429 error?

[chilly yarrow]

req_80qPsEZrZ9nEgl

[vestal plank]

Looking into this now.

This requests errored out due to lock_timeout. As mentioned in the error, increasing concurrent request limit won't help this situation:

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.

[chilly yarrow]

How do I ensure that I dont hit the 'lock_timeout' error?

[vestal plank]

The issue with this request (https://dashboard.stripe.com/acct_1PHEfKFR2gE6U1mQ/test/logs/req_80qPsEZrZ9nEgl) is that it was created at 2026-03-11 00:17:13 UTC. However, 3 seconds earlier you had created the same request for the same customer with the payment method: https://dashboard.stripe.com/acct_1PHEfKFR2gE6U1mQ/test/logs/req_uqI4KyyAQPxjXa.

You got the object lock because first payment hadn't finished processing and the second one was created. You should wait for the event to confirm that the payment was completed before creating a new request.

[chilly yarrow]

Oh right so if there was a different customer there then I wouldn’t have gotten this error

I was testing our system and its ability to handle 3000 invoices going out but I assigned all the invoices to the same customer

Do you think if I assigned 3000 invoices to 3000 unique customers I won’t run into this issue ?

[past walrus]

hello, taking over the thread as my colleague need to step away 👋 give me awhile to catch up

Do you think if I assigned 3000 invoices to 3000 unique customers I won’t run into this issue ?
It's possible you may not run into lock timeout issue in a scenario with 3000 unique customer, assuming they also have different payment method objects. But depending on your integration design, you may run into rate limits.