Changelog

This page records notable API, payment-lifecycle, dashboard, integration, and operational changes. It is technical release information, not a marketing roadmap.

2026-09-02: Asset-aware BTC and BCH support

Added

• BCH payment creation, retrieval, listing, cancellation, and webhook-event routes under /v1/bch/payments.
• BCH P2PKH account-xpub derivation and canonical CashAddr normalization for mainnet, testnet, and regtest scopes.
• BCH transaction detection, confirmation tracking, fiat pricing, regtest integration coverage, and isolated listener observability.
• Asset-aware dashboard usage and receive-wallet configuration.

Changed

• API keys and webhook secrets remain network-scoped while receive configurations are stored per API key and asset.
• Payment responses and webhook payloads now identify both asset and network.
• Active webhook capacity is shared by assets on one network key; confirmed mainnet usage is account-wide across assets.
• Dashboard asset and network options are driven by scopes configured in the API process.

Compatibility and availability

• Existing payment, API-key, receive-wallet, and usage rows are migrated to asset = 'btc'; existing BTC routes remain compatible.
• Webhook signing remains HMAC-SHA256 over timestamp + "." + raw body.
• BCH payment processing and receive configuration are available on testnet and mainnet. Follow the BCH Release and Migration Notes for integration and migration details.

Release policy

Breaking API changes, migration requirements, webhook-contract changes, integration releases, and operational changes belong in this changelog. Planned work is not listed as released functionality.