checking out the polar component Sean
checking out the polar component Sean worked on - looks pretty sweet.
For a Saas that has subscriptions bound to Teams, (not users directly, though I'd still like to have a customer binding to a user), would the polar component support this architecture? In the examples on the docs, the subscription bindings seem to be with users themselves (as it should be for most products).
6 Replies
I suspect it might already be techincally compatible if your team model is just substituting a user for a team. I don't see explicit team support in the polar docs - guessing you have teams mapping to customers in polar?
i think that's how these things usually work. customer can map to both org and/or users
That sounds promising. Haven’t implemented anything yet, still early, researching some options currently.
The ux I like is the convex dash. There is the notion of a person with a credit card, that is the owner of the team
Haven't thought it completely through, but
userId should be able to be whatever you need it to be, eg., a team id, and the getUserInfo function you provide in the config can return a userId and email that map to some sort of team id and email.yeah exactly
regarding the MoR vs stripe wrapper function - I imagine i'll want the MoR so i can scale internationally. Is that something that would require different configuration with the Polar component itself?