#tuler-customer-organization

1 messages · Page 1 of 1 (latest)

surreal quailBOT
stark zodiac
#

Hi there

fringe shell
#

Hello @stark zodiac

stark zodiac
#

So you can have an "organization" or an "individual" be represented by a Customer object

fringe shell
#

Ok, but the flow of the payment link starts with an email, right?

stark zodiac
#

Oh you mean within the Checkout flow itself?

#

Like once they open up the Checkout page?

fringe shell
#

Yes, using the no-code payment link alternative

stark zodiac
#

Yeah then they will need to enter an email within the Checkout flow, but that could be any email really.

fringe shell
stark zodiac
#

That is pretty different... that's for Subscription management

#

What's the exact confusion here? I'm not sure what you are asking at this point, sorry

fringe shell
#

Yes, that is what I need, subscription management. But my question is how to deal with user subscriptions and organization subscritpions.

stark zodiac
#

Well are you planning on having any sort of authentication on your end when they visit your site?

#

That is really the way to handle it

#

So you authenticate them then you would redirect them to the Portal corresponding with their Customer ID

fringe shell
#

I do have authentication (integration with auth0). A user can signup, I have his email, etc. Then he can create organizations in my system. So he has his personal account, and organization accounts as well.

stark zodiac
#

Okay, so all you need to do is link that "organization" to the Customer ID within Stripe

fringe shell
#

Correct, I can have a Customer ID for his user, and a Customer ID for each of his organizations. Correct? So far so good.

#

Now I need to enable the user to subscribe to a plan either to his personal account or to one of his organization accounts.

#

I was planning to use the Customer Portal for that.

stark zodiac
#

Overall Payment Links doesn't give you a ton of control here

#

It is meant for a simple one-to-many solution

#

What you really want to do is create Checkout Sessions yourself

#

This allows you to pass a Customer ID directly to the Checkout Session

#

Then you can more easily control the Customer in terms of it being the "organization" or the "person" and also easily manage the Subs with Customer Portal

#

Like every time you have a new Sub created via a PaymentLink you are going to get a new Customer

fringe shell
#

Cool, that's what I needed to know. Can you point me to the right docs page for that?

stark zodiac
fringe shell
#

So the Customer that represents an organization, is the email field required? Or unique?

stark zodiac
#

It will be required on the Checkout Session, yes. It does not have to be unique.

#

You can also pre-fill the email yourself if you want

#

By setting it on the Customer and passing the Customer ID to the Checkout Session, or you can pass customer_email to the Checkout Session on creation

fringe shell
#

Thank you for your help! I'll continue my research

pure lantern