> ## Documentation Index
> Fetch the complete documentation index at: https://docs.member.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Commerce and checkout

> Products, prices, checkout sessions, orders, subscriptions, and access grants.

Commerce turns products into access. The common flow is:

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

## Admin setup

Products are team-scoped:

```text theme={null}
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:

```text theme={null}
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:

```text theme={null}
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:

```text theme={null}
POST /api/v1/hub/{hub_id}/checkout
```

After payment, use the member billing routes:

```text theme={null}
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.

```text theme={null}
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
```