#caitlin-short_error
burnt summitBOT
👋 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/1313270411173040222
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
true merlin
Hi there
I can't help with onboarding issues in this channel. I recommend reaching out to our Support team about this: https://support.stripe.com/contact/
small nimbus
ok thank you
I have another question regarding stripe issuing. Should I create a new thread?
true merlin
You can ask it here 🙂
small nimbus
awesome!
I wanted to ask about something that is creating a lot of duplicate work for our productions. We have production companies using our platform who have multiple productions/project running every month. The entity in a lot of cases is the same but we need to maintain different issuing balances for each project since the budgets are different. Is there any way the company can do the entity verification/onboarding once, instead of having to do it for every project? It's very tedious, and more importantly needs to be done by executives (due to confidential info like SSN) who are not very accessible.
This is in regards to Stripe Issuing + Connect
true merlin
Gotcha. Which connected account type are you working with?
small nimbus
I am not sure what you mean?
We are using connected accounts to issue cards
Not with treasury
true merlin
Right, understood. With Connect, you will either create accounts of a specific type (e.g. Express, Standard, Custom) or use controller properties: https://docs.stripe.com/connect/migrate-to-controller-properties
small nimbus
They create separate proejcts in our system and then right now we just create a new conected acccount for each project and then this way there is complete separate but they have to go through onboarding several times if they have a lot of separate projects.
Now for some productions this works as their entity information is different per production.
But others they have the same entity details
true merlin
Do you know which one you use?
small nimbus
I beleive i sent this
controller: {
stripe_dashboard: {
type: 'none',
},
fees: {
payer: 'application',
},
losses: {
payments: 'application',
},
requirement_collection: 'application',
},
followed these guides
true merlin
Okay, got it!
No, it's not currently possible to re-use the same legal entity information across custom accounts automatically. The connected accounts will have to go through onboarding every time
I suspect you're using Stripe-hosted onboarding?
true merlin
What do you mean by separation?
small nimbus
so that I can have separate issuing balances, card holders but for one conencted account
true merlin
Ah, gotcha. No, this isn't possible
A connected account will have a single Issuing balance (which is different from their main balance) but cannot have multiple Issuing balances
small nimbus
Ok I see.
- Can I set notifications per connected account for low balance?
- How can we as a platform add funds to an issuing balance for a connected account?
true merlin
I'll answer # 2 first: you can "top up" a connected account's Issuing balance through a few different mechanisms outlined here: https://docs.stripe.com/issuing/connect/funding
For # 1, not exactly. You will have to periodically retrieve a connected account's balance since we don't emit events for negative transactions: https://docs.stripe.com/connect/account-balances#check-connected-account-balance
small nimbus
Ok thank you.
Sorry for all the questions - woudl this potentially solve my issues regarding the same entity onboarding
true merlin
I'm not sure if this would allow a v2 Account to hold multiple Issuing balances
burnt summitBOT
true merlin
You can sign up for private preview opt in if you're interested in testing out the new Account object and providing feedback on how this fits/doesn't fit your use case