#Muhammad-connect
1 messages · Page 1 of 1 (latest)
hi! you probably want to read the docs for Connect and find a fund flow that works for your use case.
https://stripe.com/docs/connect/
https://stripe.com/docs/connect/collect-then-transfer-guide or https://stripe.com/docs/connect/enable-payment-acceptance-guide
https://stripe.com/docs/connect/charges#types
I am using stripe connect standard for tenants. (It's working fine.)
Now I want to charge to tenant owner and all of this should be happening on master account. (It's separate from tenant<connect account>)(Like I don't want to cut something from every charge of connect account or something like mentioned in documentation)
so just a regular payment without Connect?
I think yes
For that do you think i have to create a customer for each tenant owner on master account right?
then it's really just the same overall code you have but you would set things up to for example, not use the Stripe-Account header in the requests you make.
And yes, the payment information(like the PaymentMethods or Customer objects) would have to be created on your platform account
if their card information only exists on the Standard accounts today you'd have to recollect it from the end-customer, it can't be copied 'up' to your platform account.
and same webook will be used right that is being used for stripe connect?
no, it uses a different endpoint, there are two types (when setting up an endpoint for this in the dashboard you would not tick the box for the endpoint to listen to Connect events)
Do you think it's best to collect the charges from tenant owner directly without connect?
(I am not sure what I have to do if I want to do the same thing via connect)
I'm unsure, you said that's what you want to do, so I assume you have a business/technical reason for looking into making this change?
So stripe connect account have to make a monthly payment to master stripe account.
What's the best way to capture that payment?
oh, I see. Then usually yes, you create a Customer object on the platform, collect some payment information from the connected account holder, and then charge that as if it was a regular customer on your platform account(and then you "tie together" in your own logic/databases that the connected account and that Customer are the same person).
ok thanks