#barkman_unexpected

1 messages · Page 1 of 1 (latest)

keen gobletBOT
#

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

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

bleak spear
#

👋 hello, give me a moment to catch up on your question

#

but we have many examples of this. — is this a payment example? Could you share with me the PaymentIntent ID?

hazy relic
#

Sure - let me find it

#

pi_3T9o6oRvwRxp7roW1r8gNJyR

#

I did notice it has two payment_intent.request_action events in quick succession - don't know if that might be something strange

bleak spear
#

pi_3T9o6oRvwRxp7roW1r8gNJyR was in payment_intent.requires_action , which means it was waiting for customer's authorization, but the customer did not authorized.

hazy relic
#

The customer claims they did - and I believe were redirected back to our checkout, where we showed them a loading screen until we expired their order ~15 mins later

#

Do the two payment_intent.requires_action events seem odd at all or indicate that anything was amiss?

#

Do certain LPMs have higher failure rates that we should be aware of?

#

I have an example of another PI that has... 4 or 5 payment_intent.requires_action events in quick succession

bleak spear
#

After customers submits the Payment Element, either by selecting the payment method or keying their card details, the payment button that triggers stripe.confirmPayment() [0] should ideally be disabled, so that the customer only "submits" the payment once. In this case, it looks like the customer could submit the payment twice. Either this, or your frontend is calling .confirmPayment() twice.

[0] https://docs.stripe.com/js/payment_intents/confirm_payment

#

Do certain LPMs have higher failure rates that we should be aware of?
No, there isn't a payment method that has a higher likelihood of payment failure than others.

#

Checking why your integration is confirming a single PaymentIntent multiple times would be a good start to investigate the payment flow that your customer goes through

hazy relic
#

I do believe we disable our pay now button after first click/tap - but something to look into. Would this be a potential source of buyers not being able to successfully complete their purchase? As in - does the existance of a second request present possible issues for that PaymentIntent?

bleak spear
#

it really depends on the payment flow built - but if the customer is able to submit payment twice, the second attempt could disrupt the first payment attempt while it tries to redirect the customer to authorized their payment. But we wouldn't be a 100% sure right now because we need to confirm it by stepping through your existing payment flow - this might be something you'd want to do in your staging environment.

#

Finding out why .confirmPayment() can be called more than once in a short period of time would be a good start

hazy relic
#

Hmmm - I think I've been able to recreate with a double-click

#

pi_3TCsOJACdRUFSDIz0RHvqbmh

bleak spear
#

Looks that way - there are two confirmation attempts on pi_3TCsOJACdRUFSDIz0RHvqbmh

hazy relic
#

Managed to get up to 8 on pi_3TCsfMACdRUFSDIz0nwhUbOm

#

Yeeesh

slow canyon
#

sorry to message on here but can someone put me on to staff that can direct me to the right place to report critical bug, as hackerone is blocking my attempts to report

keen gobletBOT
#

@slow canyon looks like you're in the wrong place, this thread is for someone else's question.

Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.

slow canyon
#

yes i know but i cant message in other chat .. well im out of options to report this. good luck and sorry for jumpin in on your question barkman ,

bleak spear
#

@slow canyon please go through #help to start a new conversation thread using the available buttons if you'd like assistance. We'd be happy to look into the issue you'd like to report in a new thread.