Not a bother, Memberstack implements SSO, no reason for a new username & password:
Just link those two platforms via SSO together (if that’s an option on their end).
Also, there’s more than what’s being mentioned with Memberstack & Membership solutions.
This screencast of mine is a good example of just that.
It’s not about restricting access to pages, it’s about restricting access to content. Webflow Memberships does not do this, Memberstack does.
That’s a big gap being missed.
Like I mentioned, these two solutions serve different purposes.
Discount codes may be an option, but there is a lot of complexity in making sure that works as described and managing those codes (possibly their AAA membership IDs) in real-time within the Webflow ecommerce CMS based upon the changes in another system.
Far less straight forward (maybe not even possible) versus managing this in Airtable which has a lot of solutions out-of-the-box for folks.
That would require a user system (username & password) unless you left it open for anyone to bypass - which isn’t the worst thing in the world. But the OP mentioned how their similar solution today is not that desirable.
Anywho… hope that helps!