github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #3428] Add metadata to subscription using stripe plugin #9600

New Issue
Closed
opened 2026-04-13 05:09:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 05:09:01 -05:00
Owner
Copy Link

Originally created by @CyrilPERIE on GitHub (Jul 17, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3428

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

In our application, a user can pay for other users.
Once someone is tagged as a consumer, they are considered subscribed.

To handle this, we created a view where a user can select other users to subscribe.

We implemented the subscription logic using await authClient.subscription.upgrade, and we passed metadata like this:

metadata: {
    consumerIds: "test,test,test,test",
}

Describe the solution you'd like

We would like these metadata to be stored in the subscription metadata on Stripe’s side, so we can retrieve them from the available hooks:

onSubscriptionUpdate
onSubscriptionComplete

This would allow us to store them in our database

Describe alternatives you've considered

Ideally in the stripe plugin setup add a metadata column that store the metadatas.

Additional context

No response

Originally created by @CyrilPERIE on GitHub (Jul 17, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3428 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. In our application, a user can pay for other users. Once someone is tagged as a consumer, they are considered subscribed. To handle this, we created a view where a user can select other users to subscribe. We implemented the subscription logic using `await authClient.subscription.upgrade`, and we passed metadata like this: ``` metadata: { consumerIds: "test,test,test,test", } ``` ### Describe the solution you'd like We would like these metadata to be stored in the subscription metadata on Stripe’s side, so we can retrieve them from the available hooks: `onSubscriptionUpdate` `onSubscriptionComplete` This would allow us to store them in our database ### Describe alternatives you've considered Ideally in the stripe plugin setup add a metadata column that store the metadatas. ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 05:09:01 -05:00
GiteaMirror commented 2026-04-13 05:09:03 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (Jul 17, 2025):

duplicate #3429

<!-- gh-comment-id:3085894445 --> @Kinfe123 commented on GitHub (Jul 17, 2025): duplicate #3429
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#9600
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?