onUserVerified hook or afterEmailVerification improvement

[thyngster]

Is this suited for github?

• Yes, this is suited for github

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

Currently, we rely on afterEmailVerification, which is triggered when a user verifies their email through the email sign-up flow.

The problem is that this callback does not fire when using OAuth. For example, a user might first sign up with email and later log in via OAuth, at which point the user is already considered verified.

The core issue is that this logic depends on a callback that is triggered from the /email-verification route, which is never called during OAuth authentication.

Describe the solution you'd like

I understand that afterEmailVerification is intended only for the email sign-up method. However, it feels like it should also be triggered when a user’s email is automatically verified via OAuth.

Perhaps we could introduce a configuration option or flag that allows this verification callback to fire for OAuth-based sign-ins as well, while still allowing others to keep it restricted to email-only verification if they prefer.

Describe alternatives you've considered

And another option would be having a global onUserVerified that trigger whenever the user verified status changes to TRUE.

Additional context

No response

[better-auth-agent]

Thank you for your input regarding the afterEmailVerification hook! It seems that you are suggesting an improvement for how verification callbacks are handled, particularly when users verify their email through OAuth instead of the traditional email sign-up flow.

Currently, there is an open discussion on this topic and suggestions include introducing a configuration option to trigger afterEmailVerification during OAuth sign-ins as well. Another option proposed is creating a onUserVerified hook that would be triggered any time a user's verification status changes to true. These potential improvements demonstrate a flexible approach to enhancing user verification flows in Better Auth.

If you have more specific use cases or features in mind regarding this topic, please feel free to share! It would greatly benefit the development team to have detailed scenarios to consider.

Tag @better-auth-agent if you would like an answer from the Agent!

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

[gustavovalverde]

Related in the same area (not duplicates): #3742, #8043.