#ed_connect-business-model

1 messages ยท Page 1 of 1 (latest)

timber gobletBOT
#

๐Ÿ‘‹ 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/1405662359443476492

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

#

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

  • ๐Ÿง‘โ€๐Ÿ’ป You must be a developer
  • ๐Ÿ› ๏ธ Your question must be about building a Stripe integration
  • โš™๏ธ Your question must be technical/developer focused
  • โฑ๏ธ You must be available to respond in realtime
  • ๐Ÿ‘ฅ You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.

oblique glacier
#

The problem is that they refunded more than is in their connected account balance.

#

What's the best practice here to manage this

#

Snufkin - this is exactly a best practice question - why am I being redirected to support?

#

@dire nest

dire nest
#

Are you coding solutions with the Stripe APIs?

oblique glacier
#

Yes

dire nest
#

What the exact API calls you are making that aren't working like you expect?

oblique glacier
#

But the limitations are fierce. stripe.Refund.create

dire nest
#

We don't have general "best practice" recommendations

#

An account cannot refund more than they have

oblique glacier
#

The recipient of this transfer does not have sufficient funds in their Stripe balance to reverse this amount.

dire nest
#

You can modify the payout schedule so Connected Accounts keep more money in their stripe balance

oblique glacier
#

OK sure, but they want to be able to refund in a timely manner.

dire nest
#

What is the problem with the API calls

oblique glacier
#

So if we reverse a payout, it takes 2-3 business days and then they can create a refund.

dire nest
#

This still doesn't sound like a developer question

#

I can't help with payout reversal timing

#

You can always tranfser more money from the Platform to a Connected Account

#

All of this is more "business model" questions that aren't what we focus on in this server

oblique glacier
#

Hmm @dire nest in my head it completely is: I cannot come up with a way to satisfy the connected accounts' expectations with the existing APIs and I'm looking for guidance on how to achieve this.

Even a higher stripe balance will not solve this problem. At some point, the higher balance runs out, and we need to be able to pull money from their business account.

I'm just seeking advice on what the reasonable standard across implementations is.

#

There is no way we are the only developers running into this issue - and I'm seeking advice on finding a reasonable architecture.

dire nest
#

None of this has to do directly with coding API integrations. It's all about the restrictions of moving money.

#

As such I cannot offer any help and you need to talk to Support

oblique glacier
#

Can you give me some example questions of what would be "best practices" that I can seek advice on then? To me, this seemed precisely best practices convo

dire nest
#

Can you give me some example questions of what would be "best practices" that I can seek advice on then?

This is what I said I cannot offer

oblique glacier
#

So I can improve my own triaging

dire nest
#

Which is why you are in the wrong place and should reach out to Support

oblique glacier
#

Hmm you're not understanding me

#

IF this channel is called "Best practices", what sort of questions are reasonable to ask about here, so I can improve my own triaging?

dire nest
#

Best practices for constructing API calls, structuring your integration (e.g. Payment Element) to avoid rate limits, what parameters to specify when creating subscriptions to get the expected behavior

#

These are the kinds of questions we can help with