CommunityHire an ExpertSign Up
How to GuidesAdd Users to User Groups Based on Stripe Attributes
How to Guides

Add Users to User Groups Based on Stripe Attributes

Setting up user groups based on users’ payment details.

Payment attributes

Payment attributes

If you have connected your Stripe account (in Settings => Integrations => Stripe Checkout) and plan to or are already selling products and subscriptions (e.g. via the checkout form), you can define user group conditions based on those products/subscriptions. This way, only the users that have purchase a specific product(s)/subscription(s) will be able to access the given block.

Select Attribute

So, the first two attribute options in Condition Settings are payment-related and are for selecting One-time Products or Subscriptions created in your Stripe account. For instance, you can use this to provide access to a given block only to the users who have purchased a specific subscription.

Select Condition

There are three conditions available:

  • is one of –the Attribute is any of the Value(s) (multiple values can be added)

  • is none of – the Attribute is any other value apart from the selected Value(s) (multiple values can be added)

  • has all of – the Attribute has all the Value(s) (multiple values can be added)

Payment-related condition options

Payment-related condition options

Select Value

Finally, you need to add the values for which the defined condition should work. For One-time Product and Subscription attributes you should see a list of values based on what you have created on Stripe. You can select as many values as needed.

List of values

List of values

In the example provided below, a condition is defined so that all the users that have purchased the “Advanced JavaScript Course” product, have access to the block, which could be a List block with JavaScript video tutorials.

One-time Product condition defines

One-time Product condition defines

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.