Look up how one thing works. Product docs explain what a feature does and where its edges are; developer docs are the API contract.
12 pages on how each feature behaves — for operators, finance, and admins.
What Throttle is, the objects it stores, and how a workspace is laid out.
Carts, checkout, discounts, quotes, and subscriptions.
Capturing, refunding, returning, and getting paid.
Payment connectors, shipping and tax, email, and webhooks.
Teams, roles, API keys, and the production/sandbox split.
Walk one job end to end — playbooks for each person who runs Throttle.
The API, SDKs, webhooks, and extension platform. Building something new? Start with the developer overview.
Pick an integration path and take a first payment.
The contract: conventions, errors, states, and the OpenAPI spec.
All 11 →Embedded and hosted checkout, card fields, carts, and quotes.
All 10 →Capture, returns, exchanges, and disputes.
Recurring billing, from first charge to buyer self-service.
One invoice list across cards, terms, and subscriptions.
Let buyers manage their saved cards.
Storefront sign-in, sessions, and order history.
Conversion tracking, attribution, and your own scripts.
Team members, roles, permissions, and API key scopes.
Build, test, and publish apps for the marketplace.
All 15 →Webhooks, imports, the MCP server, and the changelog.
Generated type reference for the browser and React packages.