zenoitulos | Stripe Developers | Page 1

plush valeBOT Jan 5, 2023, 4:15 PM

#

reef ravine Jan 5, 2023, 4:15 PM

#

hi! there's really no reason to be using stripe.js v2 today.

#

so you'd just use v3 really. Did you have a specific reason for thinking you need to use v2?

stiff bane Jan 5, 2023, 4:16 PM

#

I know.. we really would like to keep our UI as it is, for the short term. Eg not use the Elements...

#

that is the reason I am looking into V2

reef ravine Jan 5, 2023, 4:17 PM

#

I'd highly suggest using Elements.

but then yes, AFAIK v2 does not support Stripe-Account. Instead you'd have to use the API key of the connect account(https://stripe.com/docs/connect/authentication#api-keys). Let me double check though.

stiff bane Jan 5, 2023, 4:22 PM

#

ok, let me try that then...

reef ravine Jan 5, 2023, 4:25 PM

#

yeah I'm not seeing any way to pass that, if you're using that library you'd have to use the legacy Connect approach of using the API key. I'll emphasize again this is not recommended!

There's also a way to use stripe.js v3 but without Elements for the inputs. You need to contact our support/sales teams to get access to that though.

stiff bane Jan 5, 2023, 4:27 PM

#

oh..nice

#

so for the v2... is there a timeline for this to go "away"?

#

just curious..

reef ravine Jan 5, 2023, 4:32 PM

#

no timeline. But in ~~2022~~ 2023 you should not be building a new integration using it.

As we would see it, the options would be

use Elements (99% of Stripe merchants)
if you are an advanced/larger/multiprocessor merchant and understand the PCI implications of building your own card inputs, you can work with your Stripe account manager etc to get access to that "v3 without Elements" flow I referenced.

#zenoitulos