Security & Architecture
Non-Custodial by Design
Zyrox does not store private keys.
We do not control or access merchant funds.
Only your public wallet data (xPub) is stored.
Data Policy
No private financial credentials are held. We store only following data:
Public wallet identifiers
Zyrox stores only public wallet identifiers such as xPub keys or generated public addresses. These allow payment monitoring and address generation, but do not provide access to private keys or control over funds.
Public wallet identifiers
Zyrox stores only public wallet identifiers such as xPub keys or generated public addresses. These allow payment monitoring and address generation, but do not provide access to private keys or control over funds.
Integration data
We store limited payment metadata including transaction hashes, payment status, timestamps, and invoice references. This information is used to track payment confirmations and deliver webhook notifications to merchants.
Smart contracts
Subscription logic is executed on-chain via smart contracts.
Funds are transferred directly from customer to merchant wallet.
Public wallet identifiers
+ Details
Payment metadata
+ Details
Payment metadata
+ Details
No private financial credentials are held.
+ Details
Confirmation policy
Transactions are considered confirmed only after predefined blockchain confirmations.
No instant approval without network confirmation.
-
Encrypted HTTPS (SSL/TLS)
-
Isolated backend architecture
-
Role-based internal access
-
Minimal data storage