Start / Commercial Usage

Commercial usage built around APIs, daemon flows and payment automation.

Cryptix already provides the building blocks for automated payment handling, transaction checks, wallet-side actions and service integration.

CryptixPay Wallet Daemon Downloads

Current module stack.

The modules below already form the base for automated payment handling and service integration, while additional plugins such as WordPress, WooCommerce, Shopify and POS-targeted adapters remain part of the broader expansion path.

Module	Purpose	Source / Info	Access
Cryptix REST API Server	Read and verify blockchain-related data through API endpoints.	Source Code	GitHub
Wallet Daemon	Automate wallet actions such as address generation, sending and daemon startup.	More Info / Source Code	Windows / Linux
CryptixPay Server	Gateway-style payment server for creating and tracking payment requests.	CryptixPay / Source Code	GitHub
Wallet Daemon TCP Trigger API	Trigger wallet-daemon actions through a TCP-oriented integration layer.	Source Code	GitHub

CryptixPay server endpoints.

The payment layer is intentionally compact: operational health, payment lookup and payment creation cover the core gateway flow.

Endpoint	Method	Description	Required Parameters
getStats	GET	Returns gateway telemetry and operational status.	None
getPayment	GET	Loads payment details by payment identifier.	`paymentId`
createPayment	GET	Creates a new payment request and returns the new payment identifier.	`amount`, optional `merchant`

REST API coverage in practice.

The REST server is already broad enough for wallet lookups, explorer-like data checks and operational dashboards without requiring a full custom blockchain parser.

Address layer

/addresses/{cryptixAddress}/balance
/addresses/{cryptixAddress}/utxos
/addresses/{cryptixAddress}/transactions
/addresses/{cryptixAddress}/full-transactions
/addresses/{cryptixAddress}/transactions-count

Network layer

/info/blockdag
/info/coinsupply and supply breakdown
/info/network, /info/cryptixd, /info/health
/info/fee-estimate, /info/blockreward, /info/halving
/info/hashrate, /info/hashrate/max, /info/price, /info/marketcap

Blocks and transactions

/blocks/{blockId} and /blocks
/blocks-from-bluescore
/transactions/{transactionId}
/transactions/search
/transactions and /transactions/mass

Wallet daemon command surface.

The wallet daemon is the execution layer for many backend flows. These are the commands and runtime switches that matter most when integrating it into scripts or services.

Application options

/V, /version for version output.
/testnet, /simnet, /devnet for network selection.
/override-dag-params-file for devnet-specific DAG overrides.
/?, /h, /help for command help.

Operational commands

create, new-address, show-addresses
balance, send, sweep
create-unsigned-transaction, sign, broadcast
parse, dump-unencrypted-data, get-daemon-version
start-daemon for daemon runtime mode

All-in-One beta for POS and NFC-style flows.

Version 1.5 of the Rust developer branch of the all-in-one package exposes a beta payment layer for NFC and REST-based device handling. That makes it relevant for small point-of-sale prototypes and single-terminal environments.

REST and NFC channels

Dedicated endpoints separate NFC / POS traffic from online-store style REST traffic while still allowing device-specific routing through a device identifier.

NFC / POS
/nfc-input/    (POST)
/nfc-output/{deviceId}    (GET)

REST / Online Store
/rest-input/   (POST)
/rest-output/{deviceId}   (GET)

Operational notes

The deviceId model supports one or many devices in the same installation.
Manual input remains available for administrative or fallback usage.
Stored payment request data survives device restart and failure scenarios.
Manual NFC writing is available for compatible NFC hardware and cards.
Windows service activation for smart-card support can require net start SCardSvr.

Supported NFC hardware mentioned in the current beta documentation includes ACR122U, Omnikey 5321/5325, Identiv SCR3310v2.0, Sony RC-S380, uFR, ACS ACR38, Gemplus GemPC and NFC-capable smartphones, with ISO 7816 as the referenced base.

Fee model and deployment reality.

Commercial tooling does not add a protocol-level surcharge. The relevant question is operational support, not hidden on-chain extraction.

Fee baseline

Use of the modules is free. Typical Cryptix transaction fees are low and remain inside the network, where they are allocated to miners. A commonly referenced network fee is around 0.00003165 CPAY.

Platform coverage

Windows, Linux and Android are the primary supported environments. Browser-based PWA usage remains the most neutral fallback where native packaging is not provided. macOS and iOS are not currently offered as official distribution targets.