Subscriptions in Pegasus have three components which must all be setup in order for them to work correctly.

  1. Stripe Billing data. This is configured in Stripe.
  2. Local Stripe models. These are synced automatically from Stripe to your local database, using dj-stripe.
  3. Pegasus metadata. This is configured in apps/subsriptions/ and used to augment the data from Stripe.

The easiest way to setup all three is to follow the guide below.

Getting Started

Complete the following steps in order to setup your first subscription workflow.

  1. If you haven’t already, setup Pegasus and create an account.
  2. Setup your billing plans in your Stripe test account. See Stripe’s documentation for help on doing this.
  3. Update the STRIPE_* variables in or in your os environment variables to match the keys from Stripe. See this page to find your API keys.
  4. Run ./ bootstrap_subscriptions. If things are setup correctly, you should see output that includes “Synchronized plan plan_[plan_id]” for each plan you created, and an output starting with ACTIVE_PRODUCTS = containing the products you just created.
  5. Paste the ACTIVE_PRODUCTS output from the previous step into apps/subsriptions/ overriding what is there. Update any other details you want, for example, the “description” and “features” fields.
  6. Optionally edit the ACTIVE_PLAN_INTERVALS variable in apps/subsriptions/ if you don’t plan to include both monthly and annual offerings.

Now login and click the “Subscription” tab in the navigation. If you’ve set things up correctly you should see a page that looks like this:

Subscription Example

If you want to change the contents of the page, just edit the details in Watch how the page changes when you make changes.


Webhooks are used to notify your app about events that happen in Stripe, e.g. failed payments. More information can be found in Stripe’s webhook documentation.

Pegasus ships with webhook functionality ready to go, however you are strongly encouraged to test locally using Stripe’s excellent guide.

A few pieces of setup that are required:

  • For the webhook URL, it should be The trailing slash is required. If using the Stripe CLI you can use stripe listen --forward-to localhost:8000/stripe/webhook/
  • Make sure to set DJSTRIPE_WEBHOOK_SECRET in your or environment. This value can be found when configuring your webhook endpoint in the Stripe dashboard, or read from the console output in the Stripe CLI.

Once webhooks are properly setup, all the underlying Stripe data will be automatically synced from Stripe with no additional setup on your part.

Custom Webhook Handling

You may want to do more than just update the underlying Stripe objects when processing webhooks, for example, notifying a customer or admin of a failed payment.

Pegasus ships with an example of executing custom logic from a webhook in apps/subscriptions/ This basic example will mail your project admins when a Subscription is canceled.

More details on custom webhooks can be found in the dj-stripe documentation.

Good luck collecting and managing your first subscription payments!


Pegasus ships with a demo page with a few feature-gating examples, which are available from a new Pegasus installation under the “Subscription Demo” tab.

These include:

  1. Changing content on a page based on the user/team’s subscription.
  2. Restricting access to an entire page based on the user/team’s subscription.
  3. Showing subscription details like plan, payment details, and renewal date.

For additional questions on feature-gating don’t hesitate to get in touch!