Billing for subscription management with payment providers #42

Closed
opened 2026-03-13 07:29:30 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @ruimarcosjoao on GitHub (Oct 5, 2024).

create a plugin that will allow people to add it to their schemas to deal with system subscription validation, for example using a stripe to manage subscriptions if it is for a saas, and add hooks to do this same management
With this option it will also allow us to restrict who can create an organization, manage payments without having to create logic outside of Better-auth

imagem

Originally created by @ruimarcosjoao on GitHub (Oct 5, 2024). create a plugin that will allow people to add it to their schemas to deal with system subscription validation, for example using a stripe to manage subscriptions if it is for a saas, and add hooks to do this same management With this option it will also allow us to restrict who can create an organization, manage payments without having to create logic outside of Better-auth ![imagem](https://github.com/user-attachments/assets/255f8aba-097a-4e99-a8fb-ae6573f71d40)
GiteaMirror added the enhancementplugin labels 2026-03-13 07:29:30 -05:00
Author
Owner

@Bekacru commented on GitHub (Oct 5, 2024):

good idea. We've been thinking about this as well.

@Bekacru commented on GitHub (Oct 5, 2024): good idea. We've been thinking about this as well.
Author
Owner

@ncor commented on GitHub (Oct 17, 2024):

Might be an overhead. I don't consider access logic such as subscriptions to be the part of authentication. Maybe conditional logic from user is enough.

@ncor commented on GitHub (Oct 17, 2024): Might be an overhead. I don't consider access logic such as subscriptions to be the part of authentication. Maybe conditional logic from `user` is enough.
Author
Owner

@Bekacru commented on GitHub (Oct 17, 2024):

Might be an overhead. I don't consider access logic such as subscriptions to be the part of authentication. Maybe conditional logic from user is enough.

as a plugin could make sense. since it's a common use case.

@Bekacru commented on GitHub (Oct 17, 2024): > Might be an overhead. I don't consider access logic such as subscriptions to be the part of authentication. Maybe conditional logic from `user` is enough. as a plugin could make sense. since it's a common use case.
Author
Owner

@Bekacru commented on GitHub (Oct 17, 2024):

but mostly probably we won't implement this before v1.

@Bekacru commented on GitHub (Oct 17, 2024): but mostly probably we won't implement this before v1.
Author
Owner

@ncor commented on GitHub (Oct 18, 2024):

as a plugin could make sense

As additional field provider - yes, it would be much easier to work with subscriptions as authorization rules.

@ncor commented on GitHub (Oct 18, 2024): > as a plugin could make sense As additional field provider - yes, it would be much easier to work with subscriptions as authorization rules.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#42