#Cellar Door

1 messages · Page 1 of 1 (latest)

sleek glacierBOT
dense escarp
#

Hi, in general.. that is correct. These two are separate in that Connect allows you to process payments and transfer funds between the accounts.

eager thorn
#

Correct - and reading through the docs Treasury requires a connect account as well?

dense escarp
eager thorn
#

So a high level overview of what we're building is we'll have a platform where users can pay for services to the platform and a cut will go to providers. This seems like clear cut connect usage. However the goal is to allow users to have an account they can put funds into and pay out to the platform through. Would treasury be necessary for that?

#

Not sure if it's possible to have platform customers with an account balance and use that account balance to process payments or if that's where Treasury comes in.

dense escarp
#

So a high level overview of what we're building is we'll have a platform where users can pay for services to the platform and a cut will go to providers. This seems like clear cut connect usage.

That is correct. Your Platform account will have Connected account, like a marketplace, https://stripe.com/connect where end users pay for services. You can use destination charges, https://stripe.com/docs/connect/charges and process payments.

However the goal is to allow users to have an account they can put funds into and pay out to the platform through. Would treasury be necessary for that?

I do not think so from this limited explanation, but I would read more on this: https://stripe.com/docs/treasury#treasury-account-architecture

eager thorn
#

Looking at that doc though the use of treasury discussed is for the marketplace service providers. Is there a way for us to store value on a customer's account then use that account to pay through connect to the marketplace service providers with destination charges?

#

Essentially the marketplace customer could load their account with funds, then use those funds to pay the platform for services and the platform would then do a destination charge to the service provider and platform retain a portion of the charge

#

All that looks to be standard connect other than the customer able to load their account with funds

#

Otherwise what we'd do is create a treasury account for the platform and use that to store the funds on the customer's behalf then move money into the connected payment account to then process the payments out to the connected service provider accounts who may/may-not have treasury accounts

dense escarp
#

This seems like a unique set up so I had to read the above a few times to confirm my understanding.

sleek glacierBOT
midnight mantle
#

👋 taking over here

#

store value on a customer's account then use that account to pay through connect to the marketplace service providers with destination charges?
This doesn't sound like what Treasury offers. Treasury is to provide the financial account attached to a Connected Account rather than Customer

#

create a treasury account for the platform and use that to store the funds on the customer's behalf then move money into the connected payment account to then process the payments out to the connected service provider accounts who may/may-not have treasury accounts
This could work yes, but you will still need a way to charge your customer to store their fund on their behalf.