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

# Build with Shoppex

> Hosted checkout, Developer API, storefront SDK, and theme platform.

Shoppex is payment infrastructure for digital product sellers. You can use it at four levels of
integration depth, and mix them freely.

<CardGroup cols={2}>
  <Card title="Hosted checkout" icon="window-maximize" href="/merchants/start/quickstart">
    Your buyers check out on `yourshop.shoppex.io` or through the Shoppex Embed SDK. Zero backend
    work — you just create products.
  </Card>

  <Card title="Developer API" icon="code" href="/api-reference/quickstart">
    Drive everything from your own backend. Create invoices, manage customers, fulfill orders,
    push events.
  </Card>

  <Card title="Storefront SDK" icon="browser" href="/sdk/introduction">
    A browser-safe SDK for headless storefronts you host yourself. Use it outside the
    Shoppex hosted theme runtime.
  </Card>

  <Card title="Theme platform" icon="palette" href="/themes/introduction">
    Build your hosted storefront visually in the Theme Builder, or fork it into a Liquid
    custom theme with AI editing, local preview, validation, and publish.
  </Card>
</CardGroup>

## Pick where to start

If you have **a buyer paying for digital goods today**, start with the hosted checkout — you'll
be selling within an hour.

If you have **an existing app that needs to charge users**, jump straight to the Developer API.
You'll create invoices, redirect to checkout, and listen for webhooks.

If you have **a frontend team and want a custom storefront you host yourself**, use the
Storefront SDK on top of the public storefront API.

If you want to **redesign or ship the Shoppex-hosted storefront**, you have two paths: customize
it visually in the Theme Builder (no code), or fork it into a Liquid custom theme and edit the
source with the CLI, Dev API, or AI tooling.

## Core concepts

<CardGroup cols={2}>
  <Card title="Invoices" href="/guides/invoices">
    The unit of payment. Every transaction creates an invoice with a lifecycle from `pending` to
    `paid` (or `void`).
  </Card>

  <Card title="Payments" href="/guides/payments">
    Three ways to take money: the hosted storefront, payment links, and the API. Same invoice
    model under the hood.
  </Card>

  <Card title="Subscriptions" href="/guides/subscriptions">
    Recurring invoices with retries, trials, and plan changes.
  </Card>

  <Card title="Webhooks" href="/guides/webhooks">
    Real-time event delivery. Sign verification, retries, and the full event reference.
  </Card>
</CardGroup>