[Bug] GLM Coding Plan: 150% Extra Usage Credits Not Applied After Subscription — $168 Plan Charged Without Bonus

🐛 Bug Description

Users subscribing to the GLM Coding Max plan ($168/month) are promised 150% usage credits as part of the promotional offer, but the bonus credits are not being applied to their accounts. Users are charged the full premium price but only receiving standard quota allocation.

Impact Severity: CRITICAL — Financial

• Users paying $168 USD for premium tier are not receiving the advertised 150% usage limit

---

🔍 Detailed Report

Affected User

• Discord: RickLock
• Plan Subscribed: GLM Coding Max (most expensive tier — $168/month)
• Promised Benefit: 150% usage
• Actual Result: Standard quota only — exhausted in <48 hours with single chat session

Timeline

Date	Event
20/08/2026 20:39	User reports issue — subscribed but no extra credits received
20/08/2026	Paid $168, weekly limit about to end on day 2
21/08/2026 07:25	Staff (Agnes|Z.ai) asks if using ZCode
21/08/2026 08:00	User confirms ZCode usage
21/08/2026 13:10	Mod (Roman) requests screenshot of models & usage section
21/08/2026 21:13	User provides screenshot evidence
21/08/2026 12:42	Mod confirms same visual issue on his ZCode (OSX) after last update — escalates to dev team

User's Statement

"I got an offer to subscribe to the most expensive plan, receiving 150% usage. I did subscribe to it, but I didn't receive the extra usage credits. I checked the screenshot in the website and it was supposed to say that the extra usage is active. I've paid 168 USD and my weekly limit is about to end in the second day of use. Is there any way to check if I received the extra credits, and understand how is it possible that I spent my weekly credits in less than 48 hours? I'm using a single chat."
— RickLock, Discord

---

📸 Evidence

Moderator Confirmation

Roman | Z (Volunteer/Mod) verified the issue:

"Looks same on my side after last update. I will report to dev team."

Additional verification: Roman confirmed identical behavior on ZCode for OSX — indicating this is not platform-specific but a backend/account-wide issue.

---

🎯 Root Cause Hypothesis

Likely Causes (in order of probability):

1. Promotion Code Not Linked to Billing System

   • Marketing promo (150% bonus) may not be wired to the actual quota allocation backend
   • Payment processes ✅ but credit multiplier ❌

2. Post-Update Regression

   • Issue appeared/confirmed "after last update" (per mod observation)
   • Recent ZCode update may have broken credit bonus application logic

3. Plan Tier Configuration Error

   • $168 plan may be mapped to wrong quota tier in backend
   • Bonus multiplier variable not set for this SKU

4. UI Display Bug Only

   • Credits MAY be applied but UI fails to show bonus status
   • Less likely given user's rapid quota depletion

---

🛠️ Proposed Fix

Immediate Actions Required:

1. Audit RickLock's Account

   • Verify actual quota allocated

2. Check All $168 Plan Subscribers

   • This is likely affecting all users on this tier, not just RickLock
   • Run DB query to find all Coding Max subscribers
   • Verify bonus flag status for each account

3. Fix Backend Logic

   ON subscription(plan_id, user_id):
       IF plan_id == "coding_max_168":
           base_quota = get_base_weekly_quota()
           bonus_multiplier = 2.5  // 150% 
           apply_quota(user_id, base_quota * bonus_multiplier)
           SET promotion_active = TRUE
           LOG "Bonus credits applied"
   ``
   
   

---

🔗 Discord Thread Reference

Original Report: https://discord.com/channels/1346756824233148527/1540037636977205298

Submitted by: Roman Galaxys10 (Roman) — Z.ai Volunteer Ambassador
Discord: bignavi_x
GitHub: romangalaxys10-spec
Source: Discord #✅│report-a-bug Channel — User: RickLock

Start with the linked Discord thread and the report of the GLM Coding Max $168 subscription, then compare the affected account’s allocated quota with the advertised 150% benefit. Check whether other subscribers on the same tier are affected; the issue is done when the bonus allocation and its visible status are verified for the tier and the affected account is corrected.