> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beatpass.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# License Certificates

> Understanding the license certificates issued when your beats are licensed.

BeatPass generates a license certificate whenever someone receives a qualifying BeatPass license for your beat. Certificates are important because they capture the exact terms granted, the track identity, and the verification link used to prove the license exists.

## When BeatPass Creates a Certificate

BeatPass creates certificates for:

* Standard BeatPass downloads that generate a non-exclusive license
* Exclusive purchases that generate an exclusive license

<Note>
  If you download your own track as the owner, BeatPass does not issue a new license certificate for that owner download.
</Note>

## What a Certificate Includes

The current BeatPass certificate format includes:

* **License ID / certificate ID**
* **Track details** such as title and release data
* **License type** (`non-exclusive` or `exclusive`)
* **Licensed user details**
* **License terms**
* **Audio fingerprint details**
* **Verification URL**

## Fingerprint Details on the Certificate

BeatPass certificates currently include fingerprint-related data such as:

* Fingerprint status
* Fingerprinted date
* Analyzed duration
* Fingerprint hash

The docs should describe these as verification details, not as a promise of any specific algorithm or security marketing claim that is not surfaced by the current product.

## Standard vs Exclusive Certificates

### Standard Certificates

BeatPass standard certificates currently document terms such as:

* Non-exclusive
* Worldwide
* Perpetual
* One original musical work per download
* Attribution required
* No Content ID registration
* No film, TV, broadcast radio, commercials, or video games
* Live performances up to 50 attendees

### Exclusive Certificates

Exclusive certificates currently document the terms saved on the beat at the moment of sale, including:

* Publishing split
* Territory
* Governing law country
* Usage rights
* Files to deliver
* Producer royalty
* Content ID permission, when enabled

## How Verification Works

Every certificate includes a public BeatPass verification URL.

<Steps>
  <Step title="Open the verification link">
    Use the URL printed on the certificate.
  </Step>

  <Step title="BeatPass checks the certificate">
    BeatPass confirms the license exists and returns the stored certificate details.
  </Step>

  <Step title="Use the result as proof">
    Buyers, distributors, labels, and producers can use the verification page to confirm the certificate is legitimate.
  </Step>
</Steps>

## What This Means for Producers

Certificates help you because they:

* Record the exact rights BeatPass granted
* Preserve the sold terms for exclusive purchases
* Make it easier to resolve disputes about authorized use

They also matter after exclusive sales because earlier BeatPass non-exclusive certificates remain valid if they were issued before the beat was sold exclusively.

## Practical Rules to Remember

* You do not manually draft BeatPass certificates
* Issued certificates reflect the terms in force at the time they were created
* Selling a beat exclusively does not erase older standard certificates that were already issued

## Related

<CardGroup cols={2}>
  <Card title="Non-Exclusive Licenses" href="/help/licensing-for-producers/non-exclusive-licenses" icon="users">
    Review the current standard certificate terms.
  </Card>

  <Card title="Exclusive Licenses" href="/help/licensing-for-producers/exclusive-licenses" icon="crown">
    Configure the terms BeatPass will write into exclusive certificates.
  </Card>
</CardGroup>