SatLane

SATLANE / SECURITY

Your keys.
Your control.

SatLane helps you manage Bitcoin payments without taking custody of the customer’s payment. Your wallet controls the funds.

THE PAYMENT BOUNDARY

Funds go to your wallet.

SatLane derives receiving addresses from your extended public key. That public key allows address generation, not spending.

Customer walletYour Bitcoin wallet

SatLane provides checkout, payment monitoring and signed updates. Bitcoin network confirmation times vary.

01

Public keys, encrypted at rest

Registered extended public keys and webhook secrets are encrypted with AES-256-GCM. Keep private keys and recovery phrases in your own wallet; do not enter them into SatLane.

02

Authentication with clear boundaries

API key verification uses a SHA-256 hash rather than storing the complete key as plaintext. Sensitive wallet-registration and API-key management routes require two-factor authentication. Keep API keys on your server.

03

Signed updates and secret rotation

Webhook delivery uses HMAC-SHA256 signatures. Secret rotation retains the previous secret for a 24-hour overlap. Verify signatures, handle duplicate events and acknowledge delivery only after safely recording it.

04

Administrative accountability

Administrative access is gated by an email allowlist, with an optional IP allowlist. Audited financial decisions are recorded alongside their database changes. Manual reconciliation is distinct from automatic chain verification.

05

Payment lifecycle and recovery

The payment lifecycle tracks detection, confirmation and reversal. A reverted payment can generate a payment-reverted event. Your integration should reconcile these updates instead of treating a detected transaction as final.

RESPONSIBLE REPORTING

Help us protect the platform.

Send the affected area, reproduction steps and potential impact. Avoid sharing private keys, passwords or customer information. Use Sandbox for integration testing; do not test against other merchants.

Report a vulnerability ↗