How It Works
Configure lock type and activations
Choose a lock type (
none, hwid, or ip), set max activations, and add pricing plans.Customer purchases a key
When a customer completes an order, they receive a license key automatically (e.g.
MYAPP-XXXX-XXXX-XXXX-XXXX).Your software calls the verify endpoint
Your application sends a
POST request to https://license.rmz.gg/verify with the product ID, license key, and optionally a hardware ID.Quick Start
1. Create a License Product
In your store dashboard, go to Products and create a new product:| Setting | Description |
|---|---|
| Type | Software License |
| Key prefix | A short prefix for your keys (e.g. MYAPP produces MYAPP-XXXX-XXXX-XXXX-XXXX) |
| Lock type | none (key-only), hwid (hardware ID), or ip (IP address) |
| Max activations | How many devices can use one key (0 = unlimited) |
| Plans | Duration-based pricing tiers (monthly, yearly, lifetime, etc.) |
| E2EE | Optionally encrypt all API responses with AES-256-GCM |
2. Verify in Your Software
3. Handle the Response
Code Examples
Full working examples are available for every supported language:Node.js
Built-in fetch, no dependencies
Python
Uses the requests library
PHP
Built-in cURL, no dependencies
Lua / FiveM
FiveM-native HTTP requests
Managing Licenses
From your store dashboard under Licenses:- View all issued licenses with filters and search
- Create manual licenses (for testing, gifts, etc.)
- Revoke, suspend, or reactivate individual licenses
- Reset device activations
- View activation history and verification logs
- Aggregate stats (active, expired, suspended, revoked)
License Lifecycle
| Event | Effect |
|---|---|
| Customer purchases | Key auto-generated with the configured prefix |
| Order completed | License activated, expiry set from plan duration |
| Order cancelled | All order licenses revoked |
| Order refunded | All order licenses revoked |
| Expiry date passes | Marked expired automatically (hourly check) |

