Skip to content
The Library

Managing Sales

This guide covers the supported purchase lifecycle: public checkout creates a pending purchase and download token; a verified Stripe webhook completes or fails it; completed purchases use tokenized retrieval and fresh Dropbox download links.

What You Need Before You Start

Section titled “What You Need Before You Start”

Before you can sell licenses, two things need to be in place.

Dropbox Connection

All file delivery happens through Dropbox. When someone purchases a license, The Library generates temporary download links from your Dropbox account and sends them to the buyer. This means you must connect your Dropbox account before licensing can work.

If you haven’t connected Dropbox yet, you’ll see a prompt in the Settings page guiding you through the OAuth connection. Keep your Dropbox linked — if it gets disconnected after you’ve enabled licensing, buyers won’t be able to download their files.

Stripe Connect Account

Payments use Stripe Connect. The public checkout verifies the seller’s Stripe and Dropbox connections, creates a pending purchase, and creates the Stripe Checkout session with the platform fee configured by the purchase service.

To connect Stripe, head to Settings → Connected Accounts and click “Connect with Stripe.” The flow creates a Stripe Connect Express onboarding session. If the platform payment configuration is unavailable, The Library reports that as a payment-provider setup issue rather than treating it as a seller-account failure.

Creating Your License Types

Section titled “Creating Your License Types”

License types define what buyers get when they purchase. Think of them as different packages — a basic lease might include MP3 and WAV files, while a premium lease adds stems and project files.

How to Create a License Type

Section titled “How to Create a License Type”
  1. Go to Settings → Licensing
  2. Click Add License Type
  3. Fill in the details:
    • Name — something like “Non-Exclusive Lease” or “Premium Package”
    • Description — a short summary buyers will see (“MP3 + WAV, up to 10k streams”)
    • Price — your desired price in dollars
    • Deliverables — check the file types you include (MP3, WAV, Stems, Project Files)
    • Exclusive? — the license configuration flag
    • Terms — optional text you provide for that license type

Use the template list as starting configuration data, then review its fields before enabling it on a track.

Managing Your Licenses

Section titled “Managing Your Licenses”

From the Licensing settings page, you can:

  • Edit any license type by clicking on it
  • Disable a license type without deleting it — existing purchases stay valid, but it won’t appear for new buyers
  • Delete a license type; if purchases exist, the service deactivates it instead

Enabling Licensing on Your Tracks

Section titled “Enabling Licensing on Your Tracks”

License types are your product catalog. Now you need to decide which tracks are for sale and at what prices.

Per-Track Licensing Settings

Section titled “Per-Track Licensing Settings”

Each track in your library can have its own licensing configuration. Open a track’s details and look for the Licensing section in the sidebar. Here you can:

  • Enable licensing for the track (this is off by default)
  • Choose which license types to offer
  • Set custom prices for individual license types (overriding the default price)

For example, you can use a different configured price for a newer track without changing the default price for other tracks.

Bulk Editing

Section titled “Bulk Editing”

Have a batch of beats you want to put up for sale at once? Use the bulk edit feature in the track grid. Select multiple tracks, then choose Enable Licensing from the action menu. You can also bulk-assign which license types should be available.

How Buyers Purchase

Section titled “How Buyers Purchase”

Public purchase starts only for an enabled license on the public track. The buyer supplies a valid email address; checkout requires seller Stripe and Dropbox connections. The service creates a pending purchase and download token before redirecting to Stripe Checkout.

A verified checkout.session.completed webhook marks the purchase complete, sets a 30-day download expiry, and sends confirmation. A verified payment failure marks the pending purchase failed.

After a Purchase

Section titled “After a Purchase”

Completed purchases can be retrieved with their download token. File requests generate fresh temporary Dropbox links while the 30-day download period remains active.

Tips

Section titled “Tips”
  • Test with friends first — before going live, have a trusted colleague purchase a license to verify your Stripe and Dropbox integrations work correctly
  • Keep your Dropbox connected — if it disconnects, buyers won’t receive their files and you’ll need to manually handle deliveries
  • Review purchase state before troubleshooting — checkout completion is established by the verified webhook, not merely a browser redirect.
Section titled “Related”