#adriana_unexpected
wet estuaryBOT
👋 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/1458533936593506507
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
harsh hawk
hi there!
Can you paste in the link of the docs page you're referencing to make sure I know exactly what you're talking about?
still smelt
harsh hawk
Okay that's great. You said you were using Elements; could you be more specific about your integration, as that covers some ground? Are you using the Payment Element, or something else? If I use the 4000000000001208 card in the Payment Element I get a challenge like this:
still smelt
Yes, I'm using Payment Element when I use this card 4000000000001208 I don't see the challenge
harsh hawk
Do you see any stripe.js errors in the browser console? Any failing requests in the devtools network tab?
is your checkout page publicly accessible or can you provide credentials that I can use to inspect it?
harsh hawk
Also, do you get the same behavior with the card 4000000000003725?
still smelt
yes, I try both
still smelt
I don't think this is possible.
harsh hawk
Wait a minute - are you actually submitting the form? The inputs in the element aren't cleared, which shouldn't happen after successful submission
what's your Stripe account id?
I want to check to see if there is actually a successful PaymentIntent for the submission I just made on your site
harsh hawk
ah, I must have pasted the card details back in
still smelt
I'm using connect and this is the connected account id: acct_1CzUAeLzhyuJWJpK
harsh hawk
okay it seems to be because you're creating confirmation tokens
still smelt
yep
harsh hawk
So it is likely a gap with the test card
I also don't get the captcha challenge when creating a confirmation token with the Payment Element
still smelt
ok, so... maybe in production is not working?
harsh hawk
I'm sorry, I don't quite understand the question - could you rephrase that?
still smelt
it is only happen on test mode?
harsh hawk
Exactly; the test cards aren't a perfect representation of livemode behavior; they have to be programmed to behave in certain ways. Confirmation Tokens are a more recent feature and I am guessing that we just didn't update the test card to handle that case
still smelt
ok ok
harsh hawk
Are you confirming PaymentIntents serverside with the confirmation token, I assume?
still smelt
yes, it's correct
harsh hawk
I want to see if we trigger the captcha if you confirm client-side with a confirmation token, which will take a few minutes, but otherwise I think I'll just have to flag this and ask to have the test card behavior updated. If you want to just see how it looks, you can confirm a PaymentIntent directly on the client and use the test card and you'll see the captcha
still smelt
I can wait 🙂
harsh hawk
okay, yeah, that doesn't trigger captcha either. I'll have to take this up. If you want to keep updated, you can submit a support ticket and we can update you when we've fixed this
wet estuaryBOT
Hello @still smelt, we have sent you a direct message, please check it at https://discord.com/channels/@me/1436119793181655061
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.