Security
Current live security boundaries for custody, credentials, webhook integrity, and operator ownership.
Non-custodial boundary
Funds settle directly to merchant wallet. Trezalink does not store merchant private keys and does not operate a custodial balance layer for merchant assets.
Current controls only
Security claims in product documentation reflect controls currently available in live flows: API key rotation, webhook signature validation support, duplicate order protection, and wallet-direct settlement boundaries.
Shared responsibility
- Merchant: store API keys securely, protect webhook secrets, and maintain wallet custody.
- Trezalink: provide credential regeneration, webhook signing surface, and operational logs.
- Integration teams: enforce signature verification and controlled retry policies in backend services.
Webhook signing
Validate X-Trezalink-Signature with HMAC-SHA256 over raw payload using your webhook secret. Rotate secrets on schedule and re-validate endpoint handling after each rotation.