Feature Requests

1) The problem → I need members to be able to purchase one of my subscription products multiple times. 2) Why is this important → It's my pricing model. 3) What will happen if this goes unsolved → I will need to use a workaround where. Members have to switch back and forth between a duplicate of my plan and my plan. This is not easy to set up or ideal for tracking. 4) Possible solutions → Allow for quantities and for repeat checkout events.

1) The problem → The success and error messages aren't very helpful. The wording doesn't match my use case, the colors don't stand out against my color scheme, and the styling doesn't quite match. 2) Why is this important → I want to customize the color, the words, the language, and the styling so that it fits with my business/project. 3) What's your plan B → Override with CSS and the translation code. 4) Possible solutions we could build for you → Add more variations, make the duration it's visible adjustable, and so on.

1) The problem → I can only use Memberstack on one website / domain. I don't want members to have to log in every time they switch websites. A portion of my content lives on another website/subdomain/CMS. 2) Why is this important → My CMS isn't on my main marketing site (where people log in) and I really don't want to give up my CMS. It's core to my value prop. 3) What's your plan B → Leave half of my content "unlocked" or move all of my content into a single domain. 4) Possible solutions we could build for you → I love love it if a session carried over between domains. So, a member could log in on mywebsite.com and then access content as a logged in member on app.mywebsite.com . Both websites would have the same Memberstack script installed.

1) The problem → Having a password field adds extra steps and more friction to the signup process. 2) Why is this important → People easily create accounts by creating passwords later. 3) What's your plan B → They could use https://help.memberstack.com/en/articles/3930198-passwordless-signup-workaround to make it work. 4) Possible solutions we could build for you → Allow somebody to create an account, basically passwordless signup. Keywords: magic link, OTP, email authentication

1) The problem →Due to VAT policies I need my old Memberstack Invoices in Stripe to add my company's billing address and some other information. 2) Why is this important → This is due to the new VAT policies 3) What's your plan B → Have Memberstack edit the pdf's for me 4) Possible solutions we could build for you → A way to add information to Stripe's old invoices.

1) The problem → Hi! I need new users to be verified before they can access the hidden content on my page. I can't find an easy way to do this. They sign up, then they need to be verified by an admin before they can log in and get access to the content. 2) Why is this important → Anyone can find the signup form on my website, but I need to confirm something (their identity, the answer to onboarding questions, etc.) before they get access. 3) What's your plan B → https://help.memberstack.com/en/articles/3850065-approve-new-members 4) Possible solutions we could build for you → Create a new membership plan status of "pending" or "waiting." Ideally, I'd get an email or notification that a new person is pending approval and have a simple UI where I can view pertinent information and click "Approve" or "Deny." Each option should send a message letting the person know their new status + an explanation.

1) The problem → Do you have any information on how your service can be used in the European Union? Since the Privacy Shield was invalidated, we have no option to "transfer user data outside the EU“ (especially not to the US). 2) Why is this important → I know it’s a hard topic, but EU businesses cannot use Memberstack at all if this is not tackled. The main issue will be, for example: US authorities reserve the right to gain data access in case of criminal suspicion, whereas this is strictly forbidden in the EU. I don’t see that they will come to a solution, soon. 3) What's your plan B → 4) Possible solutions we could build for you → Use a EU-only Tech Stack for processors and sub-processors to keep at-least all end-user-data strictly inside the EU and its legislation.

1) The problem → I'm teasing features that are only available to paying members. If a free member decides to upgrade to get access to a feature, I want them to stay on the page after upgrade (or go back to the page they were on before entering the upgrade flow). 2) Why is this important → It's critical to the UX of my site. Dropping someone on a generic welcome page after upgrading doesn't make sense given my use case (it might for someone else, but not for me). 3) What's your plan B → Write some custom code to override this behavior. I wanted to use the Redirect after signup or login power-up, but that only works for static websites and on sign up. 4) Possible solutions we could build for you → Give me a way to "remember" the current URL and return the person to that page after they upgrade. Maybe with a data attribute, snippet of code, or a list of URLs in the dashboard.

Translation, although can be overridden by JavaScript ( reference ), doesn't cover all cases. Sometimes user can still see the default English text which is very confusing.