Monetization
CodeSCE modules are sold with a buy-once, own-forever model. This page covers how you price a module, how buyers pay, and how sales are tracked.
Pricing
You set your module's price in Studio's profile step (in USD):
- One-time price — what a buyer pays to own the module. A price is required to publish a paid module.
- Free — set the price to $0 to give the module away; buyers get instant access with no payment step.
- Pay-as-you-go (optional) — modules can additionally define a usage-based price for metered use, alongside or instead of a flat one-time price.
Price for the value
Buyers can read your README and try the live preview before paying, so price to match what the module actually delivers. You can't buy your own module — pricing is purely what you offer to others.
Payments
Buyers pay with cryptocurrency, and the flow is fully verified before anyone gets access:
- Payments are processed by NOWPayments on a hosted invoice page.
- The only accepted currency is USDT on the Tron network (TRC‑20).
- The price is fixed server-side from your listing — buyers can't alter the amount.
- Access is granted only after a cryptographically signed payment confirmation is received and the currency and amount are verified. A buyer can't unlock a module by faking the return page or underpaying.
For the buyer's side of this flow, see How Buying Works.
Ownership tracking
Every sale is recorded, which keeps ownership unambiguous:
- Each purchase creates a permanent ownership record tied to the buyer's account.
- Ownership is re-checked on every download, so only legitimate owners can retrieve files.
- Each delivered ZIP is watermarked to the buyer, giving paid modules traceability if they're ever leaked (see Watermarking).
Duplicate-safe fulfillment
Payment confirmations are idempotent — a buyer is only ever fulfilled once per order, even if the provider sends the confirmation multiple times.
That's the author track
You've gone from files to a priced, published, protected module. To go deeper on how CodeSCE protects your work, see the Security section.