#mitsu_api

1 messages · Page 1 of 1 (latest)

balmy trailBOT
#

đź‘‹ 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/1438017044066078892

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

#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

tight hornet
#

Hi! Looking into your question.

storm locust
#

I’m still waiting

tight hornet
#

I am still looking into the issue. I will need some time. Thanks!

#

I tested the same with a Standard connected account that had its transfer capability disabled but the transfer was successful.

storm locust
#
  1. So in test mode, can a transfer via the API from the Platform to a Standard Connect account succeed even when capabilities.transfers = inactive, right?
  2. And in live mode, to transfer from the Platform to a Standard Connect account, the Standard account must complete KYC and have capabilities.transfers = active, correct?
tight hornet
#

Yes

storm locust
#
  1. If that’s the case, we’ll check before each call to the transfers API; if it’s inactive, we won’t call the transfers API anymore, right?

  2. In test mode, how can I update “transfers” from “inactive” to “active” for acct_1SKzn3RVvCMeV3II ?

tight hornet
#

If that’s the case, we’ll check before each call to the transfers API; if it’s inactive, we won’t call the transfers API anymore, right?
Are these for live transfers? You will be updated about the connected account's capability status via the account.updated and capability.updated events. This way you don't have to check on the accounts capability each time you want to make a transfer.

#

In test mode, how can I update “transfers” from “inactive” to “active” for acct_1SKzn3RVvCMeV3II ?
You can only request for a capability: https://docs.stripe.com/api/accounts/update#update_account-capabilities-transfers
Each capability is inactive until its requirements are met and verified.

storm locust
#

I think we need to go into the Standard Connect dashboard to make the update, right?

#

acct_1SKzn3RVvCMeV3II is a Standard Connect account connected to the platform acct_1MgeedKSVjwCWErT via OAuth. So how can the platform update information for the Standard account? It should be the Standard account that updates it, right?

tight hornet
#

Yes, Standard connected accounts will need to update any pending information on their own account.

#

It doesn't matter if they are onboarded via Connect Onboarding or OAuth.

storm locust
#

So if we update all the missing information, then capabilities.transfers will be active, right?

tight hornet
#

Yes it should. Are you facing any issues with that?

storm locust
#

I still have a few fields I haven’t been able to update, so "transfers" is currently "inactive".
Could you help update that account so that "transfers" becomes "active"?

#

The goal is: if it’s inactive, I won’t call the transfers API.
So in the test environment, I want to have one active account. capabilities.transfers = active