How to set up Stripe payments with Memberstack for non-logged-in users before membership creation?

• 

  Josh Lopez

  • December 14, 2023 19:02

  Hey Amy Lamb
  
  Thank you for your inquiry about the possibility of non-members making payments for memberships before becoming official members on Memberstack.

  I must inform you that this functionality is currently not supported in Memberstack due to our system's requirement to assign a unique Stripe customer ID to each member. This step is crucial for securely managing subscriptions and payments. As such, a member account needs to be created first before any payment can be processed.

  The data-ms-price:add="test" attribute you are referring to works exclusively for logged-in users to add services or products to their existing membership. It cannot facilitate payment processing for individuals who are not registered members.

  While external payment methods like Stripe's payment links or checkout sessions can be used for collecting payments, integrating these payments into Memberstack for automatic membership creation is not something we support or recommend, due to the complexities and manual intervention required.

  We understand that this might not align with your current needs, and we apologize for any inconvenience caused. If you have any more questions or if there's another way we can assist you, please don't hesitate to reach out.

  1
• 

  Chanakya Ratnam

  • March 09, 2025 21:02

  Help Needed: No-Code Dashboard Flow for Multi-Tier Plans (Webflow + Memberstack + Stripe)
  Hi everyone! 👋

  I’m building a no-code dashboard using Webflow (frontend), Memberstack (memberships), and Stripe (payments). The current flow requires users to create an account in Memberstack first, followed by payment in Stripe. However, this is causing drop-offs during the Stripe payment step.

  Desired Flow:

  • User selects a plan and pays directly through Stripe.
  • After payment, their Memberstack account is automatically created.
  • They are redirected to the dashboard with the correct plan access.

  Question:
  How can I structure this flow to collect payment first and then create the Memberstack account? Should I use tools like Zapier, Make, or custom code?

  Any advice would be greatly appreciated! Thanks! 😊

  0
• 

  A J

  • March 09, 2025 21:04

  Hey Chanakya Ratnam, I believe currently this kind of flow is not possible since Memberstack requires creating a member account and then paying for the plan. That way, Memberstack will link that member with the relevant unique stripe customer ID in the back-end. This is a best practice for memberships which are recurring in nature.

  I am not sure what kind of plans you are aiming to provide for the users, but in case the plan type you are providing is like a one-time purchase and you are very sure you won't need to scale it to recurring / have automatic Memberstack + Stripe connect in the back-end data, you can opt for the desired flow.

  You can

  • handle the payment first via stripe,
  • create a workflow which listens to stripe purchases and

  1. create an account for the user in Memberstack with a dummy password (also send this dummy password to the user's email in order for them to reset to a secured one)
  2. assign such user a free plan in Memberstack (since we cannot add a paid plan to a member via automation),
  3. store the stripe customer id in a custom field (just in case) and
  4. assign necessary access to gated content for such free plan in Memberstack.

  You can create the workflows via Make / Zapier. This is indeed a way to achieve the desired flow but the choice of going with this will depend on whether it seems ideal and feasible for the project. Hope this helps.

  0

Please sign in to leave a comment.