WHMCS.Community
-
WHMCS Beta Program
-
- 24
- posts
-
-
WHMCS.Community
-
Using WHMCS
-
- 13.1k
- posts
-
- 6.5k
- posts
-
- 6.1k
- posts
-
- 96.4k
- posts
-
- 28.6k
- posts
-
- 855
- posts
-
-
WHMCS Showcase
-
Developing & Extending WHMCS
-
Third Party Add-ons
A place to discuss third party modules, add-ons and extensions for the WHMCS platform.
- 18.7k
- posts
-
- 22.9k
- posts
-
- 59.1k
- posts
-
- 636
- posts
-
- 183
- posts
-
-
Community Competitions
-
- 626
- posts
-
- No posts here yet
-
-
General Discussions
-
- 40.1k
- posts
-
-
General Feedback & Assistance
-
- 8.7k
- posts
-
- 6
- posts
-
-
Club Forums
-
- No posts here yet
-
- 51
- posts
-
- 149
- posts
-
- 17
- posts
-
- 523
- posts
-
- 494
- posts
-
- 108
- posts
-
- No posts here yet
-
- 69
- posts
-
- 90
- posts
-
- 6
- posts
-
- 7
- posts
-
- 5
- posts
-
- No posts here yet
-
- 29
- posts
-
- No posts here yet
-
- 30
- posts
-
- 298
- posts
-
- 20
- posts
-
- 22
- posts
-
-
Member Statistics
116345
Total Members11199
Most Online
-
Community Statistics
82k
Total Topics377.1k
Total Posts -
Who's Online 1 Member, 0 Anonymous, 3483 Guests (See full list)
-
Popular Contributors
-
1
-
2
-
3
-
4
-
5
-
-
Our picks
-
![[From the Blog] WHMCS 9.1 Is Now Available](//storage.whmcs.community/monthly_2026_10/whmcs91.png.1bfe575deb67063d976fa5af8b0156ff.png)
[From the Blog] WHMCS 9.1 Is Now Available
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
WHMCS 9.1 is here! The latest release is now available and supported for use in production environments, bringing new ways to manage billing, simplify routine maintenance, and build more flexible customer experiences. Whether you want greater control over invoice handling, an easier way to get started with MarketConnect, or less manual work keeping your installation up to date, WHMCS 9.1 has something for you. The release also introduces PHP 8.4 support and expands the possibilities for...View the full blog post-
0
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
![[From the Blog] WHMCS 9.1 Beta Now Available](//storage.whmcs.community/monthly_2026_10/whmcsheader91beta.png.edbcd64ce9f791b06baed31a5b6fcc7d.png)
[From the Blog] WHMCS 9.1 Beta Now Available
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
The WHMCS 9.1 Beta is now available for testing on staging environments. Whether you're testing your own integrations and templates, running it on staging to see how it affects your day-to-day work, or just want to help us catch issues before general availability, here's what's changed. Please don't run this build in production. Get it on the WHMCS 9.1 Beta landing page. WHMCS 9.1 Beta includes the following new functionality and enhancements: Credit and Debit Notes, with Invoice Immutability...View the full blog post-
0
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
![[From the Blog] WHMCS 9.0 Release Candidate OUT NOW](//storage.whmcs.community/monthly_2025_12/whmcs9-rc-blog-fin.png.c46266bad8fb542c4a5855754481b67c.png)
[From the Blog] WHMCS 9.0 Release Candidate OUT NOW
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
We're excited to announce the availability of the WHMCS 9.0 Release Candidate!-
1
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
-
Topics
-
-
Posts
-
By WHMCS Carlos · Posted
@pixelweb001 The original email where sent, if possible PM me your email you use with us so I can check if it was on the list -
By Waqas Ahmed Waseer · Posted
It works, but not with the app talking to WHMCS directly. Plan on a small backend in the middle, even if everything else is no-code. The WHMCS API authenticates with admin-level API credentials. Those can act on any client account, so they must never ship inside a mobile app, where anyone can extract them. A lot of no-code builders will happily let you paste credentials into an API connector, and that's the trap to avoid. Have the app call your own small service (a serverless function, or a little PHP or Node endpoint), keep the API credentials only there, and lock them to that server's IP with the API IP restriction setting. For login, WHMCS can act as an OpenID Connect provider (Configuration > System Settings > OpenID Connect). If the builder supports a generic OAuth2/OIDC login, clients sign in with their existing WHMCS account, and your backend maps the verified login to their client ID. That way a client can only ever see their own services and tickets, because the backend takes the client ID from the login, never from whatever the app sends. For the features you mentioned, the backend calls GetClientsProducts for account and service status, GetInvoices for billing, and OpenTicket / GetTickets for support. For payments I wouldn't build checkout into the app at all. Have the backend call CreateSsoToken and open the invoice or billing page of the WHMCS client area in a browser view. The tokens are single-use and valid for at most 60 seconds, so generate one when the user taps, not in advance. Your existing gateway, 3D Secure and fraud checks keep working, and you don't drag card handling into the app. Before committing to a builder, I'd check four things: Custom OAuth2/OIDC login, not only its own user system or social logins. Calling your own REST endpoints with a bearer token in the header. Opening a URL in an in-app or external browser. Whether you can host or export the backend logic yourself. If it fails the first two, it will fight you later. Honestly, for a new hosting business I'd start with a mobile-friendly client area theme and add a native app once clients actually ask for one. Most of what they need day to day (pay an invoice, open a ticket, check a service) already works in the client area on a phone. -
By Waqas Ahmed Waseer · Posted
@Nathan Davis The cancelled original stays out of the paid sequence entirely. With Sequential Paid Invoice Numbering on, an invoice only takes a number from that sequence at the moment it's paid. Until then it's a proforma, identified by its internal invoice ID. So the one you cancel never uses up a paid number, and the replacement picks up the next number when the client pays it. Nothing gets skipped. For reconciliation that leaves you with two different references: The invoice ID (the one in the URL). The cancelled original and the replacement each have their own, and the IDs will drift away from the paid numbers over time. That's normal. The paid invoice number. Only the replacement gets one, once it's paid. If your accountant works off the paid sequence, the cancelled original simply never appears there, and the "Replaces invoice #" note ties the two together for the client and for anyone searching later. One case behaves differently: if you cancel or refund an invoice that was already paid, it keeps the paid number it was given, so the sequence still has no gap. It's worth checking how your invoice template labels those, because some older custom templates print "Proforma" for anything that isn't marked Paid. -
By Waqas Ahmed Waseer · Posted
@HSc I'd lean toward product addons rather than configurable options for this, mainly because of your three requirements. Configurable options fold into the product's price as one line item and share its billing cycle. The types are Dropdown, Radio, Yes/No and Quantity. None of them is free text, so you can't store a mailbox address in one. That's likely why hiding them still felt wrong. You'd need a separate custom field on the product, and one option doesn't map well to "several mailboxes, each upgraded differently." Addons are billed as separate items, and they cover all three of your needs: 1. Create a Recurring addon. For sizes, either make one addon per tier (1GB, 2GB, 5GB), or one addon priced per 1GB with Allow Multiple Quantities turned on, so quantity equals GB. Separate tiers are easier for clients to read. The quantity route is simpler if your pricing is linear. 2. Turn on Prorata Billing for the addon. It syncs the addon's due date to the parent service, using the parent's prorata settings. That gives you the yearly anniversary alignment. 3. Add a required text Custom Field to the addon, something like "Mailbox address". Each purchase then names the mailbox it applies to. 4. Assign the addon to your email product. Clients can order it under Available Addons, or staff can add it. Do one addon instance per mailbox upgrade. One caveat, since you're not on cPanel: WHMCS won't resize anything on its own. Your module or manual process has to read the addon's custom field and apply the quota. If you have a provisioning module, check whether it handles addon events. Otherwise you'll need a small hook or a staff task. Test the prorata date on a dummy service before going live, so you can confirm the due dates land where you expect. What are you using on the mail side to set quotas? -
With the release of WHMCS 9.1.0, we're pleased to announce that all our WHMCS themes, client area templates, admin themes, and order forms have been updated and are now compatible with the latest WHMCS version. Our latest releases also include PHP 8.4 and ionCube Loader 15 support, along with various improvements, bug fixes, and UI enhancements. Updated Themes & Templates HostX – v3.1.2 https://whmcsglobalservices.com/web-hosting-themes-templates/hostx/ CloudX – v1.1.2 https://whmcsglobalservices.com/web-hosting-themes-templates/cloudx/ ClientX – v3.3.3 https://whmcsglobalservices.com/clientarea-template/clientx/ TwentyX – v1.3.4 https://whmcsglobalservices.com/clientarea-template/twentyx/ AdminX – v1.1.3 https://whmcsglobalservices.com/web-hosting-admin-themes-templates/whmcs-adminx/ Updated Order Forms One Step Checkout (OPC) – v2.5.4 https://whmcsglobalservices.com/custom-template/one-step-checkout-whmcs-orderform-template/ VueJS WHMCS One Step Checkout – v2.4.1 https://whmcsglobalservices.com/custom-template/vue-one-step-checkout-orderform/ What's Included? Full compatibility with WHMCS 9.1.0. Support for PHP 8.4 and ionCube Loader 15. Updated language files following WHMCS 9.x naming conventions. Improved mobile responsiveness across themes and order forms. Various bug fixes, stability improvements, and compatibility enhancements. Demo: http://demo.whmcsglobalservices.com/ We recommend all existing customers update to the latest versions to ensure smooth operation with WHMCS 9.1.0. Have questions or need assistance with the updates? Feel free to reach out to our support team. -
Yes I'm on 9.1.0. Happy to provide details here. Ask away. Recent tickets (over the past 12 months) result in copy/paate replies stating that yes we are aware and it will fixed but no timeline is available. Request to escalate have been met with, no that's not possible. -
-
By WHMCS Carlos · Posted
Hi everyone, We have listened to feedback from the community and from our customers, and we are extending the end of life for WHMCS 8.13 from December 31, 2026 to January 31, 2027. December is a busy month for most of you, with year-end closing, code freezes and the holidays. Moving from 8.13 to 9.x is a major upgrade, and it deserves proper time to plan and test. The extra month gives you that window in January. 8.13 continues to receive security fixes until January 31, 2027. After that date your installation keeps working, but we will not release any further patches for it. WHMCS 9.1 is available now and is the version to upgrade to. Before you upgrade, back up your files and database, check your PHP version and module compatibility, and test key workflows on a staging copy. PHP 8.2 reaches its own end of life on December 31, 2026. WHMCS 9.1 supports PHP 8.2, 8.3 and 8.4, so this is a good time to move to a newer PHP version too. Update to WHMCS 9.1 before you move to PHP 8.4. The docs are being updated with the new date, and all customers in 8.13.x will receive an email confirming it. -
By WHMCS Carlos · Posted
@Damo so you are on 9.1.0, the permission is enabled, and the option still doesn't show? That shouldn't happen. Please open a support ticket so the team can look at your setup -
Access is enabled. As for timing, if it's a critical security related issue then it should be patched immediately. This auto update feature is seemingly becoming more an automated tool to roll out 'features' than critical updates.
-
![[From the Blog] WHMCS 9.1 Is Now Available](http://storage.whmcs.community/monthly_2026_10/whmcs91.png.1bfe575deb67063d976fa5af8b0156ff.png)
![[From the Blog] WHMCS 9.1 Beta Now Available](http://storage.whmcs.community/monthly_2026_10/whmcsheader91beta.png.edbcd64ce9f791b06baed31a5b6fcc7d.png)
![[From the Blog] WHMCS 9.0 Release Candidate OUT NOW](http://storage.whmcs.community/monthly_2025_12/whmcs9-rc-blog-fin.png.c46266bad8fb542c4a5855754481b67c.png)
