[GH-ISSUE #532] Account creation on marketing pricing page #140

Closed
opened 2026-02-26 18:45:32 +03:00 by kerem · 4 comments
Owner

Originally created by @dguyen on GitHub (Oct 6, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/532

Issue Description

Currently when a user navigates to the /pricing page and submits the form to claim the 'early adopter plan', an account is unknowingly created for them regardless if they complete the stripe checkout out not.

Previously this wasn't an issue, but with the introduction of free accounts users who previously didn't complete the stripe checkout will find that an account already exists when they go to sign up.

There might also be an issue where a user creates an free account, then navigates to the pricing page to claim the plan and have their password reset since we appear to upsert the user with a random password during this process.

Steps to Reproduce

  1. Navigate to the marketing pricing page
  2. Click 'Signup Now' and submit the form with your details
  3. Regardless of the outcome (error or stripe redirect) navigate to the web app
  4. Sign up with the same credentials you entered in step 2
  5. You should be informed that an account already exists

Expected Behavior

You should be able to proceed with creating an account in step 5, since you never explicitly signed up before.

Current Behavior

You are informed that an account already exists even though you never explicitly created an account

Additional notes

  • The user can go through the forgot password flow, but this obviously isn't optimal
  • We probably can't resolve this for users who already created an account via /pricing without a spicy migration
Originally created by @dguyen on GitHub (Oct 6, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/532 ## Issue Description Currently when a user navigates to the `/pricing` page and submits the form to claim the 'early adopter plan', an account is unknowingly created for them regardless if they complete the stripe checkout out not. Previously this wasn't an issue, but with the introduction of free accounts users who previously didn't complete the stripe checkout will find that an account already exists when they go to sign up. There might also be an issue where a user creates an free account, then navigates to the pricing page to claim the plan and have their password reset since we appear to upsert the user with a random password during this process. ## Steps to Reproduce 1. Navigate to the marketing pricing page 2. Click 'Signup Now' and submit the form with your details 3. Regardless of the outcome (error or stripe redirect) navigate to the web app 4. Sign up with the same credentials you entered in step 2 5. You should be informed that an account already exists ## Expected Behavior You should be able to proceed with creating an account in step 5, since you never explicitly signed up before. ## Current Behavior You are informed that an account already exists even though you never explicitly created an account ## Additional notes - The user can go through the forgot password flow, but this obviously isn't optimal - We probably can't resolve this for users who already created an account via `/pricing` without a spicy migration
kerem 2026-02-26 18:45:32 +03:00
  • closed this issue
  • added the
    type: bug
    label
Author
Owner

@anjy7 commented on GitHub (Oct 6, 2023):

Is this issue public? If yes then I would like to take this

<!-- gh-comment-id:1750096446 --> @anjy7 commented on GitHub (Oct 6, 2023): Is this issue public? If yes then I would like to take this
Author
Owner

@dguyen commented on GitHub (Oct 6, 2023):

Not yet, this still requires discussion.

<!-- gh-comment-id:1750099646 --> @dguyen commented on GitHub (Oct 6, 2023): Not yet, this still requires discussion.
Author
Owner

@dguyen commented on GitHub (Oct 12, 2023):

@Abhijit20112003 which pull request?

<!-- gh-comment-id:1759437253 --> @dguyen commented on GitHub (Oct 12, 2023): @Abhijit20112003 which pull request?
Author
Owner

@Mythie commented on GitHub (Nov 3, 2023):

Solved this with our recent free plan updates, dangling accounts were removed as part of this change as well 🙌

<!-- gh-comment-id:1791898995 --> @Mythie commented on GitHub (Nov 3, 2023): Solved this with our recent free plan updates, dangling accounts were removed as part of this change as well 🙌
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#140
No description provided.