Confidential wallet configuration
Public account keys cannot spend funds, but can reveal wallet activity. Sensitive configuration is encrypted in storage.
SECURITY
Your wallet keeps the signing keys.
Brislet uses a compatible public account key to derive receiving addresses. It does not need your seed phrase or private keys.
DIRECT TO WALLET · ILLUSTRATION
YOUR CUSTOMERSends Bitcoin
BRISLETTracks the payment
YOUR WALLETReceives the Bitcoin
Your private keys stay with you.
CONTROLS
What protects the workflow.
Account access
Passwords are hashed. Session controls and optional authenticator-based two-factor authentication protect access.
Integration authentication
API keys identify a merchant and network. Signed callbacks let the integration authenticate updates.
Settlement protection
Receipt matching and idempotency checks help prevent duplicate settlement after retries.
Address discovery
Account verification and unused-address safeguards reduce the risk of deriving addresses beyond a wallet’s discovery range.
BOUNDARIES
Controls do not remove every risk.
Keep wallet backups secure, verify the network and destination, and review wallet discovery limits. Bitcoin transfers are irreversible. Production readiness also depends on operational email, backups and live-payment testing.
No external security certification or independent audit is claimed.