dedaldino-_api

[graceful rock]

👋 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/1313906568525254749

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[manic glen]

Hi 👋 can you elaborate on what kind of flow you're trying to build?

Setup Intents create Payment Methods, so I'm a little unclear what you're referring to when you're asking about using Sources with Setup Intents.

[oak ice]

Thanks! Let me summarize:

We want to integrate two products, allowing people to provide card information once but purchase two different products with two different publishable keys, Stripe v2 client library allows us to set the publishable dynamically (Product A collects card information using Sources), however Stripe v3 does not allow (Product B collects card information using Payment Methods). What we're trying to achieve is: upgrading Product A to Payment Methods and making use of Stripe Connect to clone saved Payment Methods would require more time, we want to create Sources for Product B and create a Subscription, meaning Sources and Payment Methods will coexist on Product B.

Let me know if you need more info.

[tranquil socket]

Hello! I'm taking over and catching up...

I'm not sure I follow. Why are you using two publishable keys? Is your intent to have your customer provide their payment information twice, once for each publishable key?

[oak ice]

two publishable keys because we have two different Stripe accounts, I intend to have my customer provide their payment information once, then create Sources for each publishable key.

[tranquil socket]

That's not possible without using Connect.

You should connect those two accounts using Connect, collect the payment info on one account, then clone it to the other as you mentioned above.

[oak ice]

I was able to create Sources and Setup Intents and attach them to a customer (Product B)

[tranquil socket]

Using Stripe.js v2?

[oak ice]

yes

[tranquil socket]

That is very much not recommended. Stripe.js v2 is very old at this point, and should be avoided if at all possible.

[unborn meteor]

The work to move off of v2 is underway, however we currently are not able to move off of v2 for one of our projects as we have an external vendor that is requiring us to continue to use that version

We are presently scoping the work it would take to move off of it, however that would be a significantly larger lift (as far as we can tell)