Support for Organizations in Polar Better Auth Plugin

[maoosi]

Description

The Better Auth Stripe plugin supports Organizations (docs). Could the Better Auth Polar plugin also support Organizations?

Use Case

I'm considering using Polar for a future SaaS product, and built-in support for Organizations would make things much easier.

Expected Behavior

• Associate subscriptions with organizations instead of individual users.
• Also work with a similar authorizeReference function to verify that the user has permission to manage subscriptions for the organization.

Thanks!

[birkjernstrom]

Great suggestion and definitely something we want to support (cc @emilwidlund)

Just shared our public roadmap and we have some exciting ideas for how we want to approach seat billing on Polar and tie it into our automated entitlements (benefits) as well. I think once we get there (v1.7) we could and should be able to offer some really powerful capabilities to organizations and seamlessly integrate it within Better Auth.
#5227

[maoosi]

Thanks for the update @birkjernstrom.

In my use case, the key requirement is to associate subscriptions with organizations (teams/groups within my app) rather than individual users. Currently, the plugin automatically links everything to a user. While the seats feature in 1.7 is a nice addition, it’s not always necessary for all contexts.

To avoid confusion, when I say "organization" I’m referring to entities within my app, not Polar’s internal organizations.

If I need to implement this myself for now, what’s the best way to associate subscriptions with app-level organizations using the existing Polar API?

• My initial idea was to pass a org_id as external_id instead of linking it to a user_id. However, since Polar requires a unique email for each customer, a user wouldn’t be able to manage multiple orgs (as this would require creating multiple customers with the same email).
• I then considered having a single org owner manage a given org subscription and update the Polar customer (email + external_id) when the org owner changes. But the Update Customer endpoint doesn’t allow modifying external_id.

What would be the best approach to achieve this?