A WHMCS mobile app puts your client area in your customers' pockets: they sign in with their WHMCS account, see services and domains, pay invoices, open and answer tickets, and get push alerts when something needs attention. It is for hosting, VPS and IPTV providers whose customers manage their accounts mostly from a phone, and the fixed price lands between $1,500 and $5,000 depending on the screens included. The app is published under your name in the App Store and Google Play. If a better mobile experience in the browser is enough, improving the existing client area through customer portal customization costs far less.
What the WHMCS API makes possible
Almost everything a customer does in the client area has a matching action in the WHMCS API, so an app can show:
- Services and addons through GetClientsProducts and GetClientsAddons, and domains through GetClientsDomains
- Invoices through GetInvoices and GetInvoice, with status and due dates
- Tickets through GetTickets and GetTicket, plus OpenTicket and AddTicketReply for new tickets and replies
- Profile details through GetClientsDetails and UpdateClient
- Announcements and support departments through GetAnnouncements and GetSupportDepartments
- New orders through GetProducts and AddOrder, when the app sells as well as serves
- Service actions such as a reboot, through ModuleCustom, where your provisioning module offers them
What a client app needs on top
The WHMCS API is an admin-level interface. Its credentials belong to an admin user, and any client's data can be read with them. That shapes the whole design:
- A small backend you host. The API identifier and secret live only on this server, never inside the app, where anyone could extract them. The backend answers the app's requests and adds the signed-in customer's client ID to every API call, so no one can request another account's invoices.
- Customer login through OpenID Connect. WHMCS can act as an OAuth 2.0 and OpenID Connect provider (Configuration > System Settings > OpenID Connect). The app opens your WHMCS login page, so your password rules and two-factor authentication still apply, and gets back a code the backend exchanges for the user's identity. WHMCS's developer docs describe the older ValidateLogin action as superseded and possibly deprecated in future, so we do not build on it.
- Account mapping. Since WHMCS 8.0 a user can belong to more than one client account, so the app lets that person switch between the accounts they can access.
- Payment through your existing gateways. The backend calls CreateSsoToken, which returns a one-time login link valid for at most 60 seconds, and the app opens the invoice in an in-app browser. Customers pay with the same Stripe, PayPal or NOWPayments checkout they already use, and no card data touches the app. If session IP checks on the Security tab of General Settings log mobile users out as they switch networks, we raise it with you before launch.
- Push notifications. WHMCS hooks such as TicketAdminReply, InvoiceCreated and AfterModuleSuspend tell the backend, which sends alerts through Firebase Cloud Messaging and Apple Push Notification service.
Technology and branding
We build with Flutter or React Native, which produce native iOS and Android apps from one codebase, in your colors, logo and app name, with the language files your client area already uses. The backend runs on your own server or a small VPS. The backend targets your own WHMCS branch, 8.13 with PHP 8.1+ or 9.x with PHP 8.2+, and every screen is tested against a staging copy with real test accounts.
Accounts and materials from you
- An Apple Developer Program account ($99 a year) and a Google Play Console account ($25 once), both in your company's name
- Logo files, brand colors and the app name you want in the stores
- A server for the backend and a staging WHMCS we can log in to
- The list of screens you want in the first release
Scope and pricing
| Release scope | Fixed price |
|---|---|
| Login, services, domains, invoices with in-browser payment, tickets, and push alerts for ticket replies and new invoices | From $1,500 |
| Adds account switching, profile editing, announcements and multi-language support | Fixed quote between the two ends |
| Adds ordering through AddOrder, service actions through ModuleCustom and domain management screens | Up to $5,000 |
Builds that grow past $5,000 are paid in three milestones; below that, half is due at kickoff and half on delivery. A typical release takes several weeks plus store review time, and the quote gives dates. We submit both apps for review and fix any issue found in the first 14 days after delivery.
Not included
- An app for your staff or admins
- Store account fees, which you pay directly to Apple and Google
- Updates for future iOS and Android releases after the correction window, which can be covered by hourly support at $65/hour
- Changes inside provisioning modules to add new service actions
If customers mostly want invoice and ticket alerts on their phone rather than a full app, our Telegram Bot or WhatsApp Cloud module may be the faster route.