# BitterCheckout Public Context

## Summary

BitterCheckout adds Stripe Checkout to an existing product site while the
product keeps control of access and fulfillment.

It lets a product define checkout configuration, embed a widget, create a
Stripe Checkout session, observe Stripe webhook events, keep Checkout-local
event records, and send signed callbacks to the consuming product.

The consuming product still owns credits, access, fulfillment, refunds policy,
support, and the meaning of purchased value.

## Product Loop

```text
CheckoutConfig -> WidgetEmbed -> BuyerAction -> StripeCheckoutSession -> StripeWebhook -> CheckoutEvent -> SignedCallback -> ProductFulfillment
```

## User And Job

The user is a small product or site operator who wants to add Stripe Checkout
without rebuilding widget UX, session creation, webhook receipt, and callback
plumbing.

## Place In Bitter

BitterCheckout works as a standalone product. A Bitter account provides seller
sign-in, while other Bitter services are optional when shared identity,
support, or product analytics are useful.

## Boundaries

BitterCheckout is not a payment processor, credit ledger, entitlement engine,
Hub identity system, credential custody service, accounting system, refund
authority, or support workflow.

Stripe owns hosted payment collection, card data, payment methods, processor
receipts, disputes, and payouts. BitterHub can own shared account identity and
ecosystem entitlement projection. The consuming product owns what the payment
unlocks.

## Public Claims

Source-supported public claims:

- BitterCheckout hosts checkout configuration.
- BitterCheckout serves an embeddable widget.
- BitterCheckout creates Stripe Checkout sessions.
- BitterCheckout receives Stripe webhook events.
- BitterCheckout records checkout events.
- BitterCheckout signs callbacks to consuming products.
- The consuming product remains responsible for fulfillment.

Claims to avoid unless separately verified:

- no backend code needed
- no Stripe dashboard or API keys needed
- instant self-serve public launch
- BitterCheckout stores credit balances
- BitterCheckout grants entitlements by itself
- BitterCheckout is the payment processor
- BitterCheckout handles buyer support or refunds

## Current Deployment Boundary

Status: source-shaped app repo, live on BitterGrid, not public-source-ready.

As of 2026-07-10:

- `https://bittercheckout.com/` is live and backed by this app/runtime service.
- live `/up`, `/widget.js`, `/sitemap.xml`, `/index.md`, `/llms.txt`, and
  `/llms-full.txt` are part of the public discovery surface
- private account routes such as `/login`, `/signup`, `/dashboard`, and the
  account callback route are marked `noindex` in HTML and HTTP robots headers
- GitHub repository visibility remains private

Publication requires a separate public marketing split repository or a
dedicated app-repo publication scrub plus current Grid source reconciliation
and live verification receipts.

## Repository

The GitHub source link is omitted until publication safety review, public
visibility, and live route behavior all verify.