#happycappie
1 messages · Page 1 of 1 (latest)
I believe if you pass the customer-email property, this will either force the payment to occur on the preexisting customer or create a new customer with the email that was supplied: https://stripe.com/docs/payments/checkout/pricing-table#customer-email
we don't know the customer email yet. This is a public Pricing Table to sign up for different kinds of memberships and at the time of payment (Checkout session being created) the user will not yet be known.
so our goal is for an actual stripe customer to be created with each Pricing Table Checkout for one time payment and to create a Customer so we can associate that specific Stripe Customer record with a user record we created in our app.
Hmmmm, let me test on my end to see if a customer is created already or not. I believe they would be, but I'm unsure. I'll circle back in a few minutes
i believe guest customers are created
That's what I thought too but I want to make sure that passing an email will not also create a guest customer (though it might)
we are unable to pass an email
the email is captured during checkout, so it's not available yet
Gotcha. I just wanted to see if that was a possible workaround, but if that's absolutely unachievable in your workflow, then I guess the answer is: no, you can't create non-guest Customers via the Pricing Table