#avery_payment-overcapture
1 messages ยท Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- avery_best-practices, 1 day ago, 7 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255649494985474090
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
I'm not sure I understand the question. Can you elaborate?
There was a change with visa debit cards, which doesn't allow them to use overcapture or extended capture anymore. This is a problem for a lot of Stripe customers and I was wondering if Stripe has any workarounds at the moment?
As far as I know, overcapture is still supported on Visa debit cards up to 20%: https://docs.stripe.com/payments/overcapture
avery_payment-overcapture
That's what you would assume
It's just started happening on Thursday
We have a workaround for a certain number of use cases, but not with extended capture use cases
@graceful juniper I'd recommend reaching out to our support team for discussing things like this and they should be able to investigate concrete examples and guide you towards the best solution
๐
โค๏ธ