So, a lot will depend on what you are selling, etc. But at the top level it works like this. Let’s assume you’re selling a membership. That is, you need someone to purchase a digital subscription to access the rest of your Glide app (not just the “Buy subscription” screen). You set up a product in Stripe. Set up a price for the product (your monthly subscription), and a payment link for the price (you do all of this in the Stripe dashboard, no code whatsoever).
Stripe payment links can be personalised for every customer. You do this by including a piece of customer information at the end of the payment link URL as a URL parameter (or a query string). What this piece of customer info will be depends on your Glide plan. If you’re on a Pro plan and you collect actual email addresses - pass the email address through. If Glide obfuscates them, you can pass the Row ID from the Users table as a client_reference_id URL parameter.
To personalise the payment link for each customer in Glide, create a column in your Users table that dynamically personalizes the payment link with the user’s email address or the row id (if you hold your user data in Glide tables, you’ll need to pass the Row ID due to the limitations of Glide Tables API). You can use the “template” or “URL builder” fields. This link is what you add to your buttons in Glide to make them… “Buy buttons”
Once the customer purchases something using this personalized payment link, whatever info you passed through as the URL parameter will appear in the transaction’s checkout object in Stripe. So you can capture it in Make (Watch events => Checkout completed) and then…[ta-da]… pass the info to the Users table in Glide. If you’re using Glide Tables for your Users data, you’d need to use Glide Tables API (use an HTTP module in Make). If you’re using Google Sheets or Airtable - call up the relevant module in Make.
Just don’t forget to change the visibility of the rest of your app in line with the purchase info from your customers that you wrote back to the Users table.
Suppose you’re using a recurring membership model. In that case, there are a few extra steps you’d need to take to link recurring billing (or cancellations) to your Glide customer, but all more than doable with Stripe, Make, and [Glide tables; Google Sheets; Airtable].
Using this setup you can sell memberships, credits, etc. The only limitation is that you probably won’t be able to sell a bazillion of products this way. But if you’re selling access tiers or credits, this will more than do.
You can further automate things by creating a “Products” table and linking a Price ID in Stripe to the membership tier you’ll write back to the Users table when someone purchases it.
Feel free to hit me up if you need a detailed walk-through.