slepzs_best-practices

[spark cypress]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1332343955530059879

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[quick steeple]

Hi, let me help you with this.

A single Checkout Session can only produce one Subscription, unfortunately.

You can still have multiple line_items, containing Products linked to different Connected accounts. If the customer wants to cancel just one of them, you can always update the Subscription line_items, and apply proration if required.

Now, when you need to transfer the funds to the Connected accounts - I suspect you're using Destination charges, i.e. Platform is accepting the payment from the customer - you can configure it in the way that you will manually create the Transfers ("Separate charges and transfers"), each with a portion of the total Invoice amount corresponding to each destination's line_item amount.

Please let me know if I should clarify any part of this.

[quick steeple]

To clarify "Products linked to different Connected accounts" is an informal link, via metadata for example. There's no built-in way to link Products on the Platform to Connected accounts.

[whole tusk]

Hi, thank you for your response!

I want to ensure I fully understand the workflow you're describing:

1. If I use a single Subscription with multiple line items for products linked to different vendors (Connected accounts), the subscription itself remains under the platform account, correct?
2. You mentioned using metadata to link products to Connected accounts. In this scenario, do I manually create Transfers based on the amounts in the line items after each invoice payment?
   If a customer cancels a single line item in the subscription, would I need to manually prorate and adjust the Transfers to the respective vendor?

Lastly, is there any recommended best practice for managing this kind of setup when dealing with multiple vendors in a subscription model? For instance, would it be better to create separate Subscriptions instead of bundling them, even if it complicates the checkout flow?

[wintry inlet]

Hey! Taking over for my colleague. Let me catch up.

If I use a single Subscription with multiple line items for products linked to different vendors (Connected accounts), the subscription itself remains under the platform account, correct?
There is no such a notion of "linked price to a Connected Account", but if the price is created at the Platform Level, then yes this is true: The Subscriprion will be created at the Platform level.

You mentioned using metadata to link products to Connected accounts. In this scenario, do I manually create Transfers based on the amounts in the line items after each invoice payment?
Yes this is a good option. Or you can have this mapping in your integration/database.

Lastly, is there any recommended best practice for managing this kind of setup when dealing with multiple vendors in a subscription model? For instance, would it be better to create separate Subscriptions instead of bundling them, even if it complicates the checkout flow?
Your current design is good yes. It's better than creating multiple Subscriptions.

But this will depends mostly on the Charge type you want to employ (Direct or Destination?)

[whole tusk]

Hi, os4m37

Ive made a excalidraw to clarify my flow. I hope it makes sense, and i am sorry if it made it more confusing. I think we want to be using Destination charges to apply a fee to each monthly renewal.

Thank you for looking at it