#Min.K
brazen vergeBOT
Hello! We'll be with you shortly. 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.
fringe flame
No in subscription mode a customer has to be created always if you don't pass one: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer
Recommend you keep track of your customers on your side so you can pass a customer id if one exists already
signal hull
You mean to create a CustomerId and map it to the actual product's user identifier in our database?
fringe flame
yep
signal hull
What could go wrong if we don't create a CustomerId when we call the Checkout Session API and let it continue to be generated automatically?
fringe flame
Well you'll just have a ton of duplicate customers
Which can be unmanageable
Will make your Stripe dashboard extremely difficult to view/deal with
signal hull
I want to manage based on subscriptionId instead of CustomerId, will that work?
fringe flame
What do you mean
brazen vergeBOT
signal hull
Question 1. Under what circumstances is it appropriate to create a subscription with the Stripe Checkout Session API without a CustomerId?
Question 2. I want to map based on subscription ID. We store customers of our products in our database so that they have a subscription identifier. Afterwards, when the invoice.paid event is sent, we attempt to give the product to the customer with that subscription identifier. This will continue to generate a CustomerId. I wonder what problems this could cause.