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

[GH-ISSUE #5388] Add Stripe cancel_at to subscription table #27553

New Issue
Closed
opened 2026-04-17 18:37:44 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-17 18:37:44 -05:00
Owner
Copy Link

Originally created by @Escapado on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5388

Is this suited for github?

  • Yes, this is suited for github

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

Hi,

So I am trying to integrate stripe through the better-auth package and it is going great. However I noticed that when the webhook handles the customer.subscription.updated event, if there is a cancel_at present in the update (such as when an auto-renewing subscription is cancelled through the customer billing dashboard), then there is no column to represent that and so the data in the subscription table does not change. We have status but that remains active, we have cancel_at_period_end but that pertains to regular auto-renew and does stay null in this case and period_end which is also just the normal billing end date.

So in a sense, now the application has no idea that the subscription is scheduled to be cancelled by the end of the billing period. In my case I would like to show a message on my billing section my site that informs the user that their subscription is scheduled to be cancelled at the end of their billing period and no auto-renew will happen (and subsequently not show them a cancel button that redirects them to their billing portal).

Describe the solution you'd like

In the @better-auth/stripe package I would like a cancel_at column in the subscription table and I would like the webhook to fill that field accordingly in response to the customer.subscription.updated event and ensure that the authClient.stripe.list({...}) would then return it too.

Describe alternatives you've considered

The current workaround is to add this column in the subscription schema yourself and then add a onSubscriptionUpdate callback in the stripe plugin to do a manual update on the data. I think it would be great if the package could handle that.

Additional context

No response

Originally created by @Escapado on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5388 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Hi, So I am trying to integrate stripe through the better-auth package and it is going great. However I noticed that when the webhook handles the `customer.subscription.updated` event, if there is a `cancel_at` present in the update (such as when an auto-renewing subscription is cancelled through the customer billing dashboard), then there is no column to represent that and so the data in the `subscription` table does not change. We have `status` but that remains active, we have `cancel_at_period_end` but that pertains to regular auto-renew and does stay null in this case and `period_end` which is also just the normal billing end date. So in a sense, now the application has no idea that the subscription is scheduled to be cancelled by the end of the billing period. In my case I would like to show a message on my billing section my site that informs the user that their subscription is scheduled to be cancelled at the end of their billing period and no auto-renew will happen (and subsequently not show them a cancel button that redirects them to their billing portal). ### Describe the solution you'd like In the `@better-auth/stripe` package I would like a `cancel_at` column in the subscription table and I would like the webhook to fill that field accordingly in response to the `customer.subscription.updated` event and ensure that the `authClient.stripe.list({...})` would then return it too. ### Describe alternatives you've considered The current workaround is to add this column in the `subscription` schema yourself and then add a `onSubscriptionUpdate` callback in the stripe plugin to do a manual update on the data. I think it would be great if the package could handle that. ### Additional context _No response_
GiteaMirror added the lockedenhancement labels 2026-04-17 18:37:45 -05:00
GiteaMirror commented 2026-04-17 18:37:46 -05:00
Author
Owner
Copy Link

@billy-victory commented on GitHub (Oct 21, 2025):

Yeah having the same issue will the cancel_at_period_end be removed and replaced with this?

<!-- gh-comment-id:3425115188 --> @billy-victory commented on GitHub (Oct 21, 2025): Yeah having the same issue will the cancel_at_period_end be removed and replaced with this?
GiteaMirror commented 2026-04-17 18:37:47 -05:00
Author
Owner
Copy Link

@kubk commented on GitHub (Oct 29, 2025):

Bump so it gets more attention.

I had to re-configure Stripe to workaround it. It'd be nice if better-auth supported it, since "Cancel at the end of billing period" is default Stripe's behavior for the customer portal

<!-- gh-comment-id:3461280629 --> @kubk commented on GitHub (Oct 29, 2025): Bump so it gets more attention. I had to re-configure Stripe to workaround it. It'd be nice if better-auth supported it, since "Cancel at the end of billing period" is default Stripe's behavior for the customer portal
GiteaMirror commented 2026-04-17 18:37:48 -05:00
Author
Owner
Copy Link

@MaxLikesCode commented on GitHub (Dec 11, 2025):

Feature Classic Billing (Basil & Older) Flexible Billing (Clover Default)
Cancellation Field cancel_at_period_end: true cancel_at: 1759104000 (Timestamp)
Portal Behavior Toggles the boolean flag. Calculates the date and sets cancel_at.
Mixed Intervals Not supported. Supported (hence the need for exact dates).

That's why it's absolutely crucial to either replace cancel_at_period_end with cancel_at (since we can derive the cancel_at value from cancel_at_period_end anyway) or add it to the table.

<!-- gh-comment-id:3642035960 --> @MaxLikesCode commented on GitHub (Dec 11, 2025): | Feature | Classic Billing (Basil & Older) | Flexible Billing (Clover Default) | |--------|--------|--------| | Cancellation Field |`cancel_at_period_end: true` |`cancel_at: 1759104000` (Timestamp) | | Portal Behavior | Toggles the boolean flag. | Calculates the date and sets `cancel_at`. | | Mixed Intervals | Not supported. | Supported (hence the need for exact dates). | That's why it's absolutely crucial to either replace `cancel_at_period_end` with `cancel_at` (since we can derive the `cancel_at` value from `cancel_at_period_end` anyway) or add it to the table.
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 enhancement 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#27553
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?