For context, currently people have to sign up on a sign up page before they’re sent to the Stripe checkout.
Is there a way to make the sign up page the step after they pay, rather than before?
How to move Memberstack signup after Stripe checkout instead of before on separate domains?
Answered
5 comments
Hello Nathan Billion
Thanks for bringing up your query. The reason we've structured the signup process to precede the Stripe checkout is that creating a member in our system simultaneously initiates certain processes within Stripe, which are then used to facilitate the checkout experience. This integration between creating member accounts and Stripe's payment processing is crucial for how our system currently operates.
Given this setup, we don't have immediate plans to reverse the order of these steps—having payment before signing up. We understand how your suggested flow could offer a different user experience and truly appreciate you sharing this idea with us.
We're always looking for ways to improve and adapt our services to meet the needs of our community better. While we might not implement this change right away, we will certainly consider your feedback for future updates.
Or even better could the signup be part of the checkout process? One step instead of two for some circumstances? I think it would reduce the bounce rate between the signup and checkout pages. Cut some friction for users.
Currently, the front-end website is separate from the back-end where we house the courses with two separate domains.
Would love some help with a logistical question.
I'm working on a Webflow website, and the other two big pieces are Memberstack and Stripe. Members will purchase a course (one-time fee) and then a subscription (recurring) for monthly mentorship. I want the checkout process to be super seamless with as little friction as possible. Ideally, a visitor on the website would purchase the course before having to go through the red tape of setting up an account, and then the account could be created at or after the purchase. Is this possible or will all members have to create an account before purchasing content so that permissions and plans are assigned accordingly?
This link seems to be saying that it's now possible to do this if the Memberstack code is placed on both sites. Is that right?
https://docs.memberstack.com/hc/en-us/community/posts/10560227208091-Use-Memberstack-on-multiple-sub-domains
Is the root domain the same for both the sites?
Say for example if the front-end site is website.com and the back-end site is app.website.com, yes you can install Memberstack script on both and make it work. But if they are 2 separate domains, the cross domain login feature won't work.
Hey Brian Farmer, currently I believe the user has to signup before purchasing any plan. This feature is in wishlist though, so you could upvote or share your thoughts on this to receive any updates in future
Ok that helps tremendously, thanks.
Please sign in to leave a comment.