Skip to main content
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.
Verification is public. The person checking the certificate does not need to log in.
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.
Every certificate points to a URL in this format:

How to verify a certificate

1

Get the license UUID

You can copy it from the certificate, the printable certificate page, or the Licenses area in the app.
2

Open the public page

Visit https://open.beatpass.ca/verify-license/ followed by that UUID.
3

Review the result

BeatPass returns a public status page for that specific certificate.

What the page shows

The current public verification page shows the certificate status plus the core identity details tied to that license:
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.

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

For licensees

Use the verification page when a distributor, label, platform, or collaborator asks you to prove you have a valid license.
Use it to confirm whether a downloader or buyer has an active certificate for one of your tracks.
Use it to verify that a certificate is real before acting on a rights dispute or release review.

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

The page says the license was not found

Double-check the UUID. A bad or incomplete UUID is the most common cause.
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.
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.

License Certificates

Learn what the certificate includes beyond verification status.

Content ID Claims

Use the verification link when disputing claims.

BeatPassID

Understand the fingerprint details tied to certificate tools.

FAQ

More common certificate questions.

Non-Exclusive License

Review the standard license scope and Content ID restriction.

Releasing Music

Prepare a finished song for distribution with its certificate ready.

Library Licenses

Find the certificate and verification action in your library.

Trust Stack

See how public verification fits into BeatPass’s proof system.
Last modified on July 10, 2026