#lawrence_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1349609569420054559
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- lawrence_webhooks, 6 days ago, 5 messages
Hi there, you can follow this guide to use destination charges to create subscriptions https://docs.stripe.com/connect/subscriptions#use-destination-charges-to-create-a-subscription
You don't need to store the connected account ID as a metadata to the subscription. You can get the connected account's ID from the subscription's transfer_data[destination]
Thanks, i've read that document already. I'm specifically asking what's the best practice for creating plans for a specific connected account
ideally the plan is exclusive to the tied connected account
Can you share more context so that I can understand what you want to achieve?
Sure! We would like to offer our customers (connected accounts) the ability to create different subscription plans that they can offer to their patients.
I see, so basically you want to create prices on your account (i.e, platform) specific for a particular connected account.
correct
Got it! Yes in that case, I agree that attaching a metadata to the objects is an appropriate solution.
Awesome! Thanks for verifying the appropriate solution.