#yoann_code
1 messages ยท Page 1 of 1 (latest)
๐ 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/1475872535181791292
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
I don't really understand what you're describing, the modal/redirect can only happen client side
Hi, let me try to clarify what I'm experiencing:
Essentially when I'm confirming a payment intent with a payment method ID, and return to the frontend the requiredAction the stripe library will open a new 3DS authentication page with broken buttons. But if I confirm a payment intent with a confirmation token (generated by the payment element on a new payment method), and follow the exact same code path, I get a nicely formatted modal opening the 3ds authentication page with functioning buttons.
the stripe library will open a new 3DS authentication page with broken buttons
Can you share an example test payment intent ID you tried this with, and a screenshot/recording of what you observe?
In this video, I'm trying to figure out how to consistently render 3DS authentication models in my application. I have a payment method that already exists on Stripe, and I want users to be able to select it for upgrades. To validate this payment method, I need to confirm the payment intent with a hold on the credit card, but I'm encountering is...
I can also record a little walkthrough of my code if it helps but the only difference in the implementation is on the Stripe Elements form submission and the createConfirmation token. Both are called on the "new payment method" flow and skipped on the "existing payment method" flow
hi there, taking over for synthrider as they had to step away. can you paste the Payment Intent ID where you experience the failing redirect flow into the chat here? also an example Payment Intent ID that causes the modal to compare against would be helpful
Thanks, here are two examples:
Failing: pi_3T4NUmJQrM0pfH8G2W3h8nXk
Succeeding: pi_3T4NYyJQrM0pfH8G1sXLQt7P
thanks, looking into this now
I noticed you're using two different test card numbers here, just to eliminate this as a possible cause, can you try the same card number for both flows and see if you have the same results?
Yes, absolutely.
One is 3DS Auth -> insufficient fund, the other one is just 3DS Auth -> validated
Displaying modal properly: pi_3T4NmNJQrM0pfH8G2GFkrsjq
Displaying 3DS auth on a different page: pi_3T4NnmJQrM0pfH8G06XAmVu2
thanks, I'm going to try to reproduce this myself with my test integration, one moment
Much appreciated, thank you
hi there, thanks for waiting. so the reason you're seeing different behavior here is that Stripe makes different assumptions about your flow based on whether you're using Confirmation Tokens or passing a Payment Method when you confirm. if you look at the response to your confirm requests, you'll notice that the next_action value is different. the modal one has a type of use_stripe_sdk, the redirect one has a type of redirect_to_url
the solution when you're passing a payment method is to use the use_stripe_sdk: true parameter https://docs.stripe.com/api/payment_intents/confirm#confirm_payment_intent-use_stripe_sdk. this will make next_action for that PI use_stripe_sdk and you should get the modal flow