#canadev_best-practices
weary thistleBOT
đź‘‹ 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/1425936454131126433
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
chilly dust
Hello, are you trying to work through a specific API tutorial of ours? Those words can apply to a few of our different subscription flows, so I want to make sure I'm speaking to the one that you are actually using.
This doc may be what you are looking for. Exactly what objects you create differs, but the two main ways to do this are:
- Create a Customer, create a Subscription with that Customer, use the first PaymentIntent or SetupIntent that the Subscription creates to save the customer's payment method details.
- Create a Checkout Session, when completed the session will automatically create all three objects
https://docs.stripe.com/billing/subscriptions/build-subscriptions
solemn current
Well, we are trying to use the «Subscription» API in B2B context. We are already using it for B2C. We are not following a specific tutorial.
chilly dust
To be 100% honest I am not sure how B2B vs B2C would effect things here, there are a lot of ways to handle both. Can you give more detail on what specifically you are trying to solve?
solemn current
So a «Customer» object does not need to be a real user. It can be a business. Is that correct?
chilly dust
Correct