Custom Token on email verification #830

Closed
opened 2026-03-13 08:06:17 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @henrikzabel on GitHub (Mar 11, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

N/A

Describe the solution you'd like

When verifying the email I think it would be a great feature to be able to have custom tokens like: 32123 in addition to the verification links a user can click on.

Describe alternatives you've considered

N/A

Additional context

N/A

Originally created by @henrikzabel on GitHub (Mar 11, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. N/A ### Describe the solution you'd like When verifying the email I think it would be a great feature to be able to have custom tokens like: 32123 in addition to the verification links a user can click on. ### Describe alternatives you've considered N/A ### Additional context N/A
Author
Owner

@dosubot[bot] commented on GitHub (Jun 13, 2025):

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

Issue Summary

  • Proposal to enhance email verification with custom tokens (e.g., numerical codes).
  • Aimed at increasing flexibility and user convenience.
  • No further comments or developments have been made.

Next Steps

  • Is this issue still relevant to the latest version of the better-auth repository? If so, please comment to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jun 13, 2025): Hi, @HenrikZabel. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Proposal to enhance email verification with custom tokens (e.g., numerical codes). - Aimed at increasing flexibility and user convenience. - No further comments or developments have been made. **Next Steps** - Is this issue still relevant to the latest version of the better-auth repository? If so, please comment to keep the discussion open. - Otherwise, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
Author
Owner

@henrikzabel commented on GitHub (Jun 13, 2025):

Yes, this is still a valid idea

@henrikzabel commented on GitHub (Jun 13, 2025): Yes, this is still a valid idea
Author
Owner

@dosubot[bot] commented on GitHub (Sep 12, 2025):

Hi, @HenrikZabel. 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 custom tokens such as numeric codes for email verification as an alternative to clickable links.
  • The issue was previously marked as stale due to inactivity.
  • You confirmed that the feature request is still valid and relevant.
  • The issue is currently awaiting further discussion or development.

Next Steps:

  • Please let me know if this feature is still important for your use case with the latest version of better-auth by commenting on this issue.
  • If I do not hear back within 7 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 12, 2025): Hi, @HenrikZabel. 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 custom tokens such as numeric codes for email verification as an alternative to clickable links. - The issue was previously marked as stale due to inactivity. - You confirmed that the feature request is still valid and relevant. - The issue is currently awaiting further discussion or development. Next Steps: - Please let me know if this feature is still important for your use case with the latest version of better-auth by commenting on this issue. - If I do not hear back within 7 days, the issue will be automatically closed. Thank you for your understanding and contribution!
Author
Owner

@henrikzabel commented on GitHub (Sep 12, 2025):

Yes, this is still a valid idea

@henrikzabel commented on GitHub (Sep 12, 2025): Yes, this is still a valid idea
Author
Owner

@ping-maxwell commented on GitHub (Sep 30, 2025):

I think that if you use the emailOTP plugin this will update the emailVerified to true already

@ping-maxwell commented on GitHub (Sep 30, 2025): I think that if you use the emailOTP plugin this will update the emailVerified to true already
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#830