2chanify
VENDOR CONSOLE

Licences for every 2chanify business

Register clients, sign their program licences and renew them on time. 2chanify checks each licence offline, against the NUI and POS registered with ATK.

Development version – not certified by ATK.

2chanify
VENDOR CONSOLE

Log in

Use your vendor account. Every login needs your password and a code from your authenticator app.

No users yet. On the server, create the first admin:
2chanify-vendor-server user add --role admin --email you@example.com --name "Your Name"

QR code for the authenticator app
  1. Open an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password…).
  2. Scan the code. Cannot scan? Type this key:
  3. Enter the 6-digit code the app shows.

At least 12 characters.

Licences are a commercial control only: they never enter a receipt and have nothing to do with ATK.
2chanify
VENDOR CONSOLE
Licence office
vendor.2chanify.com
Licences
Administration
2chanify Vendorv0.1 DEV
Clients —
The licence key is locked: licences cannot be signed.
Licences

Clients

Every business with its licence as 2chanify sees it today. Warnings start 30 days before expiry; new sales stop 14 days after it.

BusinessNUIPOSLicenceExpiresState

No clients yet

Register the first business with New client, then issue its licence.

Licences

Licence key

One ECDSA P-256 key pair signs every licence. It is separate from the fiscal keys of each POS and from the 2chanify updater key.

How the key works

  • The private key stays on this server, encrypted with the key password.
  • After a restart it is locked; an admin unlocks it with the key password.
  • It locks itself 30 minutes after it was last unlocked or used.
  • It is created once and never replaced: a new key would need a new 2chanify build and new licences for everyone.

Public key for 2chanify

Paste this line into src-tauri/licence/vendor_public_key.txt of 2chanify, below the comment lines. Builds with it accept only licences signed here.


            
Administration

Users

Admin: licence key, users, backups and activity, plus everything staff do. Staff: clients and licences, signing while an admin has unlocked the key. Everyone logs in with a password and an authenticator app.

Add a user

Give the temporary password to the person privately. At the first login they choose their own password and set up the authenticator app.

Administration

Activity

The last 300 events: logins, key use, licences and user changes. The log cannot be changed or deleted.

Administration

Backup

Download both files and keep them off the server, for example on an encrypted USB drive. Keep the key password somewhere else.

Licence key

The encrypted key file. Without it, or without its password, no licence can ever be renewed.

Register

Clients, licences, users and the activity log, as a SQLite file. It holds personal data.

Client

New client

Business

Branches and POS IDs

POS IDs are the IDs registered with ATK, separated by commas. A licence for the registered POS covers exactly these.

Issue a licence

The licence key is locked. to sign.Ask an admin to unlock it.
Save the client first.

Licence history

Licence key

Unlock the licence key

This creates the vendor's licence key pair (ECDSA P-256), once. The private key is stored only on the server, encrypted with the password you choose.

  • At least 12 characters, different from your login password.
  • Without the password, no licence can be signed or renewed.
  • Download a backup afterwards and keep it off the server.

Licence file

Licence

Send this file to the client. Their administrator loads it in 2chanify: Administration → Licence.

    
Account

Change password

At least 12 characters. Changing it logs you out everywhere else.