Two-factor authentication setup for WHMCS adds a second login step for the people who can reach your billing system: staff in the admin area and, if you want it, customers in the client area. Hosting companies, IPTV operators and resellers use it when they want 2FA in place without locking a single person out on rollout day. Admin-only TOTP on one install costs $99.
Why the admin login needs a second factor
A WHMCS admin account can issue refunds, edit payment gateway settings, read client records and send module commands to your servers. If one staff password is phished, or reused from a breached site, that password is all an attacker needs. With 2FA, a stolen password on its own gets nobody in. On the client side, a second factor protects customers' services and domains from account takeover, which also means fewer tickets about nameservers someone else changed.
Which 2FA method fits your team
WHMCS ships with three two-factor modules. We help you choose one for staff and one for clients, because the best answer is often different for each group.
| Method | How it works | Good fit for |
|---|---|---|
| Time Based Tokens (TOTP) | Six-digit codes from Google Authenticator, Microsoft Authenticator, 1Password or a similar app | Most teams and most clients, with no extra account or cost |
| Duo Security | Push approval or passcodes through a Duo account you control | Teams already on Duo who want central control of staff devices |
| YubiKey | One-time passwords from a physical Yubico key | Full administrators who prefer a hardware key |
SMS codes are not part of WHMCS core. If clients insist on them, Duo or a third-party module can send them, but we normally recommend TOTP because text messages can be hijacked through a SIM swap.
What the setup includes
- A review of every admin user and role, with old or shared logins flagged before enforcement
- Activation of the chosen module for staff, clients or both
- Mandatory enrollment for admins at their next login, and for clients too if you want it
- A plan for the one-time backup code WHMCS shows each user at enrollment
- Brute-force settings reviewed: login ban length and a ban whitelist for your office IPs
- A client-area announcement and a short knowledge base article on how customers enroll
- Test logins with each method on staging, then on production
- A one-page recovery procedure for your support desk
Clean up admin accounts first
Turning on 2FA is the right moment to delete admin users nobody remembers creating, split shared logins into named accounts, and trim each role to what that person actually does. Shared logins are the hardest to protect: one authenticator secret spread across several phones is barely better than a password everyone knows.
The lockout plan matters as much as the switch
Most 2FA rollouts that go wrong fail at recovery, not enrollment. A staff member replaces a phone, a customer deletes the authenticator app, or the only full administrator is on vacation. Before anything is enforced, we agree on:
- Which administrators can reset 2FA for another admin, and that there are at least two of them
- How support confirms a client's identity before removing their second factor
- Where the backup codes for owner accounts are kept offline
- How API and automation users are handled, since they never use the admin login form
What 2FA does not cover
Two-factor authentication protects the WHMCS login form. It does nothing for API credentials, the database, SSH or cPanel/WHM access to the server, or your Stripe, PayPal and registrar dashboards. We point out gaps we notice along the way, such as an API credential with full permissions and no IP restriction. For a full review of those areas, book a WHMCS security audit, and use firewall and brute-force protection to stop password guessing before it reaches the login page.
Timeline
Admin-only TOTP is usually finished within one business day of receiving admin access. A client rollout takes longer on purpose: we make 2FA optional first, publish the help article, then switch on enforcement on a date you choose so customers are warned in advance.
Pricing
| Scope | Price |
|---|---|
| Admin 2FA with TOTP on one WHMCS install, enforcement and recovery procedure | $99 |
| Admin and client 2FA with a staged rollout, announcement and help article | Fixed quote after the call |
| Duo or SMS provider setup, or several WHMCS installs | Fixed quote after the call |
| Small changes after handover | $65/hour |
If you also want exploit detection and admin activity alerts on top of 2FA, the WHMCS Security module adds them. To begin, send your WHMCS version and how many staff log in through the project form, and we will book the free call.