#yoyo_overcapture-visa-ineligible
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.
- yoyosaur_error, 2 days ago, 24 messages
- yoyosaur_error, 2 days ago, 13 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/1253762552765091971
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
I have seen this recently
https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.20686.html
Is it possible this is at all related?
Visa invites industry leaders to its annual Payments Forum to set agenda for the future of commerce Digital Identity and Generative AI (Gen AI) take center stage at San Francisco’s Moscone Center New innovations close the gap between in-person and digital commerce experiences SAN FRANCISCO
Sorry but your description is not very clear.
Which specific terminal flow are you going through?
Sure
We're getting the errors when using the
https://docs.stripe.com/terminal/features/collecting-tips/on-receipt#availability
Specifically for Visa Debit cards. I can send many payment intent logs if that's helpful.
We have customers using both flows. But the errrors are ocurring for this flow only.
This is also related to a previous thread by us
#dev-help message
We are experincing increased volume of this kind of error.
Okay now that I know what flow you are following I'm digging into the example charge you shared
That charge was not eligible for overcapture unfortunately
You can see that in the payment_method_details.card_present.overcapture_supported property
Looking at the payment method details it looks like this card did not support either overcapture or incremental capture.
Our docs call out that this is something you can verify before you attempt the capture:
To collect a tip, you must create and confirm a PaymentIntent following the steps outlined in collecting in-person payments. You can verify that a given PaymentIntent is eligible for over-capture by accessing overcapture_supported.
Where do I see that in the events/logs?
Ah I have found it, nvm
Help me understand:
This issue hasn't occured until the past week. And the earlier support threads ended with "It's a card network error"
Is this because something has changed with Visa Debit cards in the past couple weeks? Why is this issue only rising now when we haven't changed our tip flow in months?
Unfortunately I do not know that. The eligibility of a card for over-capture is dependent on what the card networks send back to us and it isn't something you (or I) can control.
Have you guys heard anything from banks, visa, or the like that indicated this change?
It'd be most helpful for communicating to our customers why we can't accept tips on visa-debit right now (until we generate some work around)
What you can do is inspect the card on your end when you make the /confirm request like this one: https://dashboard.stripe.com/logs/req_MRxMeAHHeky5Bd
But I'm looking for any internal doc on changes to Visa debit and overcapture...so far nothing
Sorry I'm a bit confused. What is the difference? Or do you mean we inspect the response from Stripe?
I figured, based on the earlier thread,
Didn't know there was a overcapture_supported field
Haha, I'm the new guy so riding the struggle bus currently
Can you do incremental captures when they don't have overcapture enabled?
Yeah the confirm call is when the payment method is generated so you can inpsect the properties at that time and identify whether or not you can accept on-receipt tipping
No, not for this payment mehtod at least
There's another field for whether or not incremental capture is available too
He means the payment_method_details.card_present.incremental_authorization_supported: false,
That field indicates for this payment method
"incremental_authorization_supported": false,
Jinx
Woof
Alright let's just say this card doesn't accept tipping
And if the customer complains tell them to change tipping to pre card dip
Thanks @wintry grove . You guys have been very helpful
Happy to shed what 💡 I can 🙂
I'm guessing it's related to this visa udpate in may as it said banks will be rolling it out throughout the year.
As more banks roll it out, they're not allowing overcapture on debit cards which would make sense as an overdraft protection of some kind. That's just conjecture tho
I'm wondering if you could inquire about it with Visa