Initial draft of paid content #1028

thomasgwatson · 2025-10-21T07:06:41Z

I want to get initial feedback on the migration.

The stripe connect guide allows you to select a few different options to model your overall use-case and then it generates a prompt for a coding assistant. I tweaked the prompt a little more and its generated a lot of code-changes and a lot of TODOs. But so far it looks like a decent start.

I want to be fairly measured about pulling in the changes piece by piece tho, and starting with the migration stuff

tibetsprague

looks good so far

tibetsprague · 2025-10-21T19:58:03Z

apps/backend/migrations/20251020160838_paid-content-stripe.js

+      table.bigInteger('group_id').unsigned().notNullable().references('id').inTable('groups')
+      table.bigInteger('product_id').unsigned().references('id').inTable('stripe_products')
+      table.bigInteger('track_id').unsigned().references('id').inTable('tracks')
+      table.integer('role_id').unsigned().references('id').inTable('groups_roles')


what is the role for here?

A group has three membership options. The basic option just gets you access to the group. The next two options get to access to the group and a specific role. The role is either a cosmetic buff or it actually 'unlocks' some sort of content.

tibetsprague · 2025-10-21T19:59:29Z

apps/backend/migrations/20251020160838_paid-content-stripe.js

+      table.string('stripe_session_id', 255)
+      table.string('stripe_payment_intent_id', 255)
+      table.integer('amount_paid').defaultTo(0) // 0 for free grants
+      table.string('currency', 3).defaultTo('usd')


all currencies are 3 characters for sure? what about cryptos?

Looks like it;
https://docs.stripe.com/currencies

I have seen some reference to users being able to pay with crypto but its not on the currencies page (?)

As far as I understand at the moment, these aspects of the transaciton info in our database will not the source of truth; that will be the transaction on stripe's side.

And to this end, I have actually removed them. We will list transactions in our interface but basically all details for them will stay with stripe and we would just link to them from our UI

thomasgwatson · 2025-10-23T04:53:57Z

docs/PAID_CONTENT_WORKFLOW.md

+
+This document provides a comprehensive walkthrough of the entire paid content workflow, from admin setup to user purchase completion.
+
+## Table of Contents


@tibetsprague give this a look and see if it makes sense to you as a workflow

thomasgwatson · 2025-10-23T05:02:18Z

@tibetsprague ok, so here is another round of changes.

A few updates to the migration:

function to sync content with the expired_at value of its content_access record
Added expired_at to the various pieces of content that can be gated, for quick reference when we are checking access through the platform
added json field on products to define what things are permitted when someone buys something

Also added a workflow explainer markdown file, that you should check to make sure the workflow sounds sensible

tibetsprague

looking good so far!

tibetsprague · 2025-10-23T22:08:27Z

apps/backend/api/controllers/StripeController.js

+      }
+
+      // Find the group with this Stripe account ID
+      const group = await Group.where({ stripe_account_id: account.id }).fetch()


can multiple groups use the same stripe account? probably. i wonder if there is another identifier for like a sub-account or something like that? or maybe they just give separate account_ids for each one.

ooo right that is an interesting question. This is a webhook, so I will have to check if we can store a 'foreign key' of sorts from our db in their records for an account. I assume we can

tibetsprague · 2025-10-23T22:11:41Z

apps/backend/api/graphql/mutations/stripe.js

+      }
+
+      // Check if group already has a Stripe account
+      // TODO STRIPE: You may want to store the accountId in your Group model


ok so it seems like each group will have its own "account"

tibetsprague · 2025-10-23T22:12:49Z

apps/backend/api/graphql/makeModels.js

      model: MemberGroupRole,
      attributes: [
        'id',
+        'expires_at',


intriguing, so this would be for a product that gives you a certain role?

For example: for the astrology group, they define three tiers of membership with different subscription rates.

So each of those tiers could provide a role/badge that is unique to them. I don't think we have it specced at the moment but in the future this could be used to gate chat rooms or perhaps even specific content or be another way to unlock access to a track. And those role grants don't need to be paid for either; in general, groups might want to restrict content to specific roles

tibetsprague · 2025-10-23T22:14:31Z

apps/backend/api/graphql/schema.graphql

 type Track {
  id: ID
+  # Whether this track requires purchased access (paid content)
+  accessControlled: Boolean


seems like we should call this the same thing we call it on group, so either both are paywall (or paywalled?) or both are accessControlled. i lean towards paywalled

So groups already have a property and concept related to restricted access but tracks don't. So the properties, despite both being booleans and having some conceptual overlap, don't have the same scope. So I don't want to give them the same name and thus infer that they have the same scope.

The doc note here is outdated; admins can grant access without a payment or stripe being involved.

tibetsprague · 2025-10-23T22:16:13Z

apps/backend/api/models/StripeProduct.js

+        }
+      }
+
+      // Add role-specific access records


still a little unclear on this. this means that everyone with this role gets access to this thing? or that people with this content get this role?

tibetsprague · 2025-10-23T22:20:11Z

docs/CONTENT_ACCESS_SUMMARY.md

+**When access is revoked or expires:**
+1. Status changes to 'revoked' or 'expired' in `content_access`
+2. Trigger `content_access_expires_at_clear` fires
+3. Function `clear_content_access_expires_at()` executes:


so it always has an expires_at value if content is accessible? and for lifetime we just put one far in the future?

tibetsprague · 2025-10-23T22:20:42Z

docs/CONTENT_ACCESS_SUMMARY.md

+// Creates: content_access { user_id, group_id, expires_at: '2026-01-01', track_id: NULL }
+// Trigger updates: group_memberships.expires_at = '2026-01-01' ✓
+
+// Step 2: Same user buys 1-month access to Track A (3 months later)


i think racks will always be lifetime?

tibetsprague · 2025-10-23T22:23:17Z

docs/PAID_CONTENT_WORKFLOW.md

+   - Email includes:
+     - Purchase confirmation details
+     - Links to access the content they purchased
+     - Instructions for accessing their new content


a special group link that sets up the access? or already they will have been marked as being able to access the group in the database so then its just the normal group link

maybe "specific" is a better word than "special" here; a specific link to the content.

So, this is worth checking in about and there is still a bit of gray area based on exactly how the stripe hand-off goes:

Say, we are a user, in the stripe checkout and I hit purchase.

I think then stripe redirects the user to the successUrl that we provide.

Meanwhile, there is an async update between Stripe (via webhook) and us, letting us know that the payment worked out

So, I am thinking that we made the successUrl pretty generic and simple and more or less just say: check your email

this saves us if there is a significant lag between transaction and webhook update.... but if it turns out that turn-around time is really fast (consistently?) then we are just adding another step (checking the email) for the user...

Any initial thoughts? Might just be something we figure out once we start seeing it implemented

…separately, instead of implicitly assuming they are the same

…tus; add link to stripe dashboard for connected accounts

…dation for group paywall toggle

…iptions

…iptions via the Stripe portal

gitguardian · 2026-01-07T05:10:24Z

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

…actually work

…nto 604-paid-content

…ion queries

… stripe offering records

… for agreements if they are already done

Initial draft of db migration

49f35f8

tibetsprague reviewed Oct 21, 2025

View reviewed changes

thomasgwatson added 2 commits October 22, 2025 14:57

Deeper tweaks to migration

8d67ead

Paid content backend, without actual access control

25b8d53

thomasgwatson changed the title ~~Initial draft of db migration~~ Initial draft of paid content backend Oct 23, 2025

thomasgwatson commented Oct 23, 2025

View reviewed changes

tibetsprague reviewed Oct 23, 2025

View reviewed changes

thomasgwatson added 19 commits October 24, 2025 10:28

Ensure we pass group id as metadata on stripe connect account creation

57aa2bb

Refined backend

8e35035

Get tests *runnnig* but not yet passing

002a2c8

wip web changes

f83c0d3

Merge branch 'fix-backend-tests-v3' into 604-paid-content

43b2993

Merge branch 'fix-backend-tests-v3' into 604-paid-content

dc65148

Stripe mutations tests all passing

d08ad7f

Content access mutation tests passing

f925889

Switch connect access to track granting group and permissioned group …

da4d0ed

…separately, instead of implicitly assuming they are the same

Sync schema with queries

de7a335

Merge branch 'fix-backend-tests-v3' into 604-paid-content

6ad40bc

Allow group admins to create stripe account; add check for stripe sta…

16a7e15

…tus; add link to stripe dashboard for connected accounts

Merge branch 'dev' into 604-paid-content

2741504

Switch from product to offering for paid content descriptor

b8d685c

Use correct host for links

b37bef4

Merge conflict syntax errors missed in the conflict resolution

9968bb8

Expand paid content sub-tabs in the group settings

983b839

Clean up stripe account connection

7b3de54

Allow offers to be created; display existing offerings; start of vali…

919ed81

…dation for group paywall toggle

lorenjohnson temporarily deployed to hylo-node-staging November 6, 2025 06:57 Inactive

lorenjohnson temporarily deployed to hylo-evo-staging November 6, 2025 06:58 Inactive

Merge branch 'dev' into 604-paid-content

e4dadfb

thomasgwatson added 8 commits January 2, 2026 10:56

Allow admins to invite users to their group AND add a role

d22466f

Add my transactions to user menu, and display transactions and subscr…

ebf63d8

…iptions

Update backend readme with stripe details

8acbf11

Allow users to see their transaction/subscriptions, and manage subscr…

78cfc37

…iptions via the Stripe portal

Merge branch 'dev' into 604-paid-content

15dd17f

Add optional donations to hylo transactions

a264967

Add emails to many of the paid content actions

ee45f42

Merge branch 'color-scheme' into 604-paid-content

fe6d062

thomasgwatson and others added 21 commits January 8, 2026 11:57

Update offering urls to redirect to the about page

e6d7fc0

Update test scenarios and add one day subscriptions

c33afe6

Add revoke button for content access records

86964e4

disable donations for now

ab03164

Try to fix staging again

7faec33

Fix staging

f2449c3

Add set donation line item for hylo donations

2db9570

Renable refunds with the correct logic

da90aa4

Remove conditional for offerings create/edit ui

cd95ba9

Flesh out the paid content interactions with roles to make sure they …

6caeeee

…actually work

Merge branch 'dev' into 604-paid-content

9304792

Merge branch 'dev' into 604-paid-content

83d2e83

Merge branch '604-paid-content' of https://github.com/Hylozoic/hylo i…

c08b04a

…nto 604-paid-content

Add filters to user transactions list

a87433d

Add filters to my transactions user tab; re-position tab in user menu

03bb536

Further fixes to how roles are handled by content access and transact…

2317ce7

…ion queries

Further tweaks to how roles are handled by content access records and…

274748c

… stripe offering records

Fix tracks enrollment display logic in TrackHome view

d639b7d

Fix join flow; actually save pre-answered join questions and dont ask…

a0228b2

… for agreements if they are already done

PAID CONTENT: Ensure membership is created before roles are granted

86c4e17

Improve UX of My transactions and the filters

816adb3


		This document provides a comprehensive walkthrough of the entire paid content workflow, from admin setup to user purchase completion.

		## Table of Contents

Uh oh!

Initial draft of paid content #1028

Are you sure you want to change the base?

Initial draft of paid content #1028

Uh oh!

Conversation

thomasgwatson commented Oct 21, 2025

Uh oh!

tibetsprague left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

thomasgwatson commented Oct 23, 2025

Uh oh!

tibetsprague left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gitguardian bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

️✅ There are no secrets present in this pull request anymore.

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

gitguardian bot commented Jan 7, 2026 •

edited

Loading