رفتن به محتواWallet
EXZIX wallet support is non-custodial: wallets and accounts are owner-scoped, and client-vault material is encrypted client-side.
Wallet types and ownership
The implemented service supports external wallets and client_vault wallets. Merchant wallet access is owner-scoped through merchant wallet permissions. Accounts are EVM addresses attached to an active wallet and begin unverified.
Verify control safely
Ownership verification uses a server-issued, expiring challenge bound to the current wallet address and network. The wallet owner signs the challenge locally; the signature proves control of the address and does not authorize a transaction. Network, address, owner and pending-challenge state are checked server-side.
Client vault boundary
Client-vault ciphertext, nonce, salt, KDF parameters and encryption metadata are accepted as a validated envelope. Encryption and decryption stay client-side; the server stores encrypted material and does not receive a plaintext private key, seed phrase or unlock password.
Wallet operations
Wallet status can be locked or disabled, and pending ownership challenges are invalidated when lifecycle or network conditions change. Use the wallet UI and documented ownership flow; do not submit plaintext secret fields to EXZIX.
Payment separation
Wallet ownership verification is an access and control check. It does not sign or submit a payment, change a Payment Intent status, confirm blockchain evidence, or authorize a refund. Payment confirmation remains the Payment Intent observer authority.