License Verification & Purchase Codes

Overview

• Each completed order generates a unique purchase code.
• The purchase code is used to identify and validate a purchased product.
• Sellers can find the corresponding Product ID in their Products Dashboard.
• Purchase codes can be verified via a public API endpoint.
• No official installation interface is enforced — sellers are free to implement their own verification flow.

Purchase Code

A purchase code is generated when an order is marked as paid. It is stored on each order item and shared with the buyer.

• Unique per product purchase
• One code per order item
• Reusable across environments (unless seller restricts it)

License Types

• Personal – single project / personal use
• Commercial – commercial or client projects

Support Plans

• Standard – 6 months (included for free)
• Extended – 12 months (paid upgrade)

License Verification API

{
  "purchase_code": "AB3F9-92KD1-PLM82-XQ91Z",
  "product_id": "product_id"
}

{
  "valid": true,
  "license": {
    "type": "commercial",
    "support": {
      "type": "extended",
      "duration_months": 12
    }
  },
  "purchased_at": "2026-02-12T10:31:00Z"
}

{
  "valid": false,
  "reason": "invalid_purchase_code"
}

Security & Rate Limiting

• Endpoint is rate-limited (e.g. 10 requests / minute / IP)
• Purchase code must match a paid order
• Support data is returned server-side only

Seller Responsibilities

• Build your own activation / install UI
• Store purchase code locally if needed
• Decide how strict validation is (online / offline)
• Do not hardcode secrets in frontend apps

FAQ

Q: Is an installation screen mandatory?
A: No. Sellers decide how activation is handled.

Q: Can apps work without verification?
A: Yes, for MVP or demo purposes, at the seller’s discretion.