frida-shtise_best-practices

[scarlet pasture]

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

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

[rugged skiff]

👋 Hi there!

Yes, using the organisation key as described in the documentation you linked would probably be the simplest

[muted vortex]

The documentation also says that there's no publishable key for the organization, so clients have to use the publishable keys that are available for the separate accounts.

So does that mean the clients also need logic on their side to switch between the PKs?

We have created our own checkout flow, but clients use some Stripe elements like 3D secure or call Stripe directly for external bank account tokens.

[rugged skiff]

If you just have a single platform with multiple connected accounts, then you don't need to use organisation keys

If you're using Stripe.js on the client-side, you can use the publishable key of your platform, but pass in the appropriate stripeAccount value when initialising Stripe

[muted vortex]

No, we need multiple platform accounts, and both will have connected accounts 🙂

[rugged skiff]

Then assuming you want the same client-side code to work with both platforms, then you would need to use the correct publishable key for the platform, as you mentioned

[muted vortex]

Okay, thanks for the verification 👍