Sterling

Sterling — Options Data Session

Stripe → HMAC → session → bridge → MQTT/LVC → WS frames.

Sterling — Options Data Session (v2026-09-30T100356Z-5e473105f4) 2026-09-30 | Stripe → HMAC → session → bridge → MQTT/LVC → WS frames. 1 - Billing Routes - Handle billing and API key management Stripe POST /api/sterling/subscribe GET /api/sterling/subscription POST /api/sterling/subscribe/cancel POST /api/sterling/keys GET /api/sterling/keys sterling_billing_router sterling_subscribe sterling_subscription sterling_subscribe_cancel sterling_issue_key ApiKeyStore DEFAULT_KEY_STORE_PATH verify list_for_email Stripe API req… API key respon… 1. Stripe API request received 2. sterling_billing_router processes… 3. ApiKeyStore verifies or manages k… 4. Stripe API response sent 5. Webhook event processed Stripe Checkout Session Response {"checkout_url": "https://checkout.stripe.com/..."} {"session_id": "cs_test_a1b2c3d4e5"} API Key Response {"key_id": "1234567890ab", "key_prefix": "prefix", "tier_code": "sterling_starter", "issued_at": "2023-10-01T12:00:00Z"} Stripe API requests are handled by sterling_billing_router, which interacts with ApiKeyStore for key management. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal As of 2026-09-30 10:03 UTC, from commit 5e47310

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Sterling
Slug
sterling-options
Rendered
2026-09-30T100356Z
From commit
5e473105f4
Updated
30 Sep 2026, 10:03 UTC
Sources at
5e47310
Watches
1 path
  • daemon/src/plugins/sterling