Skip to content
SoundSyncAudio software platform

Guide

Commerce Overview

SoundSync commerce systems from checkout through payment provider completion, orders, ledger, entitlements, library access, billing, settlement, tax, marketplace, and promotions.

Live Moonwave FX products workspace showing the SoundSync product management surface for audio software releases.
Live Moonwave FX analytics workspace showing revenue, product, customer, activation, and download reporting.
Live Moonwave FX customers workspace showing customer management and activity for the developer account.

SoundSync

Checkout to access

The documented path is implementation-backed and intentionally avoids internal owner-only controls.

  1. Product or cart

    Public storefront, marketplace, embed, or direct client sends productId/items to /api/checkout/product.

  2. Checkout session

    platform resolves product owner, server price, promo code, tax quote, Stripe mode, safe return URLs, and checkout session record.

  3. Payment provider

    Stripe Checkout handles payment collection; free claims bypass Stripe only after server-side zero-total resolution.

  4. Webhook completion

    Verified Stripe webhook processes checkout.session.completed with provider-event/idempotency protection.

  5. Order and ledger

    Order service writes order, order items, sale ledger, optional journal/settlement allocation, and marketplace shares.

  6. Entitlement and library

    Order service grants entitlements; customer library and delivery endpoints expose access.

  7. Download and activation

    Downloads use entitlement-gated delivery; plugin activation/validation uses product credential and entitlement/license state.

SoundSync

System boundaries

Use this map to keep public, developer, partner, and owner-only operations separate.

AreaPublic/developer surfaceBoundary
Checkout/api/checkout/product and /api/checkout/quotePublic buyer call, server-authoritative money.
OrdersDeveloper analytics/reporting and partner external order lookupInternal order tables are not exposed as broad public admin APIs.
Refunds/disputesDeveloper docs explain effects; partner has scoped external-order refund routeOwner/provider controls remain internal.
Billing/settlement/api/developer/billing/* and /api/developer/settlements/*Developer-visible balances/statements only; owner emergency controls are not public docs.
Tax/MoRQuote and jurisdiction endpoints plus docsDocumentation describes platform behavior, not tax/legal advice.