Topping up a GLM API account looks like a simple matter of paying money, but it actually involves four separate questions: which account the money goes into, whether you are buying cash balance or a resource pack, what amount the invoice is issued for, and how to restore service quickly when the balance runs low. The larger the team, the more often these questions bounce between finance and engineering.
This article separates the two paths, direct top-up on the official platform and top-up through a gateway, and focuses on invoices, refunds, procurement, and balance monitoring. Specific top-up entry points, payment methods, and promotions are governed by the console billing page; this article does not list fixed prices or discount figures.
Note: Zhipu, GLM, and BigModel are trademarks of their respective owners. This article is for technical explanation only and implies no affiliation, agency, or endorsement relationship with Zhipu. Top-up rules, invoice policies, and refund terms may change; read the platform's latest agreements before acting.
1. First confirm which account is being topped up
Before topping up, check which account owns the key. An official key can only be backed by an official account balance, and a gateway key can only be backed by a gateway account balance. The two balances are not connected. Moving money from an official account to a gateway, or the reverse, produces the familiar situation where "the money was paid, but calls still fail."
Also distinguish cash balance from resource packs. The official documentation states that deduction usually draws on resource packs first and cash balance second. Resource packs have an expiry date and cannot be extended, renewed, or reactivated after expiry. The validity policy for cash balance is not clearly stated in the documentation, so avoid leaving large amounts idle for long periods.
2. The official top-up process
This path suits teams that use only GLM, need direct access to new official capabilities, or whose finance department requires settlement directly with Zhipu. The usual steps are:
- Sign in to the Zhipu open platform and open the billing or account center.
- Confirm the account entity, verification status, and available payment methods.
- Choose either a cash balance top-up or a resource-pack purchase, and check the covered models and validity period.
- Complete payment and return to the console to confirm the funds have arrived.
- Check the deduction order and balance changes on the billing page.
- Verify service with one minimal request before restoring production traffic.
If you use the overseas site, the currency, payment channels, and settlement entity may differ; follow what the checkout page shows. Domestic teams settling in RMB usually find reimbursement and invoicing easier, and they avoid budget deviations caused by exchange-rate movements.
3. The gateway top-up process
If a team uses several models at once, or wants one balance to cover GLM, DeepSeek, Claude, and other models, it can register with the ZSQH AI Gateway and top up on the wallet or top-up page. The basic process is:
- Register and sign in to the gateway console.
- Complete account and invoice information in advance so documents do not have to be supplied afterward.
- Choose a top-up amount and complete payment.
- Confirm the balance has arrived, and check how GLM models are billed on the model pricing page.
- Create keys for different environments and set spending caps.
- Validate with a small amount of traffic, then ramp up gradually.
The value of a gateway is not simply "one more payment entry point." It consolidates bills for several models in one place, reducing reconciliation and reimbursement cycles. The trade-off is that model availability timing, parameter support, and billing rules are determined by the gateway, so confirm them before use.
4. How invoices are issued
The core rule for official invoices is that they are issued for the cash amount actually consumed, not for the amount topped up. The official documentation states that the invoiceable range usually includes API inference bills from the previous month and earlier, plus resource-pack orders purchased the previous day or earlier. Bills in arrears must be settled before they can be invoiced. If the verified enterprise entity is about to change, complete historical invoicing first.
Gateway invoices follow the gateway's billing and invoicing rules, and usually support a company title, tax number, and delivery email. Whether ordinary or special invoices are available, the tax rate, and the issuance time depend on the gateway console and support guidance.
Whichever path you take, finance colleagues care about three things: whether the invoice title matches the contracting entity, whether the invoiced amount matches actual consumption, and whether bills can be split by project or department. Confirming these before integration is much easier than supplying documents at month end.
5. Balance monitoring and arrears handling
When the balance is insufficient, the common symptom is error 1113. Reaching the quota limit may return 1308, account rate limiting returns 1302, and platform congestion returns 1305. The first two require a top-up or a quota adjustment; the last two require lower concurrency and backoff retries. Do not treat them as the same problem.
Configure at least three monitoring layers: notify the owner when the balance falls below a threshold, alert when daily consumption grows abnormally compared with the previous period, and notify the on-call engineer immediately when 1113 or 1308 appears. Below is a simple estimate of remaining days of balance; replace the balance and average daily spend with real data.
balance = 500.0 # Current balance in CNY
daily_spend = 12.5 # Average daily spend over the last seven days, CNY
days_left = balance / daily_spend
print(f"Estimated days remaining at the current rate: {days_left:.1f}")
Do not look only at the absolute balance. During promotions, batch jobs, or month-end settlement, the consumption curve can rise suddenly, so an average daily estimate is more reliable.
6. Refunds, procurement, and contracts
The official documentation is fairly clear: the platform generally does not support refunds in arbitrary forms, and consumed or already invoiced amounts usually cannot be refunded. Unused top-up funds may, in special circumstances, be requested through support; if approved, they are returned through the original payment method, but top-up promotions become invalid and used discount amounts may be deducted. Confirm usage before topping up, and do not lock up too much money at once.
Gateway refunds follow the gateway service agreement and may involve handling fees, used quota, and invoice reversal. For enterprise procurement, write the following items into the contract or purchase order: settlement currency, invoice type and tax rate, payment terms, balance validity, refund conditions, data and privacy responsibilities, and service availability statements.
7. Comparing the two paths
| Dimension | Official top-up | Gateway top-up |
|---|---|---|
| Settlement currency | Mainly CNY; overseas sites may differ | Per the gateway checkout page |
| Coverage | GLM and official Zhipu products | Multiple models enabled on the gateway |
| Invoices | Issued for cash actually consumed | Issued against the gateway bill |
| Balance management | Cash balance and resource packs are separate | Unified balance, deducted per model |
| Suitable teams | Single model, deep use of official capabilities | Multiple models, unified procurement and reconciliation |
Neither path is inherently better. If you use only GLM and want the newest official features, direct top-up is more straightforward. If you use many models from many vendors and finance wants consolidated bills, a gateway saves management effort.
8. FAQ
1. Can I get an invoice for the full top-up amount?
Official invoices are usually issued for the cash amount actually consumed, not the amount topped up. Unconsumed amounts generally cannot be invoiced; follow the billing page and official invoice policy.
2. Can an expired resource pack be refunded?
The official documentation states that resource packs cannot be extended, renewed, or reactivated after expiry. Assess usage and validity before purchasing, and avoid stockpiling.
3. Does service stop immediately when the balance runs low?
After arrears, calls fail and return the corresponding error code; the exact grace and recovery rules follow platform policy. Configure balance alerts instead of waiting for errors.
4. Can gateway balance and official balance be transferred between each other?
No. The two account systems are independent, and balances, keys, and bills are not connected. Confirm model coverage and finance requirements before choosing.
5. What does enterprise procurement require?
Usually a business license, invoicing information, the contracting entity, and a payment process. Confirm invoice type, payment terms, and refund clauses in advance before topping up.
