#jz-1_docs

1 messages · Page 1 of 1 (latest)

primal vergeBOT
#

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

📝 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.

toxic sinew
#

Hello 👋

If your Account is already a Connect Platform, it cannot also be the same account that publishes Stripe Apps.

#

This is a hard requirement for developing Stripe Apps, even in Test mode.

#

I have created a separate Stripe Account exclusively for developing Stripe Apps myself.

cloud mica
#

hi @toxic sinew - I see. is the difference exclusively in the API environment vars or is there a lot more complications to ensure 2 stripe developer accounts do not interfere

#

i.e. - our connect platform already has both webhook and api querying logic, will we run into complications if we make them point to the exact endpoints etc?

toxic sinew
#

It's more complicated. If you wish your existing Account to be enabled as a Stripe Apps developer, you will need to write in to Support and we will have to run some config updates manually

#

It's a fundamentally different permissions structure internally and they don't play nice together

cloud mica
#

I see, yeah we have a support ticket going for recommended approach but we have not heard back on a concrete answer

From a development and stability best practice perspective, is it easier to just have 2 stripe accounts - 1 for connect and 1 for stripe app?

toxic sinew
#

That's what I have done for my test integrations

#

But I'm not operating a real business here so I don't have the same constraints

#

BUT you can connect multiple stand-alone Stripe Accounts using Organizations

#

So that might avoid some of the pain points with managing multiple separate accounts

cloud mica
#

I see, how could we get concrete production grade recommendations on this topic? seems like email support is not super helpful

#

interesting did not see organizations before, we thought that was irrelevant for integration purposes

toxic sinew
#

they can take a while but that is still the best option. On this server, we focus on very specific integration coding questions so we aren't the best for business guidance.

cloud mica
#

got it i see thank you!

primal vergeBOT
modest sorrel
#

hello! fyi i'm taking over this thread. it'll be open for a bit longer in case you have more technical questions you need support with!

cloud mica
#

hi @modest sorrel - yeah really trying to just get the most amount of clarity

it seems like we need to use 2 stripe accounts but we're not sure what kinds of issues we may run into in production

#

would you be able to help clarify what that implicates in terms of webhooks, auth, permissions, etc?

#

e.g. it seems error prone if 2 stripe accounts (one for connect and one for stripe app) connect to the same webhook destination