Develop and submit plugins

1. Start with the example

The example is a standalone browser-based support checklist. It demonstrates the package format and requires no customer data or access keys. Extract it and open checklist.html.

Tickessa does not currently provide a general-purpose plugin loader or guaranteed internal runtime hooks. Standalone extensions include their own setup. Integration into internal interfaces or database tables must be agreed before development and approval; these structures are not a stable SDK.

2. Manifest and ZIP structure

Place tickessa-plugin.json at the ZIP root, without a parent directory. The key and version must be unique. Use three numeric components for a stable version; each submission requires a higher version.

{
  "schemaVersion": 1,
  "key": "example-checklist",
  "version": "1.0.0",
  "name": {
    "de": "Support-Checkliste",
    "en": "Support checklist"
  },
  "description": {
    "de": "Eine eigenständige Checkliste zur Vorbereitung und Prüfung von Supportfällen.",
    "en": "A standalone checklist for preparing and reviewing support cases."
  },
  "compatibility": {
    "tickessaMin": "0.13.0",
    "tickessaMax": "0.13.0",
    "platforms": [
      "web"
    ]
  },
  "permissions": [
    "browser:local-checklist"
  ],
  "supportUrl": "https://tickessa.de/",
  "license": "perpetual",
  "updates": "one_year",
  "installation": "INSTALL.md",
  "update": "UPDATE.md",
  "uninstall": "UNINSTALL.md"
}

• Name and description in German and English. Plain text only; HTML is not executed.
• Explicit tested Tickessa version range and platforms: web, mac-arm64, windows, linux.
• Describe all access and data transfers in permissions. Disclose external services and costs in the description.
• Include INSTALL.md, UPDATE.md, UNINSTALL.md, LICENSE.txt and CHANGELOG.md. The update instructions must cover backups and restoration.
• Maximum 4 MiB ZIP, 16 MiB expanded, 200 entries and 1 MiB per file. Source and text files are accepted: JSON, Markdown, TXT, JS/TS, PHP, CSS, HTML, SQL, shell and YAML. No executables, nested archives, symbolic links, dependency directories or credentials.

3. Submit, test and approve

Apply for developer access, complete your billing profile and accept the partner terms. For each version, set an initial price and an additional update-year price in EUR excluding tax.

Upload checks validate ZIP structure, checksums, metadata and required documents. Tickessa then reviews source, rights and privacy, and tests installation, updates with existing data, restoration and uninstallation in an isolated environment. An optional AI report supplements the review. It is not a security certificate and cannot publish software.

Only a manually approved version can update the Paddle catalog and sales page. Price changes affect new orders; existing orders retain their agreed price.

4. Usage, updates and remuneration

Buyers receive perpetual use of their purchased version and one year of updates. An optional renewal starts at the existing expiry date, or on confirmed purchase if updates have expired. Plugins must not disable paid perpetual usage on expiry or temporary loss of the portal connection.

Tickessa grants access after server-confirmed payment. Downloads check the licence, plugin and release date. Previously entitled versions remain available. Paddle is synchronized through payment notifications and additional periodic reconciliation.

Remuneration and monthly self-billing follow the linked partner terms. Statements provide a breakdown of sales, fees and adjustments.