DocsUser guide

Read one chapter at a time from the left menu. Steps match the live UI. Screenshots are from the English product interface.

18 / 217 min read

Credits and membership

Generating uses credits. This chapter covers how credits are spent and topped up, and the refund rules.

How credits are spent

  • Before every paid generation, the prompt bar shows the credits it's expected to use; confirm, then submit;
  • Prices and pricing units depend on the selected model. Usage-based tasks are settled by actual usage, and any unused precharged credits are returned.
  • Your credit balance is shown live in the top bar; hover over it to see the breakdown. Some credits can be used only for specific models (dedicated model credits); “Spend order” in the account menu decides whether dedicated or general credits are used first.

Membership and top-up packs

  • Subscription credits are granted monthly and expire when the current period ends. Regular paid credit packs are valid for 730 days after they arrive, and gifted credits are valid for one UTC calendar month after they're granted. Special items keep the validity listed in the catalog.
  • The pricing and membership page (/pricing) lists every plan. Switch between “Monthly” and “Annual prepay”, and between “Individual plans” and “Business plans”. Top-up packs are sold in the Credit Store (click your credit balance in the top bar, or the Credit Store card in the sidebar) or under “Credit top-up” on the subscription page (/billing). They're for active paid members only, and how many you can buy at once depends on your plan tier;
  • “Subscription” (/billing), “Usage” (/usage) and “Redeem code” in the account menu are where you manage your subscription, see your credit usage and redeem credits;
  • Each team has its own shared credit pool, and generations in team projects are charged to the team pool.
The pricing and membership page: plan tiers, monthly credits and how much you can generate
The pricing and membership page: plan tiers, monthly credits and how much you can generate

Refund rules

  • Canceling: you can cancel while the request hasn't been sent to the model yet, and the precharged credits are returned. Once the request has been sent, it can't be withdrawn through the normal cancel flow.
  • A failed task isn't always fully refunded. Usage that's already confirmed may still be charged, and when the result is unknown, the precharge is held until it's been checked.
  • “Charged N credits, returned M credits to your balance” on a node means the task was settled by actual usage and the unused precharge was returned. “Refunded N credits to your balance” means a refund. While the refund amount is still being checked, you'll see “Refunded. The amount is pending review, so it isn't shown yet”. All of these are credits, not cash refunds.
Check the estimate before generating; “Up to N” means usage-based billing · Membership grants credits each period; top-up packs need an active membership and are one-time purchases · You can cancel before the request is sent and get the precharge back; failed tasks follow the usage and return rules

· Maintained by the Sumi Studio team · Written for the live product UI