SMX Documentation

Purpose of This Page

This page describes the full Tebex purchase and license process, including verification and support handling, to keep your delivery flow clean and auditable.

Recommended License Model

• Every purchase creates a unique license key
• Each license is tied to a unique customer identity
• Updates within the same product line remain active
• Use status values such as active, suspended, revoked

Recommended Tebex Workflow

1. Customer buys product on Tebex
2. Webhook/API verifies transaction on server side
3. License is created or assigned to existing customer
4. Customer gets access to download and documentation
5. Support can validate license status in ticket flow

# Simplified schema
license_key      VARCHAR(64) UNIQUE
product_id       VARCHAR(64)
customer_id      VARCHAR(64)
status           ENUM('active','suspended','revoked')
created_at       DATETIME
updated_at       DATETIME

Discord Linking (Optional)

• Customer links Tebex email to Discord account
• Bot assigns roles based on purchased products
• Ticket system reads role + license status for quick validation
• In conflicts, always trust Tebex transaction data as source of truth