Commerce and checkout

Commerce turns products into access. The common flow is:

Create a product.
Add one or more prices.
Attach the product to a hub checkout display.
Start checkout as a member.
Webhooks update orders, subscriptions, payments, and entitlements.

Admin setup

Products are team-scoped:

GET  /api/v1/teams/{team_id}/products
POST /api/v1/teams/{team_id}/products
GET  /api/v1/teams/{team_id}/products/{product_id}
PATCH /api/v1/teams/{team_id}/products/{product_id}

Prices live under a product:

POST /api/v1/teams/{team_id}/products/{product_id}/prices
GET  /api/v1/teams/{team_id}/products/{product_id}/prices

Payment accounts connect the team to Stripe Connect:

POST /api/v1/teams/{team_id}/payment-accounts/onboarding-link
GET  /api/v1/teams/{team_id}/payment-accounts

Member checkout

The member-facing checkout route starts a hosted checkout session:

POST /api/v1/hub/{hub_id}/checkout

After payment, use the member billing routes:

GET  /api/v1/hub/{hub_id}/me/orders
GET  /api/v1/hub/{hub_id}/me/subscriptions
POST /api/v1/hub/{hub_id}/me/subscriptions/{sub_id}/cancel

Operational routes

Admins can inspect payments, subscriptions, orders, and webhook events. Use these for support tooling and reconciliation.

GET  /api/v1/teams/{team_id}/hubs/{hub_id}/orders
GET  /api/v1/teams/{team_id}/hubs/{hub_id}/payments
GET  /api/v1/teams/{team_id}/hubs/{hub_id}/subscriptions
GET  /api/v1/teams/{team_id}/hubs/{hub_id}/payment-webhooks

Start here

Core concepts

Guides

API reference

Admin setup

Member checkout

Operational routes

​Admin setup

​Member checkout

​Operational routes

Admin setup

Member checkout

Operational routes