#village-checkout-email
tepid dust
The customer part of the session object, it says checkout will create a customer object based on that. It becomes the "customer id"? I could use that same thing for creating the link to customer portal page? Safe to use their email address for this ID?
And if i create another checkout session using the same customer value will it overwrite the previous checkout session?
deft vault
no it's not the customer id, the id is cus_123456 unrelated to the email
If you pass customer: 'cus_1234' on Checkout Session creation it has to be an already existing Customer in your account
tepid dust
Not sure we on the same wavelength. I might have confused it by using email in two different ways. Not related to customer_email. If i wanted to just use their email i have on file as the customer value, does that create their customer object in stripe with that email as their ID? And would i supply that for sending them to the portal page?
deft vault
no I understood what you meant, that's why I tried to explain it my way. It can't work, you can't choose the id, when you pass customer it has to be an already existing Customer in your account and our ids are always cus_1234567
tepid dust
Oh, i see, so i have to create the customer first using a different API.
deft vault
or you let Checkout do that for you as part of the first transaction
tepid dust
But i don't want to create a customer object for someone if they haven't paid yet. This is for subscriptions, so if they haven't paid they aren't a customer and im not even creating an entry on my site for them yet.
tepid dust
So on the callback you are passing to me the cust_id created?
deft vault
yes
tepid dust
Will your system allow more than one customer object with the same customer_email? Or will i have conflict issues if i dont protect against that?
deft vault
we have no de-duplication so yes we allow it and you have to handle this if you don't want to let us do that
tepid dust
I have only gotten as far as creating a checkout session for a subscription, i can follow the link to the payment page. How do i addon a one time fee in addition to the subscription like a setup fee? Is there something to set in the session object or do i have to switch to a whole different API/Object?
deft vault
you would simply add an extra line item when you create the Session really
tepid dust
Okay, that makes sense.
tepid dust
For subscriptions; On dashboard i created products (subscription levels) like base, silver, gold. Then for each product i have created different prices for a monthly and yearly price. I pass the API ID price_xxxxx to have them pay that on the checkout page.
Instead, is there a way to just pass that product ID, and on the checkout page it can present them with the price options, monthly vs yearly, and allow them to pick which they want?
deft vault
so you still pass a Price id today, but we support what we call "upsells" which allows you in the Dashboard to configure the yearly Price as an upsell of the monthly Price
tepid dust
ok
tepid dust
Will upsells work with subscription + setup? It says you can only have one type=recurring in checkout session or is that about something else?
deft vault
it's per line item so yes it just works. But you can't change N line items "in bulk" if that makes sense
but you can have a setup fee and a monthly Price and then switch the monthly for the yearly, keeping the setup fee Price as is
tepid dust
Okay, i see that now. But i can only have one upsell per line item. Thx.
The email i pass as customer_email which is what my customer will be forced to use on the checkout page. Are there any circumstances where they will need to be able to check that email address to complete their purchase?
Like some code emailed to them they have to give stripe to finish.
deft vault
not exactly, but you want it to be valid since that's where we'll send follow up emails like an email receipt or instructions on how to pay when they use OXXO for example in Mexico
tepid dust
Im working on email subscription service, so the email would accept, but they wouldn't have access until i get the hook of payment approved. Just wanted to make sure i wasn't creating a roadblock.