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

# Licenses

> Issue, inspect, suspend and delete license keys that your software can verify online.

**Store → Licenses** is the register of every key Vexaris generated, plus any key you create by hand.

## When keys are issued

A key is generated at the moment an order is paid, for products whose delivery method is **License**. The key is bound to that order and to the buyer, so it always traces back to a real sale.

## The list

| Column | Meaning |
| - | - |
| Key | The full license string, with the product prefix |
| Product | Which product the key unlocks |
| Customer | Who bought it |
| Status | Active or suspended |
| Created | Issue date and time |

## Manual keys

Use **Create Manual License** to issue a key without an order. Pick the product and the customer, then confirm. Manual keys behave exactly like purchased ones: they can be verified, suspended and deleted.

> [!WARNING]
>
> Manual keys do not create a sale, an invoice or a revenue entry. Use them for replacements, warranty cases and migrations, not for normal selling.

## Suspending and deleting

* **Suspend** blocks verification while keeping the record and the history. This is the reversible option and the right choice for chargebacks or abuse.
* **Delete** removes the key permanently. The customer can no longer verify it, so prefer suspension unless the key was issued by mistake.

## Verification

Your software can call the store's verification endpoint with a key and a domain. The response tells you whether the key is active, which product it belongs to and when it was issued. Verification is rate limited, so cache the answer on your side for a short period instead of calling on every page load.

## Tips

* Give each product a distinct prefix so keys are recognisable in support tickets.
* Never print the whole key in a public changelog or screenshot.
* When you migrate from another licensing system, import keys as manual entries first, then switch your verification calls over.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.