docs / proof
Transaction proof ledger.
This page names the shipped transaction path and the evidence surfaces that can be inspected after a production proof run. It is not a claim about SDKs, ACS, Stripe Projects, x402, or agent-channel distribution.
Current standard
Use /live and /orders/{id}/evidence to inspect the current state. If the feed has no paid-order event, run the public transaction runbook before treating the proof as fresh.
Canonical operator runbook: docs/V1_0_PUBLIC_PROOF_RUNBOOK.md.
Verified path
What a passing proof run covers
Create
01POST /v1/storesReturns a DB-backed generated store, owner token, slug, and preview handoff.
Publish
02POST /v1/stores/{id}/publishStarts or confirms Stripe Connect readiness before buyer checkout.
Checkout
03POST /v1/checkoutsCreates the hosted Stripe Checkout path for a buyer cart.
Persist
04Stripe webhookRecords the paid order and payment evidence after Checkout completes.
Inspect
05GET /v1/orders/{id}/evidenceReturns structured receipt, order, payment, email, and webhook evidence.
Broadcast
06Merchant webhookRecords signed outbound delivery that can be verified by the proof inbox.
What this proves
The shipped runtime has a generated-store path, publish step, checkout path, order record, evidence endpoint, and merchant webhook record.
REST and MCP operate the same store runtime instead of separate demo surfaces.
Stripe Checkout is the payment boundary; receipt and evidence pages expose the proof after payment.
The production proof is only current when the public verifier passes against a known store and order.
What this does not prove yet
SDK publication or CLI packaging.
Provider provisioning or store creation through Stripe Projects.
ACS catalog registration or broader agent-channel distribution.
x402 or other machine-payment rails in production.
Operator path
Run the canonical procedure in docs/V1_0_PUBLIC_PROOF_RUNBOOK.md.
The final check is pnpm verify:public-transaction https://commerce.fyi <storeId> <orderId>.
Public proof surfaces include /live for the feed, GET /v1/proof/live for API consumers, and GET /v1/orders/{id}/evidence for structured evidence on a known order.