Growth Source edition 1.0.4
Funnel and Revenue
Remember the person behind the purchase.
Keep customer identity and progress together from email capture to Stripe Checkout, then grant access from current payment and subscription records.
Example scenario
From newsletter signup to paid access
A reader signs up for your free newsletter and later chooses a paid membership. Keep the same customer record through Checkout, then let your app read confirmed access after payment reconciliation.
From setup to the result
- Capture the customer and retain their progress.
- Queue a checkout using a configured price and amount.
- Verify Stripe events and retrieve current payment state.
- Read confirmed access, payment problems, and recovery history.
What the package handles
What you can build with it
- Persistent email/customer records and expiring continuation tokens.
- Hosted Checkout for configured fixed-price offers.
- Provider reconciliation, subscription expiry, and refund/dispute holds.
Supported behavior
- One-time and flat subscription Checkout; fixed expected amounts; one quantity per funnel checkout.
- Snapshot webhook events verified by the shared raw-body endpoint; current Stripe retrieval drives access.
- Persistent email/customer mapping and authenticated expiring continuation tokens.
Before you choose
Will it fit your project?
Who it is for
- Founders selling a subscription or digital product.
- Teams repairing a signup journey that loses progress between steps.
- Businesses that need payment status and product access to agree.
Runtime and connections
Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.
Depending on the features you enable, setup can require your own Stripe accounts and credentials. Their usage, plans and transaction charges are separate from the source purchase. Check the supported behavior below before choosing a connection.
A useful handoff to your coding agent
How setup works
The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.
- Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
- Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
- Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.
Questions to prepare
- Which fixed Stripe prices, expected amounts, currencies, and checkout modes should be supported?
- Where do customers return, and how long should continuation tokens last?
- Which trusted application verifies customer identity before calling the service?
What your agent checks
- Resume the same authenticated customer without duplicating records.
- Complete the fixture checkout and inspect access before and after reconciliation.
- Check repeated events, failed payment, cancellation, refund, and wrong-customer access.
Scope of this edition
Important limits
Fixed expected Checkout amounts and currencies. The surrounding app authenticates customers; a continuation token is not a login. Stripe accounts, webhook configuration, tax decisions, and processing costs remain with the business.
- No tax, discounts, arbitrary trial setup, usage billing, refunds initiation, or outbound marketing.
- A continuation token resumes state; the surrounding application must authenticate its customer and verify email where required.
- Partial refunds, disputes, and fraud warnings conservatively hold account access until owner review. Maximum 100 checkouts and 100 risk resources per account before maintenance.
Before you decide
Will this work with my existing app?
The package runs on Node.js 22.13+ and PostgreSQL 17. Your coding agent connects it to your application using the included integration guide and supported interfaces. Check the requirements, supported behavior and limits on this page; compatibility with every framework or hosting provider is not promised.
What will my agent need from me?
Your goals, the relevant app details and permission to configure your own accounts. The setup questions on this page help prepare that handoff. Keep credentials in your own private environment; do not paste secrets into a public support request.
What happens if setup fails?
The package includes verification and troubleshooting resources so your agent can inspect the failure and resume the documented setup. Initial setup and reproducible-defect support lasts 30 days from purchase. The refund policy covers material defects we cannot fix, alongside applicable statutory rights.
Is this a subscription?
Helpful Mods sells the source package once. There is no monthly maintenance subscription or automatic renewal. Hosting and connected services have their own costs. Optional major upgrades require a separate purchase.
Can I buy this now?
Purchases are not open yet. You can inspect the product information and use the library planner while checkout is being prepared. A plan is not an order and does not grant source access.