#mike-j_api

1 messages ¡ Page 1 of 1 (latest)

grizzled matrixBOT
#

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

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

chilly ledge
#

I'm going to have to apologise if I sound like I don't know what's going on. It's true. The person who originally set up the oauth process is no longer here and I'm trying to catch up when our users tell me something's behaving differently.

#

I think another problem is that the new "standard account" has connected to our primary stripe account, and it would normally connect to a new stripe account with the same name. I've not worked out how that's identified though.

terse glen
#

Hi, I'm reviewing this right now!

chilly ledge
#

I think I might see, but it's going to be awkward to explain. I think we start with creating a new stripe account manually. (acct_1DiIeEL8Wt2wSxsO). We would then expect our api to create the standard account against that manual stripe account, but it created a brand new one. Probably because our backend needs to know the account id of the manual account. As it's missing, we get a new unconnected standard account.

#

Does that make sense?

terse glen
#

For the two account IDs that you provided in your original question, I can see that they were set up in two different ways - the first with OAuth and the second as a Standard account. Both accounts are properly connected to the platform account.

I'm trying to better understand your specific error. Can you share with me a specific failing transfer or other failing request?

chilly ledge
#

Yes, that's true. I was using the old oauth one as an example, because the new one's behaving differently. Let me see if I can find better examples...

terse glen
#

These accounts should be fine to examine. You mentioned "Transfers aren't working either". What is the exact problem that isn't working? For example, a failed transfer or other request, not seeing something in your dashboard, etc. If you can share a specific transfer or request ID I can look into that specifically.

chilly ledge
#

OK, I think I see the issue. Let me run through the process:

  1. We create a new account manually (see acct_1GIFhDD2WewLSOc4)
  2. We connect using oauth and it would connect acct_1GIFhDD2WewLSOc4 to our primary stripe account.

Now:

  1. We create a new account manually (see acct_1DiIeEL8Wt2wSxsO)
  2. We connect using express connect and it creates a new account acct_1Rw3WQIPtSQoa6CP connected to our primary account.e
#

So either it's our backend needs the account id so that it doesn't create a new one, or our users had previously chosen the account to connect, but aren't getting the option to do that any more.

terse glen
#

It looks like you are mixing the legacy OAuth account creation flow with the modern API account creation flow.

This is the creation request for acct_1Rw3WQIPtSQoa6CP
https://dashboard.stripe.com/logs/req_Otvi1xoR6HnVgU

This is the correct approach using our current recommendations. No account needs to be created before this, and you don't need to use the OAuth flow at all. If you are trying to connect to an existing standalone account, then using this account creation API is not appropriate.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

Other than the onboarding sequence, is there something that is not working as you would expect, such as the transfers, creating payments, etc.?

chilly ledge
#

Sorry - I'm moving us away from oauth onto the new flow. It's just the new flow is behaving differently. That's the only reason I'm using oauth as an example of what used to happen.

terse glen
#

Got it. If you can provide a specific example of a request that is failing, then we can investigate the specifics and help clarify further.

chilly ledge
#

I'm not being awkward, but I don't have an example of a request that they say has failed. So, I'm just trying to understand the nuances of the options that may or may not be available.

Could you clarify this:

We would normally create a standalone account, set it up as we like, and connect it to our primary account with an oauth api call.

Now we're not using oauth to connect standalone accounts, are we better off:

  1. Using a different api call that does support that operation (if so, what?)
  2. Create the standalone account manually, connect it to the primary account manually, then just copy/paste the account id into our database via a new gui?
  3. Something else?

In an ideal world, we would move all our standalone accounts to express accounts, but unless there's a streamlined way to achieve that, we're not ready.

terse glen
#

Using the API to create accounts is the recommended way, so it's great that you're moving to it! This doc explains the entire flow:
https://docs.stripe.com/connect/standard-accounts#create-account

You should not create a new standalone account via the dashboard first, as it will not be possible to connect that account to the platform with this flow.

grizzled matrixBOT
chilly ledge
#

Ok, well, atleast knowing it's not possible means I can explorer other options without wondering if I've missed something. Thanks.

#

New person joining for a second opinion, or this is a shift change?

rotund bough
#

Hi, yes it is.

chilly ledge
#

OK, so just in case it does turn out to be an incredibly simple conversion process, is there a way to convert our collection of standalone accounts to express accounts?

rotund bough
#

That is not currently supported, no.

chilly ledge
#

OK, so there's no built in way to do it. What would a not-built-in way look like? Would we have to:

  • Duplicate each standalone account as a new express account
  • Transfer funds etc from the old account to the new account

Anything else we would need to do as part of that? Or are we truly stuck as we are?

#

Actually, don't worry about it. The reason we use the standalone accounts is because the owner of each account gets a more detailed view than they would as an express account, and we don't yet have the reports to cover the gaps. By the time we manage that, you might have a way to do it. We're a long way off though.