Architecture Overview
The payment system is designed with a multi-tenant architecture where each project can have its own Stripe configuration:API Groups
Payments (Aggregated)
Cross-project payment data for developers to view all subscriptions and transactions across their projects.Stripe Configuration
Developer-facing endpoints for configuring Stripe credentials per project.Stripe Checkout
Create Stripe checkout sessions for subscription or one-time payments.Stripe Webhooks
Receive and process webhook events from Stripe.Stripe Subscriptions (End User)
End-user facing endpoints for managing their own subscriptions.Authentication
Payment endpoints use different authentication methods based on the user type:Test vs Live Mode
All Stripe endpoints support both test and live modes:- Test Mode: Uses test API keys (prefix
sk_test_/pk_test_), simulated payments - Live Mode: Uses live API keys (prefix
sk_live_/pk_live_), real payments
test_mode query parameter controls which mode is used (defaults to true for safety).
Quick Start
1. Configure Stripe Credentials
First, add your Stripe API keys to your project:2. Get Webhook URLs
Configure webhooks in your Stripe dashboard:3. Create Checkout Session
Create a checkout session for end users:Webhook Events
The following Stripe webhook events are processed:Related Documentation
Stripe Integration Tutorial
Step-by-step guide to integrating Stripe
Cloud Admin Payments
View payment analytics in Cloud Admin
Security Best Practices
Secure your payment integration
Environment Variables
Configure payment settings

