#brianscott - Subscription
1 messages · Page 1 of 1 (latest)
HI 👋
With destination charges all the Stripe records exist on the Platform account so the connect account cannot make changes to them.
Thanks!
When creating charges and subscriptions on connected account using the cloned customer method, does the connected account have the ability to make changes to the customer and subscriptions?
It all depends on how the charges and subscriptions are created.
If you use direct charges (Standard Connect only) they can modify those records as they exist on the connect account. For Destination or Separate Charges & Transfers the charges and customers belong to the platform and cannot be modified by the connect account.
https://stripe.com/docs/connect/accounts
https://stripe.com/docs/connect/charges
What are you actually trying to accomplish?
I want a customer and all their payment_methods to "belong" to the platform, and have connected accounts be able to cancel subscriptions, but not able to change the subscription amount, interval, etc
or change the customer
That sounds like a cloning situation but the cloned records will belong to connect account
But the connected account could edit the subscription details, no?
If the subscription is created on the connect account, yes
but if it's created on the platform, then the connected account cannot cancel it? there's no way to scope that, unless I scope that behavior through some bespoke code on my end?
The bespoke code approach is the common integration.
I feel like with the bespoke code approach I can choose either destination charges on_behalf_of a connected account, OR cloning the customer onto the connected account. How does cloning the customer change the experience for either the customer, the connected account, or the platform? I'm struggling to seeing the advantage of cloning
Cloning is a bad approach in general. It is commonly used with Direct charges where the customer needs to exist on the connect account but a platform wants to use the same customer across multiple connect accounts.
The reason it's bad is the word "cloning" can be taken to mean the records will stay synced but that is not the case. Any change to one record would not be mirrored in the others.
Yes, thanks for the feedback
With destination charges on behalf of the connected accounts that are non-profits, the stripe fees are based on the tax status of the connected account - not the platform, correct?
I believe so as the non-profit is the Merchant of Record but you should really consult Support for tax related questions. We're developer support (APIs n such) here.
https://support.stripe.com/contact/email
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
thanks, appreciate your help