#ricardones_77

1 messages · Page 1 of 1 (latest)

sly magnetBOT
novel sierra
#

Hi 👋

We don't really do "compehensive lists of technical steps" here. This server is designed to unblock developers who have specific errors in their integrations with Stripe APIs.

#

That being said, I can provide some documentation for this scenario

#

For External Accounts, this would be created by the Connected Account during their onboarding

unborn raven
#

Hi. Thanks for replying.
Yes, that’s Stripe Connect for the connected account (my B2B clientes). It’s been frustrating to implement this backend. Couldn’t find anything in your repos nor in the API documentation. I’ll continue to try and get back when I have more specific errors. It will be a try-and-error journey 😔

novel sierra
#

Have you created a Connected Account yet? That's a good place to start (in Test mode)

#

Next, create an account of that type in Test mode and walk through the onboarding process

unborn raven
#

In my list above, use case 1 is direct charges while use case 2 is destination changes.
The type of accounts is CUSTOM.

novel sierra
#

You do not want to be mixing charge types

unborn raven
#

I won’t use Stripe Connect Onboard because our platform already collect all the info you need.

novel sierra
#

that is a very bad idea

#

Nothing about use case 2 implies destination charges

unborn raven
#

Sorry, use case 3

novel sierra
#

You can create subscriptions for your connected accounts using Direct charges

#

You should really decide where the Customer & Payment records need to live (Platform or Connected Account) and start there. But if you are using Custom accounts you should only use Destination or Separate Charge and Transfers

#

Also be aware that Custom accounts require the most engineering on your end

unborn raven
#

Use case 1: a simple subscription between our platform and the B2B customer (our customer)
Use case 2: a subscription between the b2b customer and their customers. This is where direct charges comes in between their clientes and the B2B client (with an external account)
Use case 3: the b2b customer can sell ad-hoc stuff in our platform, and we will take a percentage of the sale to the platform. This is a destination charge, charged at the time of the sale

#

Am I missing something?

novel sierra
#

You cannot create a Subscription for the account in use case 1

#

You can only create a Subscription for a Customer object

#

You can create a Customer object that represents that Connect Account

#

But that isn't a direct charge because Connect isn't invovled at all

unborn raven
#

At the time of the onboarding, I will create a customer object to represent the subscription between us and the customer, plus a connected account to allow them to have subscriptions between them and their customers

novel sierra
#

Okay so that rules out the Direct Charges which is good

#

Since that's a subscription that is only tangentially related to Stripe Connect (from our perspective).

unborn raven
#

Ok. Let me continue and will create a new thread if I come across a roadblock. Thanks for your replies here. 👍🏼