#george
1 messages · Page 1 of 1 (latest)
Hi 👋 I'm not the most familiar with React, but nothing is readily jumping out at me. Is it safe to assume that SECRET actually contains your publishable key in your real code?
Yes, the same issue is happening even on our real app and also the codesandbox, when using a valid SECRET
Just noting that the sandbox also uses v2 & v3 like our app to properly reproduce our error
Is the error only present when V2 is included?
From my tests it seems like that
It's pretty clear that having both versions should work though:
If you need to use both versions of Stripe.js for some period of time, they can be loaded and used on the same page.
I suspect that was published around the time v3 was released, but I'm not sure if something has changed since then that makes that statement not 100% true anymore since v3 has been out for quite a while now. Will you continue to need to run v2 and v3 side-by-side, or are you planning to replace the v2 components with v3 flows?
Updating/replacing v2 does not fit our timeline, so we need v2 & v3 side by side
Oh, I just noticed that document is flagged as deprecated.
My suggestion would be to focus on replacing v2 rather than putting in the effort to build an integration that runs them side by side.