#PayRole Admin
steady pumice
main warren
Hi there, can you tell me is there a problem that you want this new param to solve that Separate Charges and Transfers can't?
remote radish
Hey! Yes, this would enable functionality similar to Separate Charges and Transfers but with Stripe Standard Connect instead of Express or Custom.
main warren
In your proposal, where will the charge be created? in platform or connected account?
remote radish
In your proposal, where will the charge be created? in platform or connected acc...
The Charge would be created in the Connected Account as in the Direct Charges approach.
main warren
OK, and you can achieve the same goal by creating multiple Direct Charges right?
remote radish
OK, and you can achieve the same goal by creating multiple Direct Charges right?
I believe so, however ideally it should be possible with Subscriptions and Payment Intents as they currently exist.
main warren
In this case, I don't think we need to introduce a new param since we already have a solution.
remote radish
In this case, I don't think we need to introduce a new param since we already ha...
Although technically possible, the result is non-atomic such that it would require management of multiple subscriptions. For instance, imagine that a Subscription that pays an affiliate were created in addition to a Subscription that pays a merchant. Then, if the merchant were to cancel one Subscription but not the other the system could get out of sync. Also, this is very unclean when viewed from the Customer's perspective, as the Billing Portal would show multiple Subscriptions when they only subscribe once. Since it seems that a single Subscription cannot currently perform the application_splits as described above using Stripe Connect Standard, then I think this may warrant a new parameter.
main warren
I don't think there's a way to share the same customer across multiple accounts at this moment.
remote radish
I don't think there's a way to share the same customer across multiple accounts ...
I don't think it's necessary to do so, as the current Stripe Connect only creates an Application Fee in the Connect Platform when a payment is recieved - so the Customer stays only in the Connected Account that originated the Charge. In this scenario, nothing changes except an Application Fee is created in not just the Connect Platform's account, but also in the Connected Accounts that receive splits.
main warren
The application fee is designed for platform, you can't transfer an application fee to a connected account.
If you have a Separate Charges and Transfers shaped use case, I'd suggest using express/custom accounts instead of standard account.
remote radish
Okay, I understand. Is there someone I can talk to about a possible feature suggestion for the future?
main warren
You can submit your feature request to https://support.stripe.com/contact/email