Stripe Integration Setup

Overview

Event Schedule supports Stripe for payment processing, but the setup varies depending on how you're using the platform. This guide is organized by user type to help you find exactly what you need.

Choose Your Setup

Find your setup type and follow the corresponding guide:

For Selfhosted Users

If you're running your own Event Schedule instance for your organization, venue, or community, all ticket payments go to a single Stripe account that you control.

1. Get Your Stripe API Keys

1. Go to the Stripe Dashboard
2. Navigate to Developers → API keys
3. Note your Publishable key and Secret key

2. Configure Environment Variables

Add these to your .env file:

# Stripe Direct Payments (selfhosted)
STRIPE_PLATFORM_KEY=pk_live_your_publishable_key
STRIPE_PLATFORM_SECRET=sk_live_your_secret_key
STRIPE_PLATFORM_WEBHOOK_SECRET=whsec_your_webhook_secret

• STRIPE_PLATFORM_KEY: Your publishable key (starts with pk_live_ or pk_test_)
• STRIPE_PLATFORM_SECRET: Your secret key (starts with sk_live_ or sk_test_)
• STRIPE_PLATFORM_WEBHOOK_SECRET: Webhook signing secret (next step)

3. Set Up Webhooks

1. In Stripe Dashboard, go to Developers → Webhooks
2. Click Add endpoint
3. Set URL to: https://yourdomain.com/stripe/webhook
4. Select event: checkout.session.completed
5. Save and copy the Signing secret to STRIPE_PLATFORM_WEBHOOK_SECRET

4. Enable Stripe for Events

Once configured, event creators can select "Stripe" as the payment method when creating events with tickets. All payments automatically use your platform Stripe account.

How Checkout Works

1. Customer selects tickets and fills out the checkout form
2. Event Schedule creates a Stripe Checkout Session
3. Customer completes payment on Stripe's hosted page
4. Webhook confirms payment and marks the sale as paid
5. Customer receives their tickets

For SaaS Operators

If you're running your own white-label SaaS platform (like eventschedule.com but with your own branding), you need two Stripe integrations:

1. Enable Stripe Connect

1. Go to the Stripe Dashboard
2. Navigate to Settings → Connect → Settings
3. Enable Connect for your platform
4. Configure your branding and platform profile
5. Get your API keys from Developers → API keys

2. Environment Configuration

# Stripe Connect (for event creators to receive ticket payments)
STRIPE_KEY=sk_live_your_stripe_secret_key
STRIPE_WEBHOOK_SECRET=whsec_your_connect_webhook_secret

• STRIPE_KEY: Your platform's Stripe secret key
• STRIPE_WEBHOOK_SECRET: Webhook secret for Connect events

3. Webhook Configuration

1. Go to Developers → Webhooks
2. Click Add endpoint
3. Set URL to: https://yourdomain.com/stripe/webhook
4. Select event: payment_intent.succeeded
5. Save and copy the signing secret to STRIPE_WEBHOOK_SECRET

User Onboarding Flow

Your event creators will:

1. Go to Profile → Payment Methods
2. Click "Connect Stripe Account"
3. Complete Stripe's onboarding
4. Return to your platform ready to sell tickets

Connect API Endpoints

1. Create Subscription Products

1. In Stripe Dashboard, go to Products → Add product
2. Create a "Pro Plan" product with:
   • Monthly price (e.g., $9.99/month, recurring)
   • Yearly price (e.g., $99.99/year, recurring)
3. Note the Price IDs (starts with price_)

2. Environment Configuration

# Laravel Cashier (for subscription billing)
STRIPE_PLATFORM_KEY=pk_live_your_publishable_key
STRIPE_PLATFORM_SECRET=sk_live_your_secret_key
STRIPE_PLATFORM_WEBHOOK_SECRET=whsec_your_subscription_webhook_secret
STRIPE_PRICE_MONTHLY=price_monthly_price_id
STRIPE_PRICE_YEARLY=price_yearly_price_id

• STRIPE_PLATFORM_KEY: Publishable key for your platform
• STRIPE_PLATFORM_SECRET: Secret key for your platform
• STRIPE_PLATFORM_WEBHOOK_SECRET: Webhook secret for subscription events
• STRIPE_PRICE_MONTHLY: Price ID for monthly subscription
• STRIPE_PRICE_YEARLY: Price ID for yearly subscription

3. Subscription Webhook

1. Go to Developers → Webhooks
2. Click Add endpoint (this is a second webhook, separate from Connect)
3. Set URL to: https://yourdomain.com/stripe/subscription-webhook
4. Select events:
   • customer.subscription.created
   • customer.subscription.updated
   • customer.subscription.deleted
   • customer.subscription.trial_will_end
   • invoice.payment_succeeded
   • invoice.payment_failed
5. Save and copy signing secret to STRIPE_PLATFORM_WEBHOOK_SECRET

4. Customer Portal Setup

1. Go to Settings → Billing → Customer portal
2. Enable subscription management features:
   • Subscription cancellation
   • Plan switching
   • Payment method updates
3. Customize branding to match your platform

Subscription API Endpoints

Testing

Test Mode Setup

For development and testing:

1. Toggle to "Test mode" in the Stripe Dashboard
2. Use test API keys (starting with pk_test_ and sk_test_)
3. Create test webhook endpoints pointing to your development environment

Test Card Numbers

Use any future expiration date and any 3-digit CVC.

Testing Webhooks Locally

Use the Stripe CLI to forward webhooks:

# Install Stripe CLI
brew install stripe/stripe-cli/stripe

# Login to your Stripe account
stripe login

# Forward webhooks (selfhosted or Connect)
stripe listen --forward-to localhost:8000/stripe/webhook

# For SaaS: Forward subscription webhooks (separate terminal)
stripe listen --forward-to localhost:8000/stripe/subscription-webhook

The CLI displays a webhook signing secret to use in your .env file.

Trigger Test Events

# Test checkout completion (selfhosted)
stripe trigger checkout.session.completed

# Test payment success (Connect)
stripe trigger payment_intent.succeeded

# Test subscription creation
stripe trigger customer.subscription.created

Troubleshooting

Common Issues

Debugging Logs

• Application: storage/logs/laravel.log
• Stripe API: Dashboard → Developers → Logs
• Webhooks: Dashboard → Developers → Webhooks → Select endpoint → View logs

Security

1. API Key Security: Never expose secret keys in client-side code or version control. Use environment variables.
2. Webhook Verification: Always verify webhook signatures—Event Schedule does this automatically.
3. HTTPS Required: Stripe requires HTTPS for webhook endpoints in production.
4. PCI Compliance: Using Stripe Checkout and Elements keeps you out of PCI scope—card data never touches your server.