> ## Documentation Index > Fetch the complete documentation index at: https://docs.superun.ai/llms.txt > Use this file to discover all available pages before exploring further. # Cloud service credit pack > Buy project-only credits that pay that project's cloud service fees. Purchase and check balance from Operations > Publish. A **cloud service credit pack** gives one project its own credit balance, used only to pay that project's [cloud service fees](/superun/pricing). It is not general account credit. You cannot spend it on another project or on chat generation. On **My credits** it is called a dedicated cloud-service credit pack. In the project, the title is **Buy a cloud service credit pack**. It is available on the China site. Private-deploy publish pages do not show this entry. ## Where to open it In the project, open **Operations > Publish**. A banner at the bottom of the page opens the pack. * Before the first purchase, the banner mainly invites you to buy. * When a balance remains, the banner shows the purchased balance. * After any purchase, the dialog has **Buy a pack** and **Purchased credits**. * Desktop uses a dialog; phones use a bottom sheet. You can buy before the project is published. If it is not published yet, or this project has already bought a pack, the one-year usage estimate is not shown. After a successful publish, if the project supports packs, you have permission, and sales are open, the success dialog can open the same purchase flow. **My credits** only shows the introduction. To buy, open **Operations > Publish** on the project. ## Who can buy Only the **project owner or a team admin** can buy. Whether the project supports packs, and whether sales are open, follows the page. Credits you already bought keep their original rules if sales pause. A project with purchase history can still open purchased-credit details, but you cannot buy another pack while sales are paused. ## How to buy 1. Open **Operations > Publish** on the target project and enter the cloud service credit pack. 2. Check the project name in the dialog so the credits are bound to that project. 3. Pick one offer. Each order is **one pack, one copy**. You cannot combine tiers or change quantity in one order. You can buy again later. 4. Check **I have read and agree to the rules below**, then **Buy**, and pay at checkout. 5. When you return, confirm the message that the project's cloud service credits have arrived, then check the balance or purchased details. The purchase dialog lists the packs you can buy now. Each one shows its price and the credits you receive. **Pay the price shown on the pack you select.** Choose by what the project is for: * **400 dedicated credits**: a public demo or a small trial, such as a site, portfolio, or campaign page. * **2,000 dedicated credits**: an app with user accounts and data management that stays live. “From 0.45 yuan” on the introduction means dedicated credits can cost less. When you order, pay the price on the pack you selected. You can buy another pack after this one is used up. If the dialog lists other packs, choose by the price and description shown there. Desktop browsers open checkout in a new window. Phones and tablets open checkout in the current page. WeChat and Alipay in-app browsers use their own pay pages. Team projects can show a corporate transfer entry on desktop checkout; available methods follow checkout. If checkout fails to open, the order already created stays open and you can continue paying it. For a project that is **published and has never bought a pack**, the first package picker estimates usage. If the selected amount is not expected to cover a year of cloud service fees, the dialog says you can buy again. You can still buy this pack now and add another later. ## Balance and expiry * **Bound project**: credits pay only that project's cloud service fees. * **Expiry**: one calendar year. Each batch's expiry is on **Purchased credits**. * **Buying again**: does not extend older credits. Batches stay separate. * **Refunds**: purchases are non-refundable. * **Past debt**: a project pack does not pay historical arrears. Buying one does not by itself restore a suspended project; the original balance and recovery rules still apply. ## Balance and bills On **Purchased credits**, each batch shows: | Status | Meaning | | - | - | | X credits available | This batch still has balance | | Expired | This batch is past its expiry | | Used up or transferred | This batch is used up | A zero balance does not mean you never bought. Purchase history can still be opened. Under **My credits > usage details** you can check: * A purchase: buying a cloud service credit pack for the named project * Fully covered by the pack: cloud service credit pack deduction * Split with general credits: pack deduction plus a general-credit charge ## Paid but not arrived Payment and credit delivery are checked separately. If you have paid and delivery is still in progress, the dialog says so. Use **Check delivery** and do not pay again. * **Waiting for payment**: continue the original order, check delivery, or pick another pack. * **Paid, delivery in progress**: only check the result. * **Delivered**: review the balance and purchase history. * **Order closed**: go back to the offers and buy again. **Picking another pack does not close the original order.** The page warns you not to pay twice. If the original order is already paid or delivering, you cannot reselect. *** How published projects are billed for cloud compute and storage. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.