Real commerce control plane for provider checkout, webhook verification, entitlement storage, and private order state.
STATUS=INSTALLED_FAIL_CLOSED · PROVIDER=STRIPE_CHECKOUT · FAKE_CHECKOUT=false
curl -X POST https://speedkit.eu/api/marketplace/checkout \
-H 'content-type: application/json' \
-d '{"plan":"starter","offer_id":"offer-wsp-001"}'
This endpoint is real and fail-closed. It will not create fake sessions. It requires real provider secrets and real Stripe price IDs.
npx wrangler pages secret put STRIPE_SECRET_KEY --project-name speedkit npx wrangler pages secret put STRIPE_WEBHOOK_SECRET --project-name speedkit npx wrangler pages secret put STRIPE_PRICE_SPEEDKIT_STARTER --project-name speedkit npx wrangler pages secret put STRIPE_PRICE_SPEEDKIT_PRO --project-name speedkit npx wrangler pages secret put STRIPE_PRICE_SPEEDKIT_ENTERPRISE --project-name speedkit npx wrangler pages secret put SPEEDKIT_BASE_URL --project-name speedkit
Also bind a KV namespace as SPEEDKIT_COMMERCE_KV for private order and entitlement records.
No checkout is simulated. No customer data is public. No order is stored in the repository. Orders and entitlements live only in private runtime storage.
Commerce is live. Stripe Checkout is active, webhook storage is KV-bound, fake checkout is false, and entitlement proof is routed through the marketplace runtime.
Founder access to SPEEDKIT public marketplace control.
Commercial operator access for teams and builders.
Institutional control access for serious integrations.
PUBLIC_ONLY=true · COMMERCE_READY · FAKE_CHECKOUT=false · KV_ENTITLEMENT_STORAGE=true
The marketplace is now a command tower. Pricing, checkout, entitlement, receipt proof, plan matrix, route map, and buyer path are bound into one live product control surface.
Payment is only the money rail. These bundles define what each plan unlocks inside the Product Control OS.
Capability enforcement is live. Plans now have allowed and denied capability sets, and the access-check API returns deterministic ALLOW/DENY decisions.
Plan usage is now measurable. Allowed capability use writes metered events to KV; denied capability use does not write.
Usage is now evidence. Allowed metered usage writes hash-chained ledger entries to KV. Denied usage remains blocked by policy and is not recorded as consumption.