#yoyosaur_error

1 messages ¡ Page 1 of 1 (latest)

arctic capeBOT
novel rivetBOT
#

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.

arctic capeBOT
#

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

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

astral yew
#

Starting second thread, had to step away for some on-call stuff

unkempt wigeon
astral yew
#

Sure, the failed one is:
pi_3PT41YAcqRxm04BK1VXX74xi
The succesful one is:
pi_3PT43XAcqRxm04BK1hSIKBm6

#

On the succesful one, you can see we update the payment intent with the new amount from the tip

image.png
unkempt wigeon
astral yew
#

But in the failed one, the request to capture fails.

image.png
#

Thanks, let me clarify:
We collect the tips through the reader via a UI flow. So we aren't using the on-receipt tips where it's manually entered by an employee.

#

However we are making that update call, which is the on-receipt flow per the docs.

unkempt wigeon
#

The successful capture was for the same amount as the PaymentIntent amount
https://dashboard.stripe.com/logs/req_rD6RcZ67EqFYNw -> amount = 1136, capture amount = 1136

The failed capture one was for more amount than the PaymentIntent amount
https://dashboard.stripe.com/logs/req_rrQwoJv4DGTLQP -> amount = 1036, capture amount = 1136

Over-capture is only allowed for eligible MCCs
https://docs.stripe.com/terminal/features/collecting-tips/on-receipt#limits
https://docs.stripe.com/terminal/features/collecting-tips/on-receipt#availability

Are you sure you selected the correct MCC?

astral yew
#

Let me check with this specific customer their MCC is setup corect.

unkempt wigeon
#

Ah I think the MCCs are fine

astral yew
#

Yes, the locations dealing with this are Eating places and restaurants

unkempt wigeon
#

The payment method likely doesn't support over-capture

astral yew
#

Is this because it's Visa Debit?

#

We've recently had the exact same flow support over-capture for a Mastercard credit card

unkempt wigeon
#

If you look at the charge object, ch_3PT41YAcqRxm04BK119JCnWH

and check payment_method_details.card_present.overcapture_supported property then it says false

So most likely, yeah.. It isn't supported with that specific payment method.

astral yew
#

Apologies if this is a remedial question, but is that something on our end that we can remediate, or is this just a Visa Debit issue?

unkempt wigeon
#

I don't think its something you can remediate. I'm pretty sure this is something the card network decides...

#

You could look at charge.payment_method_details.card_present.overcapture_supported parameter before you redirect to tipping UI to see if its even supported.

astral yew
#

Alright, thanks. Glad to know stripes working perfectly, sad to know there's work on our end haha