Core Flows

Three flows carry almost all of CodeSCE's value. Each one crosses several components; here's how they move through the system.

Flow 1 — Publish

An author turns files into a live listing. The security pipeline runs before anything is stored.

Upload→Scan→Store→Publish

1. Upload — in Studio, the author submits the Module ZIP, UI, and README with metadata.
2. Scan — the security pipeline runs all scanners and produces a decision: published, hold, or rejected. Rejected uploads stop here — nothing is saved.
3. Store — on pass, private files go to R2 (private/), the README to public/, and the module record (with its config_schema) is written to PostgreSQL.
4. Publish — the module's status is set. A hold is kept as a draft for manual review; a clean pass with "publish" requested goes live and appears in the marketplace.

See Author → Studio Workflow and Scanning.

Flow 2 — Purchase

A buyer pays, and ownership is granted only after the payment is verified.

Checkout→Payment→Verification→Ownership

1. Checkout — the backend opens a pending order at the module's server-side price and creates a NOWPayments invoice.
2. Payment — the buyer pays in USDT (TRC-20) on the hosted invoice page. The app polls the order status in the background.
3. Verification — NOWPayments sends a signed IPN webhook. The backend checks the signature, finished status, currency, and amount before trusting it. The success redirect grants nothing on its own.
4. Ownership — on a verified payment, fulfillment records a permanent purchase (idempotently), and the buyer's button flips from Buy to Download.

See Buyers → How Buying Works and Payment Verification.

Flow 3 — Download

An owner retrieves files through a link that's useless to anyone else.

Request→Signed link→Watermark→Download

1. Request — the owner clicks Download; the app asks the backend for a fresh access token.
2. Signed link — the backend re-checks the session and ownership, then issues a short-lived (≤60s), one-time token bound to the user, module, and IP.
3. Watermark — as the file is served, a per-buyer trace is embedded (a hidden ZIP record and in-code marks).
4. Download — the watermarked ZIP streams to the owner. The token is consumed and can't be replayed.

See Secure Downloads and Watermarking.

How the flows connect

The three flows chain into the full lifecycle of a module:

Author publishes→Buyer purchases→Buyer downloads→Integrates

Next step

Get moving fast with the Quick Start →.