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

[GH-ISSUE #5635] Multiple verified phone numbers #10308

New Issue
Closed
opened 2026-04-13 06:20:55 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-13 06:20:55 -05:00
Owner
Copy Link

Originally created by @ghyath5 on GitHub (Oct 28, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5635

Is this suited for github?

  • Yes, this is suited for github

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

I believe each user should be allowed to add multiple PhoneNumbers and he can verify each one on adding it

Describe the solution you'd like

So I suggest to move phoneNumber and phoneNumberVerified fields to accounts table to allow user to have multiple ones with providerId phone

Describe alternatives you've considered

Additional context

phoneNumber

Originally created by @ghyath5 on GitHub (Oct 28, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5635 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I believe each user should be allowed to add multiple PhoneNumbers and he can verify each one on adding it ### Describe the solution you'd like So I suggest to move `phoneNumber` and `phoneNumberVerified` fields to `accounts` table to allow user to have multiple ones with providerId `phone` ### Describe alternatives you've considered * ### Additional context phoneNumber
GiteaMirror added the enhancementlocked labels 2026-04-13 06:20:55 -05:00
GiteaMirror commented 2026-04-13 06:20:58 -05:00
Author
Owner
Copy Link

@naamanu commented on GitHub (Oct 28, 2025):

i'd like to work on this.

<!-- gh-comment-id:3455417204 --> @naamanu commented on GitHub (Oct 28, 2025): i'd like to work on this.
GiteaMirror commented 2026-04-13 06:20:58 -05:00
Author
Owner
Copy Link

@ghyath5 commented on GitHub (Oct 28, 2025):

@claeusdev it could be a new plugin, until the team update and improve the existing plugin

<!-- gh-comment-id:3455441853 --> @ghyath5 commented on GitHub (Oct 28, 2025): @claeusdev it could be a new plugin, until the team update and improve the existing plugin
GiteaMirror commented 2026-04-13 06:21:00 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jan 27, 2026):

Hi, @ghyath5. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for multiple verified phone numbers per account by moving phone-related fields to the accounts table.
  • This would allow linking several phone numbers to a single providerId "phone."
  • Contributor naamanu showed interest in working on this feature.
  • You suggested an initial implementation as a new plugin before updating the core plugin.
  • The discussion reflects community interest in expanding phone number verification capabilities.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of better-auth by commenting on this issue.
  • If I don’t hear back within 7 days, I will automatically close the issue.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3806096923 --> @dosubot[bot] commented on GitHub (Jan 27, 2026): Hi, @ghyath5. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for multiple verified phone numbers per account by moving phone-related fields to the accounts table. - This would allow linking several phone numbers to a single providerId "phone." - Contributor naamanu showed interest in working on this feature. - You suggested an initial implementation as a new plugin before updating the core plugin. - The discussion reflects community interest in expanding phone number verification capabilities. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of better-auth by commenting on this issue. - If I don’t hear back within 7 days, I will automatically close the issue. Thanks for your understanding and contribution!
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#10308
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?