Stripe
The Stripe plugin integrates Stripe's payment and subscription functionality with Better Auth. Since payment and authentication are often tightly coupled, this plugin simplifies the integration of stripe into your application, handling customer creation, subscription management, and webhook processing.
This plugin is currently in beta. We're actively collecting feedback and exploring additional features. If you have feature requests or suggestions, please join our Discord community to discuss them.
Features
- Create Stripe Customers automatically when users sign up
- Manage subscription plans and pricing
- Process subscription lifecycle events (creation, updates, cancellations)
- Handle Stripe webhooks securely with signature verification
- Expose subscription data to your application
- Support for trial periods and subscription upgrades
- Flexible reference system to associate subscriptions with users or organizations
- Team subscription support with seats management
Installation
Install the plugin
First, install the plugin:
If you're using a separate client and server setup, make sure to install the plugin in both parts of your project.
Add the client plugin
Migrate the database
Run the migration or generate the schema to add the necessary tables to the database.
See the Schema section to add the tables manually.
Set up Stripe webhooks
Create a webhook endpoint in your Stripe dashboard pointing to:
/api/auth
is the default path for the auth server.
Make sure to select at least these events:
checkout.session.completed
customer.subscription.updated
customer.subscription.deleted
Save the webhook signing secret provided by Stripe and add it to your environment variables as STRIPE_WEBHOOK_SECRET
.
Usage
Customer Management
You can use this plugin solely for customer management without enabling subscriptions. This is useful if you just want to link Stripe customers to your users.
By default, when a user signs up, a Stripe customer is automatically created if you set createCustomerOnSignUp: true
. This customer is linked to the user in your database.
You can customize the customer creation process:
Subscription Management
Defining Plans
You can define your subscription plans either statically or dynamically:
see plan configuration for more.
Creating a Subscription
To create a subscription, use the subscription.upgrade
method:
This will create a Checkout Session and redirect the user to the Stripe Checkout page.
Important: The
successUrl
parameter will be internally modified to handle race conditions between checkout completion and webhook processing. The plugin creates an intermediate redirect that ensures subscription status is properly updated before redirecting to your success page.
For each reference ID (user or organization), only one active or trialing subscription is supported at a time. The plugin doesn't currently support multiple concurrent active subscriptions for the same reference ID.
Listing Active Subscriptions
To get the user's active subscriptions:
Canceling a Subscription
To cancel a subscription:
This will redirect the user to the Stripe Billing Portal where they can cancel their subscription.
Reference System
By default, subscriptions are associated with the user ID. However, you can use a custom reference ID to associate subscriptions with other entities, such as organizations:
Team Subscriptions with Seats
For team or organization plans, you can specify the number of seats:
The seats
parameter is passed to Stripe as the quantity for the subscription item. You can use this value in your application logic to limit the number of members in a team or organization.
To authorize reference IDs, implement the authorizeReference
function:
Webhook Handling
The plugin automatically handles common webhook events:
checkout.session.completed
: Updates subscription status after checkoutcustomer.subscription.updated
: Updates subscription details when changedcustomer.subscription.deleted
: Marks subscription as canceled
You can also handle custom events:
Subscription Lifecycle Hooks
You can hook into various subscription lifecycle events:
Trial Periods
You can configure trial periods for your plans:
Schema
The Stripe plugin adds the following tables to your database:
User
Table Name: user
Field Name | Type | Key | Description |
---|---|---|---|
stripeCustomerId | string | - | The Stripe customer ID |
Subscription
Table Name: subscription
Field Name | Type | Key | Description |
---|---|---|---|
id | string | Unique identifier for each subscription | |
plan | string | - | The name of the subscription plan |
referenceId | string | - | The ID this subscription is associated with (user ID by default) |
stripeCustomerId | string | The Stripe customer ID | |
stripeSubscriptionId | string | The Stripe subscription ID | |
status | string | - | The status of the subscription (active, canceled, etc.) |
periodStart | Date | Start date of the current billing period | |
periodEnd | Date | End date of the current billing period | |
cancelAtPeriodEnd | boolean | Whether the subscription will be canceled at the end of the period | |
seats | number | Number of seats for team plans | |
trialStart | Date | Start date of the trial period | |
trialEnd | Date | End date of the trial period |
Customizing the Schema
To change the schema table names or fields, you can pass a schema
option to the Stripe plugin:
Options
Main Options
stripeClient: Stripe
- The Stripe client instance. Required.
stripeWebhookSecret: string
- The webhook signing secret from Stripe. Required.
createCustomerOnSignUp: boolean
- Whether to automatically create a Stripe customer when a user signs up. Default: false
.
onCustomerCreate: (data: { customer: Customer, stripeCustomer: Stripe.Customer, user: User }, request?: Request) => Promise<void>
- A function called after a customer is created.
getCustomerCreateParams: (data: { user: User, session: Session }, request?: Request) => Promise<{}>
- A function to customize the Stripe customer creation parameters.
onEvent: (event: Stripe.Event) => Promise<void>
- A function called for any Stripe webhook event.
Subscription Options
enabled: boolean
- Whether to enable subscription functionality. Required.
plans: Plan[] | (() => Promise<Plan[]>)
- An array of subscription plans or a function that returns plans. Required if subscriptions are enabled.
requireEmailVerification: boolean
- Whether to require email verification before allowing subscription upgrades. Default: false
.
authorizeReference: (data: { user: User, session: Session, referenceId: string, action: "upgrade-subscription" | "list-subscription" | "cancel-subscription" }, request?: Request) => Promise<boolean>
- A function to authorize reference IDs.
Plan Configuration
Each plan can have the following properties:
name: string
- The name of the plan. Required.
priceId: string
- The Stripe price ID. Required unless using lookupKey
.
lookupKey: string
- The Stripe price lookup key. Alternative to priceId
.
annualDiscountPriceId: string
- A price ID for annual billing with a discount.
limits: Record<string, number>
- Limits associated with the plan (e.g., { projects: 10, storage: 5 }
).
group: string
- A group name for the plan, useful for categorizing plans.
freeTrial: Object containing trial configuration:
- days:
number
- Number of trial days. - onTrialStart:
(subscription: Subscription) => Promise<void>
- Called when a trial starts. - onTrialEnd:
(data: { subscription: Subscription, user: User }, request?: Request) => Promise<void>
- Called when a trial ends. - onTrialExpired:
(subscription: Subscription) => Promise<void>
- Called when a trial expires without conversion.
Advanced Usage
Using with Organizations
The Stripe plugin works well with the organization plugin. You can associate subscriptions with organizations instead of individual users:
Make sure to implement the authorizeReference
function to verify that the user has permission to manage subscriptions for the organization:
Custom Checkout Session Parameters
You can customize the Stripe Checkout session with additional parameters:
Tax Collection
To enable tax collection:
Troubleshooting
Webhook Issues
If webhooks aren't being processed correctly:
- Check that your webhook URL is correctly configured in the Stripe dashboard
- Verify that the webhook signing secret is correct
- Ensure you've selected all the necessary events in the Stripe dashboard
- Check your server logs for any errors during webhook processing
Subscription Status Issues
If subscription statuses aren't updating correctly:
- Make sure the webhook events are being received and processed
- Check that the
stripeCustomerId
andstripeSubscriptionId
fields are correctly populated - Verify that the reference IDs match between your application and Stripe
Testing Webhooks Locally
For local development, you can use the Stripe CLI to forward webhooks to your local environment:
This will provide you with a webhook signing secret that you can use in your local environment.