The owner's call, 2026-10-30: USDC through Circle Gateway is Circle's own SDK (@circle-fin/x402-batching) in Hanzo's x402 gateway in front of cloud, a deposit into Gateway once and a payment per request. The Go rail reimplemented that protocol, so it goes now rather than later: billing/gateway, payment/providers/circle, models/remittance, the three /v1/billing/crypto/gateway routes, the commerce treasury route, and the gateway networks in /v1/billing/crypto/options. Crypto top-ups by authorization pause until the gateway takes them; the deposit-address rail is unchanged. Hashid kinds 292 and 293 stay taken. Testing: go build ./... and vet clean; api/billing's crypto tests pass (TestPlanAtInterval and TestSubscribeTrial_NoChargeCardVaultedTrialing fail on main without this change too). Risk: removes a live payment route; cloud must drop its plane ops in the release that pins this. How to revert: revert this commit.
commerce
Checkout, billing, pricing, invoicing — the light commerce router for the Hanzo platform. NOT in PCI-DSS scope (PAN data lives in hanzoai/vault).
Quick start
docker run -p 8001:8001 ghcr.io/hanzoai/commerce:latest
What this is
commerce handles orders, products, subscriptions, invoices, and customer records for every Hanzo deployment. It is CDE-connected, not CDE-in-scope: card data is tokenized at hanzoai/vault and commerce only ever sees the token. The service is production multi-tenant (37+ X-Org-Id call sites), IAM-integrated, and already exposes func Mount(*zip.App, cloud.Deps) error — it is one of the three reference implementations of the HIP-0106 Mount contract.
Specs
Implements:
- HIP-0037 AI Cloud Platform (billing surface)
- HIP-0106 Unified Cloud Binary (commerce subsystem — already exposes
Mount())
Architecture
client -> gateway -> commerce (zip.App)
|
orders / products / subscriptions / invoices
|
+-----------+-----------+
| |
hanzoai/vault billing provider
(CDE — tokenizes PAN) (Stripe etc., webhook in)
|
per-tenant data via base (HIP-0302)
Development
sh scripts/fetch-plans.sh # vendor the @hanzo/plans catalog (go:embed)
go run ./cmd/commerce -dev # API on 127.0.0.1:8090
Data lives under COMMERCE_DIR (default ./commerce_data), one SQLite file per
org. The build needs cgo with the sqlite_math_functions tag, or
CGO_ENABLED=0 for the pure-Go SQLite backend.
Test
export GOWORK=off CGO_ENABLED=1 GOFLAGS=-tags=sqlite_math_functions
go vet ./...
go test ./billing/... ./payment/...
go run github.com/onsi/ginkgo/v2/ginkgo -r test/
The same gates run in CI from hanzo.yml.
License
MIT OR Apache-2.0 (LICENSE, LICENSE-MIT, LICENSE-APACHE) per HIP-0137 One License; vendored third-party terms are in NOTICE.