Documentation

    Delivery Types and Presets

    Five delivery engines support files, links, keys, one-time Discord roles and seller-fulfilled manual orders.

    BeginnerSetup guide

    Choose the real delivery engine

    File sends a configured file URL; Link sends an access URL; Key reserves one available code for its checkout before capture and keeps the assigned code for recovery; Role attempts one configured role grant; Manual records an order for the seller to fulfill. New key captures require a healthy recovery service. Reserved and revoked keys are not available stock.

    Understand presets

    Archive bundle means one archive file, not multiple component products. Course/event/SaaS presets deliver a URL, not a hosted course, calendar booking or provisioned account. Team key sends a seller-supplied key, not managed software seats. Service booking and managed fulfillment require human scheduling/work.

    Separate payment and delivery

    A paid order can still have pending, failed or review-held delivery. Inspect both statuses. Fix the underlying failure and retry the existing order rather than creating another payment.

    Explain limits before selling

    Buyer recurring billing, multi-role bundles and drip delivery are not included. Signed license verification requires developer integration. Timed role passes require an available expiry service, and setup is blocked while that service is unavailable. Describe the actual one-time access and delivery terms.

    Game server delivery (preview)

    This setup preview does not enable game sales. A connected server and release acceptance are required before game checkout.

    Setup and limitationsGame accounts

    Was this guide helpful?