#humblegawwwd
1 messages · Page 1 of 1 (latest)
The client ID should be set to what you set it to but we do not support choosing a capital-c Customer (one that you have a Stripe object for) via that parameter
Checking in to why the client ID is not getting passed on and what you can do here
Are you looking to re-use existing customer objects?
yes
on my website (which is fairly greenfield right now) I track who a customer is in stripe through their stripe_id.
Should I be passing in my own site's userId as a client-reference-id? If I did that, how would I deal with things like cancellations, updating subscriptions, etc...
If you want to re-use the Customer ID, you would need to use Stripe Checkout for subsequent sessions after the first time the user pays you.
For things like cancellations and updating subscriptions, you can use our customer portal, which has low code and no-code integration options https://stripe.com/docs/no-code/customer-portal
Looking for docs on re-using the Customer in Checkout
So in otherwords, let the first time with the pricing table generate the pricing id. Then use that subsequently with a customer portal?
Yes, the first session will create a Customer with a Customer ID (cus_1234) and after that, that ID is what you can use to tell Stripe to do things with that customer
What would the portal look like when I open it the second or later time. My worry is that I won't be able to customize the interface enough to be usable