The payment stack covers browser, merchant and local-device payment routes.
Cryptix / CryptixPay
CryptixPay
CryptixPay is the CPAY payment layer for wallet payments, merchant payment requests, REST-based integrations and local payment handling.
QR payments are already available in wallet flows. NFC is also already available: the web wallet has an active NFC function, and the All in One software already includes REST/NFC payment routes and NFC write functions in the current beta branch.
NFC is already integrated in these two environments and is not only a planned feature.
Payments settle on CPAY with low network fees that remain inside the network.
Overview
CryptixPay is the umbrella term for the payment-related modules around CPAY.
Scope
- Wallet-side QR payments
- Merchant and service-side payment requests
- REST-based payment server workflows
- NFC payment and NFC write functions
- Planned physical card-based receive routes
Current components
The table below separates what is already available from what is still only planned.
| Component | Status | Current use | Location |
|---|---|---|---|
| CryptixQR | Live | QR-based wallet payments | Wallet payment flow |
| CryptixGateway | Beta / active expansion | Merchant payment requests, checkout and POS-oriented server handling | CryptixPay server and commercial stack |
| CryptixNFC | Active in web wallet, beta in All in One | NFC tabs, reader-based requests and NFC write functions | Web wallet and All in One |
| CryptixCard | Planned | Physical QR and NFC receive medium | Not released |
The name CryptixTouch is used for the local tap and phone-to-phone payment direction inside the same NFC area. The currently relevant public implementations are the active web-wallet NFC function and the NFC-related beta routes in All in One.
NFC status
NFC is already present in the current software stack, but platform and hardware support still matter.
| Area | Status | Notes |
|---|---|---|
| Web wallet | Active | NFC was activated and tested for NFC-based send flows and NFC tabs. |
| All in One | Available in current beta | /nfc-input/, /nfc-output/{deviceId}, /rest-input/, /rest-output/{deviceId} and manual NFC writing are already part of the beta payment layer. |
| Browser support | Platform-dependent | Browser-based NFC depends on Web NFC support. Chromium and Edge class browsers are the reference. iOS browsers do not provide browser-based NFC support. |
| Desktop and readers | Hardware-dependent | Desktop systems need compatible NFC hardware. Current beta documentation mentions ACR122U, Omnikey 5321 and 5325, Identiv SCR3310v2.0, Sony RC-S380, uFR, ACS ACR38, Gemplus GemPC and NFC-capable smartphones. |
Technical notes
Fee model
The network has a 0% developer fee. Transaction fees remain inside the network and go to miners. A commonly referenced transaction fee is around 0.00003165 CPAY.
Chain basis
Cryptix uses the CPAY Blogdag chain with a target block cadence of about one second, which is the on-chain base for the payment modules.
Control model
The payment modules are built around normal wallet usage and payment requests. The wallet remains under user control instead of being replaced by a central account layer.
Related pages
The surrounding pages contain the operational details for merchant usage, wallet access and local software.