#OptimalSurprise-connect
lament shadow
@floral sorrel hi! can you expand on that a little?
Generally there are three parties : you(the platform), your connected accounts who receive money, and the end-customers who pay money. Subscriptions are for end-customers. Just to clear up the terminology.
floral sorrel
Ah ok, so what I'm trying to do is have our vendors pay us $x per month
on top of some application fees
i've added application fees in the end customer subscription so that's fine
i'm just looking to add the $x per month for the vendor now
lament shadow
ah ok
well there's really only three options :
- increase the application fee you take to get that money, in a different way.
- potentially, debit the connected account for some extra amount occasionally (https://stripe.com/docs/connect/account-debits)
- create a Customer object on your platform, collect payment information from the person running the vendor account, and charge that customer through regular Stripe payments, and then in your database, connect that Customer
cus_xxxand Connected Accountacct_xxxinto one entity for bookkeeping(there's no link on the Stripe side)
floral sorrel
ok great, i'll most probably go with the 3rd approach
lament shadow
yes that one is common enough
floral sorrel
is there a way to use the information from the vendor's financial information and save this so they can checkout as a regular customer?
lament shadow
there is not, no, you have to collect the information twice(once for payouts, once for payin)
floral sorrel
ah ok
lament shadow
as I mentioned, on Stripe's side there is really no link here. It's a very common use case and we might ned up redesigning the API to make this more straightforward, but for the forseeable, this is how it works