How to Connect NiceNIC with WHMCS

If the NiceNIC registrar module is installed but WHMCS is not successfully placing or tracking domain orders, follow this connection-and-first-order checklist. For the initial ZIP installation, use the official NiceNIC WHMCS setup guide.

1. Confirm the connection

Open Configuration → System Settings → Domain Registrars in WHMCS 9.0 and confirm NiceNIC is activated. In the module settings, verify the account username and API Secret from NiceNIC API Settings. Do not enter the NiceNIC website password.

If NiceNIC enforces server IP authorization, add the public outgoing IP used by the WHMCS server, not merely its advertised hosting IP or a Cloudflare address. For a new deployment, start with a read-only availability query and review the returned error, rather than attempting a registration.

NiceNIC has announced WHMCS 9.0 support; it publishes standard and V8+ registrar packages. Match the installed package to your environment before replacing production files.

2. Set up the domain products

Open the WHMCS Domain Pricing area.
Enable the TLDs you intend to offer and assign NiceNIC as registrar for new orders.
Configure retail prices and terms for registration, renewal and transfer separately. Installing the module does not automatically set the amount you charge customers.
Check currency conversion, customer contact-field mapping and any TLD-specific extended attributes.
Confirm available funds in your NiceNIC account for paid registrar actions; a WHMCS invoice payment does not automatically credit the registrar balance.
Review the current WHMCS cron configuration and how the selected module handles pending or rejected operations.

Installing NiceNIC as an additional registrar does not automatically transfer customers' existing domains from their old registrar.

3. Test the full customer-to-registry workflow

Use a read-only lookup first. When ready, choose one authorized live registration and verify each stage:

WHMCS checkout/invoice

Customer order approved and correctly priced

Module submission

Request accepted or explicitly pending; no silent authentication error

NiceNIC order

Transaction visible in NiceNIC account

Registry result

Domain registered, with correct contacts/expiry or a documented pending reason

Customer communication

WHMCS status and notices match the actual registrar result

Important: NiceNIC API examples use code: 0 for success and code: 201 for pending processing. A pending request, a gateway timeout or an HTTP 200 response is not proof that a domain has been registered. Reconcile the first transaction before another chargeable attempt.

4. Diagnose by symptom

"Unauthorized" / failed authentication: inspect credentials, authorized outbound IP and the installed module's API configuration.
Parameter/eligibility rejection: check the exact TLD, term, contacts and mandatory extended attributes.
Wrong customer price: review WHMCS retail pricing independently of the NiceNIC account-level price.
Order shows paid in WHMCS but missing at NiceNIC: confirm the module log and registrar transaction before manually resubmitting.
"Test Mode" confusion: WHMCS module testing is not automatically connected to the separate NiceNIC API Sandbox.

Do not paste credentials or unredacted customer documents into support tickets. The current module download, release guidance and troubleshooting are at NiceNIC WHMCS Integration.

Example workflow: customer renews a domain in WHMCS

A customer pays a renewal invoice for example.net. Your WHMCS system marks the invoice paid, but you must still check whether the registrar renewal action ran and the registry expiry date changed. If it did not, investigate the module log and NiceNIC transaction before resubmitting.

Confirm the WHMCS domain is assigned to NiceNIC, not a previous registrar module.
Check that the domain and TLD support the requested renewal term; some registries limit the remaining registration period or renewal window.
Check the NiceNIC balance and the active API Secret/IP restrictions on the WHMCS server.
Use the module log and the API response to distinguish payment received, request accepted and domain renewed.
Update the WHMCS customer record from the confirmed registrar result, and tell the customer the verified registry expiration date.

Transfer example

A transfer order is not complete simply because an EPP/Auth code was entered. The domain may need to be unlocked at its current registrar, and certain extensions have special processes. Record the pendingTransfer state and monitor the final status. Never send an automatic repeated paid transfer or renewal request only because the first response timed out.

Operational separation: This article focuses on connecting a configured module to live business workflows. For installing the module files and activating NiceNIC in WHMCS, use the dedicated setup guide.