> ## 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.

# Verifying Licenses

> How to verify a BeatPass license certificate using the public verification page.

BeatPass includes a public verification page for license certificates. Anyone with the license UUID can check whether the certificate exists and whether it is currently valid.

<Info>
  Verification is public. The person checking the certificate does not need to log in.
</Info>

<Note>
  Verification confirms BeatPass's certificate record and current status. It does not guarantee that no third-party claim, AI-origin dispute, or rights-verification issue can ever arise.
</Note>

## Verification link format

Every certificate points to a URL in this format:

```text theme={"theme":{"light":"github-light","dark":"one-dark-pro"}}
https://open.beatpass.ca/verify-license/{uuid}
```

## How to verify a certificate

<Steps>
  <Step title="Get the license UUID">
    You can copy it from the certificate, the printable certificate page, or the **Licenses** area in the app.
  </Step>

  <Step title="Open the public page">
    Visit <a href="https://open.beatpass.ca/verify-license/">[https://open.beatpass.ca/verify-license/](https://open.beatpass.ca/verify-license/)</a> followed by that UUID.
  </Step>

  <Step title="Review the result">
    BeatPass returns a public status page for that specific certificate.
  </Step>
</Steps>

## What the page shows

The current public verification page shows the certificate status plus the core identity details tied to that license:

| Field                           | What it means                                                       |
| ------------------------------- | ------------------------------------------------------------------- |
| **Certificate Valid / Invalid** | High-level result shown in the page header                          |
| **License UUID**                | The certificate ID being checked                                    |
| **Track name**                  | Track tied to the license                                           |
| **Artists**                     | Credited artists on the track                                       |
| **License type**                | Standard or exclusive                                               |
| **Licensed User**               | Masked email only                                                   |
| **Issued date**                 | When the license was created                                        |
| **Status**                      | Current record status, such as `active` or another non-active state |
| **Database Verification**       | Confirms the license exists in BeatPass records                     |
| **Verification Count**          | Number of times the page has been checked                           |

<Note>
  BeatPass stores additional verification metadata internally, but the current public page focuses on the fields above rather than exposing every stored timestamp or audit detail.
</Note>

## What the page does not expose

* It does not reveal the full email address of the license holder
* It does not require the viewer to open the user account
* It does not replace reading the actual certificate terms when rights questions get specific
* It does not grant AI training, dataset, model-development, sample-pack, or competing-library rights
* It does not certify that a beat is AI-free or immune from future rights review

## Privacy boundary

Public verification is designed to prove a license without exposing unnecessary account data. It uses masked licensee information and does not reveal the account's full email address.

## Common use cases

<AccordionGroup>
  <Accordion title="For licensees" icon="user" defaultOpen>
    Use the verification page when a distributor, label, platform, or collaborator asks you to prove you have a valid license.
  </Accordion>

  <Accordion title="For producers" icon="music">
    Use it to confirm whether a downloader or buyer has an active certificate for one of your tracks.
  </Accordion>

  <Accordion title="For third parties" icon="shield">
    Use it to verify that a certificate is real before acting on a rights dispute or release review.
  </Accordion>
</AccordionGroup>

## What to send when someone asks for proof

Send:

1. The public verification URL
2. The certificate PDF or printable certificate page
3. The track title and artist name
4. The release or project name that uses the beat
5. Any distributor or platform case number, if applicable

The verification link confirms that the certificate exists in BeatPass records and shows its current status without requiring the reviewer to log in.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The page says the license was not found" icon="triangle-exclamation" defaultOpen>
    Double-check the UUID. A bad or incomplete UUID is the most common cause.
  </Accordion>

  <Accordion title="The page says the license is revoked" icon="ban">
    The certificate exists, but it is no longer valid. The public page still helps confirm that the UUID is real, while the status badge tells you the license is not active.
  </Accordion>

  <Accordion title="The page shows review or rights issue status" icon="triangle-exclamation">
    A review, dispute, or rights-issue status means BeatPass has identified a license, rights, compliance, AI-origin, or verification issue that may require support. It does not automatically mean the buyer acted wrongly.
  </Accordion>

  <Accordion title="I need the full legal terms too" icon="file-lines">
    The verification page confirms status. The certificate itself remains the right place to read the full terms and restrictions.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="License Certificates" icon="file-lines" href="/help/downloads-and-licensing/license-certificates">
    Learn what the certificate includes beyond verification status.
  </Card>

  <Card title="Content ID Claims" icon="shield" href="/help/downloads-and-licensing/content-id-claims">
    Use the verification link when disputing claims.
  </Card>

  <Card title="BeatPassID" icon="fingerprint" href="/help/downloads-and-licensing/beatpass-id">
    Understand the fingerprint details tied to certificate tools.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/help/downloads-and-licensing/faq">
    More common certificate questions.
  </Card>

  <Card title="Non-Exclusive License" icon="users" href="/help/legal/license-terms/non-exclusive">
    Review the standard license scope and Content ID restriction.
  </Card>

  <Card title="Releasing Music" icon="rocket" href="/help/downloads-and-licensing/releasing-music">
    Prepare a finished song for distribution with its certificate ready.
  </Card>

  <Card title="Library Licenses" icon="bookmark" href="/help/library/licenses">
    Find the certificate and verification action in your library.
  </Card>

  <Card title="Trust Stack" icon="layer-group" href="/help/getting-started/beatpass-trust-stack">
    See how public verification fits into BeatPass's proof system.
  </Card>
</CardGroup>