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

[PR #4995] [MERGED] fix(stripe): sync customer email on db change #13949

New Issue
Closed
opened 2026-04-13 09:14:00 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 09:14:00 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4995
Author: @himself65
Created: 9/30/2025
Status: ✅ Merged
Merged: 9/30/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/09/30/stripe-email-sync

📝 Commits (1)

  • 6be9f0c fix(stripe): sync customer email on db change

📊 Changes

2 files changed (+130 additions, -0 deletions)

View changed files

📝 packages/stripe/src/index.ts (+50 -0)
📝 packages/stripe/src/stripe.test.ts (+80 -0)

📄 Description

Fixes: https://github.com/better-auth/better-auth/issues/2385

Summary by cubic

Sync Stripe customer email when a user's email changes in our database. Keeps Stripe data consistent and prevents checkout/billing issues from mismatched emails.

  • Bug Fixes
    • Added after user.update hook to compare and update Stripe customer email when a stripeCustomerId exists.
    • Gracefully handle deleted customers and errors with logs (best-effort, no failures).
    • Added test verifying retrieve and update are called on email change.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/4995 **Author:** [@himself65](https://github.com/himself65) **Created:** 9/30/2025 **Status:** ✅ Merged **Merged:** 9/30/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/09/30/stripe-email-sync` --- ### 📝 Commits (1) - [`6be9f0c`](https://github.com/better-auth/better-auth/commit/6be9f0c2576f00718151e3610634fcd88283f64d) fix(stripe): sync customer email on db change ### 📊 Changes **2 files changed** (+130 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/stripe/src/index.ts` (+50 -0) 📝 `packages/stripe/src/stripe.test.ts` (+80 -0) </details> ### 📄 Description Fixes: https://github.com/better-auth/better-auth/issues/2385 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Sync Stripe customer email when a user's email changes in our database. Keeps Stripe data consistent and prevents checkout/billing issues from mismatched emails. - **Bug Fixes** - Added after user.update hook to compare and update Stripe customer email when a stripeCustomerId exists. - Gracefully handle deleted customers and errors with logs (best-effort, no failures). - Added test verifying retrieve and update are called on email change. <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 09:14:00 -05:00
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 pull-request
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#13949
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?