sleepyhead_error

[graceful torrent]

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

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

[tardy spear]

The form was a bit limited. Basically I am wondering how to best handle transactions in requires_capture state. We have modified our code to check if the form submit is disabled to ensure client will not use keyboard to submit form. But in the case there are other sources of this occuring, any generic best practice methods to handle this?

[odd breach]

Do you have a pi_xxx? Sounds like you're just using an auth/capture flow and the intent requires capturing: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method#capture-funds

[tardy spear]

Sorry I was a bit unclear. This is working for us. Just occasionally a client is able to execute confirmCardPayment() twice

resulting in that state. I think our new code which will check if submit button is disabled should do the trick. But wanted to see if there are any other best practices to handle this

(we enable the form submit after retriveing an error from the stripe api)

[odd breach]

Unclear how confirming twice would transition an intent to requires_capture, but yes you should prevent multiple submissions by disabling the submission handler

If you can share a specific example or some code I can maybe offer some beyond that, but right now I have little context

[tardy spear]

it is a bit hard to debug as it is client code, but i was able to replicate it by executing confirmCardPayment() twice

[odd breach]

Again, an example pi_xxx will help me understand the issue

[tardy spear]

pi_3pfMlbJmcOS4ZTnM1QgyBEFU

[odd breach]

Hmm, seems like an invalid ID

[tardy spear]

it is from one of our Stripe Connect accounts

let me check

[odd breach]

Can't find it internally

[tardy spear]

I'm able to find it

it has state cancelled if that matters

[odd breach]

Shouldn't no

[tardy spear]

https://dashboard.stripe.com/acct_1INZc7JmcOS4ZTnM/payments/pi_3PfMlbJmcOS4ZTnM1QgyBEFU

[odd breach]

Has this been deleted or something? I cannot view that or find it internally

[tardy spear]

the URL is available for me. Looks like it was refunded if that makes a difference

[odd breach]

Should not no. Any other examples?

[tardy spear]

No that is the only example I have

connecte to this charge ch_3PfMlbJmcOS4ZTnM1Z4V4Mpp

[odd breach]

OK, the intent ID is pi_3PfMlbJmcOS4ZTnM1QgyBEFU

Note the different characters

OK, timeline:

• intent creation with capture_method: 'manual' into a requires_payment_method state here: https://dashboard.stripe.com/logs/req_zpCx4yJ0DHNnAX
• initial confirmation attempt succeeds, transitions to requires_capture: https://dashboard.stripe.com/logs/req_QvxZTTlAitQ3PD
• 2nd confirmation attempt errors rightfully as intent is already confirmed, so remains in requires_capture: https://dashboard.stripe.com/logs/req_lj1WJRRUYuhNbi

Help me understand what is unexpected?