#cherub_docs

1 messages ยท Page 1 of 1 (latest)

kindred rivetBOT
#

๐Ÿ‘‹ 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/1484636833844564029

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

tired sandal
#

Hello! I don't see why this would behave differently with a real card but let me do some digging to be sure...

kindred rivetBOT
haughty bay
#

hello thank you so much! Yes, the test version worked for me but I'm worried if its a real bank flow if it won't work in the popup just because the popup would be in our iframe. I know for security reasons banks usually don't like to load auth flows inside an iframe

hot geode
#

hi there, taking over for jazz as they had to step away. I've never heard of anyone having an issue with this. we designed that test card flow to be as close as possible to the real thing, so if it's working with the test card, I see no reason it wouldn't work with a real card

haughty bay
#

ok i see, that is great to hear thank you!

#

sorry also, one last question

#

i was using the stripe ai and it said that the default behavior of the 3ds popup is a redirect but that is false right? it just closes, and then we can handle the confirm success anyway we want without a redirect?

hot geode
haughty bay
#

ok thank you!

hot geode
#

no problem!

haughty bay
#

so for this line in the doc 'Authorizing the payment simulates successful authentication and redirects you to the specified return URL. '

#

that is not true for the default popup modal

#

only for the manual opt in redirect flow

hot geode
#

correct

haughty bay
#

alright thanks!

hot geode
#

(though I agree that could be more clear, I'll surface that feedback to the docs team)

haughty bay
#

yes for feedback i think the popup section should be in its own section and the rest of the article should be in a seperate section!

#

thank you so much for helping and have a good weekend! you guys might see more of my questions in the dev-help channel lol so i appreciate a lot

hot geode
#

you're welcome, it's what we're here for ๐Ÿ™‚

haughty bay
#

also for another feedback, for the PaymentFormElement beta, I have access to the docs and I think the pregenerated checkout session curl call puts in an outdated version number

#

one second i will show you

#

Stripe-Version: 2020-03-02

#

but then later running it with embeddable payment form, i get errors: "message": "Invalid Stripe API version: 2020-03-02; custom_checkout_payment_form_preview=v1. In order to use ui_mode: custom, you must upgrade to Stripe API version 2025-03-31.basil.

hot geode
#

some of those code blocks are dynamically generated based on the account you're logged in to, so I can't see that Stripe-Version in the curl command. if you can, raise that feedback with your contact at Stripe who entered you into the beta

haughty bay
#

ah i see i didn't realize it was dynamically generated