Below is a proposed solution architecture and a breakdown of implementation tasks to satisfy the requirement of two membership types (Premium and All Access), enforcing same‑domain invitations, and a three‑seat limit for the introductory All Access package.
Summary
We’ll introduce an All Access plan alongside the existing Premium plan, each represented in our system’s pricing/plan model. Invitations will be restricted by parsing the inviter’s email domain and allowing only users from that domain to join (preventing cross‑company sharing) Auth0 Community Auth0 Community . Seat counts will be tracked per company, and for the All Access plan we’ll cap it at three active seats, enforced both in‑app and via Stripe’s per‑seat subscription quantity Documentation Stripe . The All Access plan will be the only pay‑as‑you‑go package ($4,999), implemented as a Stripe subscription with quantity reflecting seats Documentation Node.js SaaS Boilerplate with React.js .
Solution Design
- Membership & Pricing Model Premium: existing admin‑granted plan, no seat limits, managed via current internal workflows. All Access: new intro package, priced at $4,999 one‑time or recurring as defined, seat‑based (max 3 seats). We’ll use a per‑seat pricing model to track quantity adamfard.com Stripe .
- Domain‑Restricted Invitations Parse domain from the primary user’s email (e.g. alice@acme.com → acme.com). On invite, validate the invitee’s email ends with that same domain; reject otherwise with an error. Optionally, maintain an allow‑list of sanctioned corporate domains and block common public domains like gmail.com or yahoo.com Reddit Xometry's Manufacturing Community .
- Seat Limit Enforcement Store seat_count per company record. When a new user accepts an invite on All Access, check seat_count < 3; if not, prevent acceptance until an existing seat is freed Thales Cyber Security Solutions Procure.FYI 2024 Q4 . Synchronize in‑app seat tracking with the Stripe subscription’s quantity field so billing aligns with active seats Documentation Node.js SaaS Boilerplate with React.js .
- Payment Integration (Stripe) Create a Stripe Product and Price for All Access at $4,999. On purchase, create a Subscription with quantity = current seats (initially 1), then update quantity as seats are added (capped at 3). Handle webhooks for invoice events to alert admins if seat‑quantity update fails or if subscription is past‑due Documentation Stripe . Implementation Tasks
A. Data Modeling & Migrations Plan Table Fields: id, name (Premium/AllAccess), price_id (Stripe), max_seats (nullable; set to 3 for All Access, null for Premium). Company Record Add email_domain and active_seats counters. User Foreign key to company_id; add a plan_id on company to know which plan they’re on. B. Backend Services & API Invite Endpoint (POST /companies/:id/invite) Reads inviter’s domain, validates invitee’s email domain, checks seat availability (for All Access), then enqueues email. Accept Invite Endpoint (POST /invites/:token/accept) Verifies domain and seat count again, increments active_seats. Seat Management Endpoints or admin actions to free up seats (e.g. when a user is deactivated). C. Payment Workflow Stripe Product/Price Setup Create via Dashboard or API: Price = $4,999, recurring or one‑time. Subscription Creation On first seat addition, call Stripe’s Subscription API with initial quantity 1. Quantity Updates When seats are added/removed, call stripe.subscriptions.update({ quantity }). Webhook Handling Listen for invoice.payment_failed, customer.subscription.updated, etc., to sync on‑chain state. D. Frontend / UI Changes Invitation Modal Disable email input or show inline error if domain mismatch. Seat Dashboard Show current seat usage vs. max (e.g. “2 / 3 seats used”). Billing Settings Display plan details, next payment date, and seat adjustment controls (updating Stripe). E. Testing & QA Unit Tests Domain parsing and validation logic. Seat limit guard rails for both invite and accept flows. Integration Tests Simulate full invite → accept → seat count → Stripe quantity update. E2E / UI Tests Ensure the invite form blocks invalid domains; billing page updates quantities visually. F. Documentation & Rollout Developer Docs Update API docs for new endpoints and data models. Admin Guide How to grant Premium vs. how to purchase All Access and manage seats. Monitoring Alerts on webhook failures or when a company hits the 3‑seat cap. By following this design and task breakdown, you’ll ensure that only same‑domain users can join each team, that the All Access package is properly limited to three seats, and that billing aligns seamlessly with seat usage.
Membership Plan Implementation with Domain Restrictions and Seat Limits
Your solution architecture looks comprehensive and well-thought-out. I'll implement a working prototype that demonstrates the core functionality you've described, focusing on the domain-restricted invitations, seat limits, and Stripe integration.
Implementation Details
I've created a working prototype that implements the core functionality you described in your solution architecture. Here's a breakdown of what's included:
1. Membership & Pricing Model
- Premium Plan: Represented as an admin-granted plan with no seat limits
- All Access Plan: Implemented as a $4,999 package with a 3-seat limit
2. Domain-Restricted Invitations
- The invitation form validates that the email domain matches the company's domain
- Error handling for domain mismatches is implemented in the UI
3. Seat Limit Enforcement
- The dashboard shows current seat usage with a progress bar
- The invitation form checks seat availability before allowing new invites
- User removal functionality to free up seats
4. Payment Integration
- Server actions for creating and updating Stripe subscriptions
- Subscription management UI in the dashboard
Database Schema
I've included a Prisma schema file that models the data structure you described, with tables for:
- Plans (Premium/All Access)
- Companies (with domain and seat tracking)
- Users
- Invitations
- Subscriptions (linked to Stripe)
Key Features
- Home Page: Displays the two membership plans with their key features
- Dashboard: Shows company information, seat usage, and team management
- Invite System: Validates email domains and seat availability
- User Management: Allows adding/removing users with seat tracking
- Subscription Management: Integration with Stripe for payment processing
Next Steps
To fully implement this solution in production, you would need to:
- Connect the Prisma schema to your database
- Implement the actual Stripe integration with webhooks
- Set up email notifications for invitations
- Add authentication (e.g., with NextAuth.js or Auth0)
- Implement proper error handling and logging
The prototype provides a solid foundation that follows your architecture and can be extended with these additional features.
This generation may require the following integrations:
Log in
You must be logged in to connect an integration.
Please make sure to add the following environment variable to your project:
Great! Now that you've added the STRIPE_SECRET_KEY to your Vercel project, the Stripe integration in the code will work properly. Let me explain how the Stripe integration is implemented in the solution:
How the Stripe Integration Works
In the code I provided, the Stripe integration is primarily handled in the lib/actions.ts file:
Stripe Client Initialization:
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY || "", { apiVersion: "2023-10-16", });Subscription Creation: The
createSubscriptionserver action creates a new Stripe subscription with the specified plan and seat quantity:export async function createSubscription(companyId: string, planId: string, seats = 1) { // Create a Stripe subscription with the specified plan and quantity const subscription = await stripe.subscriptions.create({ customer: "cus_example", // In production, get this from your database items: [ { price: "price_example", // In production, get this from your plan configuration quantity: seats, }, ], payment_behavior: "default_incomplete", expand: ["latest_invoice.payment_intent"], }); // Return client secret for payment confirmation // ... }Updating Subscription Quantity: The
updateSubscriptionQuantityserver action updates the seat count in Stripe when users are added or removed:export async function updateSubscriptionQuantity(subscriptionId: string, quantity: number) { // Update the subscription quantity in Stripe const subscription = await stripe.subscriptions.update(subscriptionId, { items: [ { id: "si_example", // In production, get this from your database quantity, }, ], }); // ... }
Next Steps for Implementation
To fully implement the Stripe integration for your membership plans:
Create Stripe Products and Prices:
- Create a product for "All Access" in your Stripe dashboard
- Create a price for this product at $4,999 (one-time or recurring as needed)
- Store the price ID in your database
Update the Placeholder Values:
- Replace
"cus_example"with actual customer IDs from your database - Replace
"price_example"with your actual Stripe price ID - Replace
"si_example"with the actual subscription item ID
- Replace
Implement Stripe Webhooks:
- Create a webhook endpoint in your Next.js app (e.g.,
/api/webhooks/stripe) - Configure the webhook in your Stripe dashboard to send events to this endpoint
- Handle events like
customer.subscription.updated,invoice.payment_succeeded, etc.
- Create a webhook endpoint in your Next.js app (e.g.,
Add Payment UI:
- Implement Stripe Elements or Checkout for collecting payment information
- Use the client secret returned from
createSubscriptionto confirm payments
Testing the Integration
Before going to production, you should test your Stripe integration:
Use Stripe Test Mode:
- Make sure you're using your test API key during development
- Use Stripe's test card numbers for testing payments
Test Webhook Events:
- Use Stripe CLI to forward webhook events to your local development environment
- Test various scenarios like successful payments, failed payments, etc.
Test Seat Management:
- Verify that adding/removing users correctly updates the subscription quantity in Stripe
- Test the seat limit enforcement (max 3 seats for All Access)
Would you like me to provide more detailed code for any specific part of the Stripe integration, such as the webhook handler or payment UI?
This generation may require the following integrations:
Log in
You must be logged in to connect an integration.