#Min.K
pearl swallowBOT
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.
grave portal
With Checkout Session in subscription mode, customer will always be required, i.e. create a new one or use an existing one with customer field set.
If you do not wish to create a new customer, I'd recommend setting the customer (cus_xxx) that associated with the email, so that no new customer will be created
ocean thistle
If you do not wish to create a new customer, I'd recommend setting the customer (cus_xxx) that associated with the email, so that no new customer will be created
No, I want a new CustomerId to be generated each time I perform a new subscription via the Stripe Checkout Session API. Right now, if the email is the same, the subscription is created with the most recently created CustomerId that has the same email.
grave portal
Hmm... Can you share an example Checkout Session (cs_xxx) with this scenario? It shouldn't be the case
ocean thistle
Ok wait a minutes please
Case
- Call Checkout Session API for Subscription A (with customer_email == A)
- Invoice paid completed.
- Stripe Customer Generated (cus_1)
- cus_1 customer has subscription A
- Call Checkout Session API for Subscription B (with customer_email == A)
- Invoice paid completed.
- Stripe Customer did not generated.
- cus_1 customer has subscription B
I want a new CustomerId to be generated even if it is the same email.
ocean thistle
May I ask for an answer?
grave portal
I don't see the example Checkout Session ID (cs_xxx) for the flow you described.
This flow shouldn't happen as mentioned earlier
I'd need the example Checkout Session ID (cs_xxx) to check what happened
At step 5 without setting customer, it should create a new customer even though the email is the same
ocean thistle
I will give you my checkout session id
cs_test_a10VRS2UedCjWKVqM9Un9Za5cJYOwONgIzBM7AKb7Qo2kynBn9TpsRLng1
pearl swallowBOT
ocean thistle
I just tested it with a different card number and it seems to have created a new Customer.
By any chance, does it recycle the same CustomerId if they have the same email and use the same card?
median cobalt
Hi! I'm taking over this thread.
ocean thistle
Hi
median cobalt
If you want to reuse the same customer object, then the only option is to pass a customer ID here: https://stripe.com/docs/api/checkout/sessions/create?lang=node#create_checkout_session-customer
ocean thistle
No, i do not want to reuse
median cobalt
Then never pass a customer ID.