Security
Deposit keys
Each session gets a fresh, single-use private key for its deposit address, encrypted at rest with AES-256-GCM. It’s only ever decrypted inside the settlement job, to sweep funds onward once a payment arrives.
Account credentials
API secret keys are never stored in plaintext — only a SHA-256 hash. Dashboard passwords use scrypt. Neither can be recovered from the database if it’s ever exposed.
Webhooks
Deliveries are HMAC-SHA256 signed (see Webhooks) so you can verify a payload actually came from us. Your webhook URL is checked before every delivery: HTTPS only, no embedded credentials, and it must resolve to a public address — an internal or loopback address is rejected.
Rate limits
Sign-up and login are limited to 10 requests/minute/IP. The widget’s publishable-key session endpoint is limited to 20 requests/minute/IP.
Refunds
A payment that arrives after a session expires, or an underpayment, stays at the deposit address rather than being swept automatically. From Transactions, you can manually sweep that balance back out to any address — no fee is taken, since the session never settled.
Known gaps
Wallet connect only supports browser extensions (MetaMask, Rabby, etc.) today — WalletConnect, for mobile wallets that connect by scanning a QR, isn’t wired up yet.