The close-audit DoD validator on a Sovereign host
(e.g. console.t32.omani.works) probes POST /api/v1/billing/purchase
+ POST /api/v1/sme/billing/purchase during the marketplace
customer-journey re-walk (Step 15 — "Purchase" button). On t32 both
returned 404 because the route was never registered on catalyst-api
or the billing service — distinct from the prior 502 class which
was a billing-service-Pod-stale / NATS-connection failure (TBD-A1
The canonical purchase wire has always been
POST /api/billing/checkout (marketplace gateway → billing service
Checkout handler — see CheckoutStep.svelte:722 + handlers.go +
routes.go); the validator vocabulary diverged from the in-cluster
naming. Rather than renaming the canonical handler or migrating
every existing caller, this PR registers two thin aliases:
- billing service (core/services/billing/handlers/routes.go):
POST /billing/purchase → existing Checkout handler. Same
promo-code application, same Stripe-session creation, same
paid_by_credit shortcut. Semantic alias only.
- catalyst-api (products/catalyst/bootstrap/api/...):
POST /api/v1/billing/purchase + POST /api/v1/sme/billing/purchase
→ proxy to SME gateway /api/billing/purchase → billing
service /billing/purchase. Mirrors sme_billing_vouchers.go
proxy shape — same mintSMEBridgeToken RS256→HS256 bridge,
same 503 sme-gateway-unreachable graceful-degradation on a
Sovereign without the SME services tier.
Marketplace UI continues to call /api/billing/checkout unchanged
(no FE migration), so every existing customer-journey GREEN path
remains stable. The new aliases exist primarily so the
operator-side DoD validator on console.<sov-fqdn> stops 404'ing.
Chart bump: 1.4.188 → 1.4.189 + bootstrap-kit pin synced.
Tests: routes_test.go asserts both /billing/purchase and
/billing/checkout resolve (regression guard for accidental
rename / removal). All existing billing + catalyst-api handler
tests pass.
Co-authored-by: hatiyildiz <hatiyildiz@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>