avery_error

[hallow glade]

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

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

[hollow sparrow]

Taking a look

Doesn't look like you set the overcapture parameter on the PI: https://dashboard.stripe.com/logs/req_YIXxjJwIUFJSIa

[untold latch]

I believe this is incorrect for our account

"Your business is in the overcapture beta program, which means that all payments implicitly request overcapture. If you want to opt out of overcapture for a given payment, use never with the request_overcapture parameter."

This is directly from the docs

Here is an example of a payment intent that doesn't have that parameter and has over capture: pi_3PRBZQAcqRxm04BK0dsQRIgl

[hollow sparrow]

Yeah, I see that too. Weirdly it's not set on that intent from what I can see. Looking at the actual charge from the previous capture, looks like the card used may not support overcapture: https://dashboard.stripe.com/events/evt_3PRBGaAcqRxm04BK0hA6U8Pw

See payment_method_details[card_present][overcapture_supported] field

[untold latch]

A regular visa card doesn't support overcapture?

This has been happening with multiple cards on this connect account

[hollow sparrow]

Just relaying what I can see internally. Digging deeper

[untold latch]

This can usually happen if they have the incorrect MCC

[hollow sparrow]

OK, for the card used in the original capture/confirmation we did request overcapture but it wasn't honored

[untold latch]

But it seems to be the correct one

Take a look at : pi_3PRBF8AcqRxm04BK1Aame8yc

[hollow sparrow]

What am I checking here?

Support is ultimately determined by the issuer/network. If they don't honor the overcapture, then your integration should handle that accordingly

[untold latch]

Well multiple payments on just this account are giving the same error code with cards that normally honor over capture

[hollow sparrow]

with cards that normally honor over capture
The exact same card? Or same brands/issuers?

Ah, so pi_3PRBF8AcqRxm04BK1Aame8yc is an example of supported overcapture for the same card?

Oh, no it failed there too. Not sure relevance of that ID then

[untold latch]

Correct

[hollow sparrow]

https://dashboard.stripe.com/logs/req_7XTsPoBXiTrnzE

Same issue: we requested overcapture support but it wasn't honored

[untold latch]

https://docs.stripe.com/payments/overcapture

Visa credit cards allow over_capture

Both these cards were Visa

I've never had a problem with a Visa debit card in the over 100k payment intents we do a week

[hollow sparrow]

But you just said it worked for this card in the past and then shared another failed example of overcapture?

[hollow sparrow]

I don't know really. This kind of ask isn't really suited for our team (it's not integration/API shaped). Seems like yes, based on our documentation Visa should be supported but perhaps some card types/issuers don't support it yet?

It's recommended reaching out to your contact at Stripe as they're far better suited to help in this case

[untold latch]

I can reach out to our support manager then

Awesome thank you!

Sorry for being a bother

[hollow sparrow]

Sorry I couldn't help further!