Install the AIvikings WHMCS registrar module

What should you prepare before installing the module?

Have a WHMCS installation with registrar modules enabled, PHP cURL available, and an authorized AIvikings account with an API key. Obtain the AIvikings module package and identify the staff member responsible for its configuration. Use the domain resale guide to check that the supported operations fit your service before rollout.

Installation makes the connector available. It does not verify the storefront, customer ownership arrangements, account funding, or renewal process. Treat those as separate acceptance checks and record who will perform them.

Where do the module files go?

Copy the package's modules/ directory into the WHMCS root. The registrar directory should contain aivikings.php, logo.png, and whmcs.json at:

<whmcs-root>/modules/registrars/aivikings/

Use your normal deployment backup and access process. Record the installed package version or file checksum so another operator can tell which implementation was tested. Do not edit built-in endpoint values just to make a failed request appear successful; investigate configuration or contact support.

Activate AIvikings in the WHMCS domain registrar settings. The supplied installation guide uses Configuration > System Settings > Domain Registrars; navigation labels can differ between WHMCS versions.

Which settings do you configure?

Keep the API key in the module's protected configuration field. Do not put it in screenshots, tickets, or client emails. A test customer's name does not change which registrar account the key controls.

WHMCS-supplied nameservers take precedence over the configured fallback. If neither is supplied, the registration relies on the AIvikings account defaults. Check the complete path before presenting a hosting bundle as ready to use.

How do you import and verify TLD pricing?

Use WHMCS's Registrar TLD Sync utility, select AIvikings, and review the imported extensions. Assign the intended TLDs to AIvikings in Domain Pricing and inspect the selling prices in the customer cart.

The pricing and catalog checklist covers renewal prices, currency, and premium behavior. An import that returns data is not the same as a reviewed customer offer.

Do not enable transfer checkout on the assumption that a transfer-price row proves module support. Transfer-in returns an unsupported-operation error in the reviewed module.

What should you test before a purchase?

Start with catalog retrieval and availability lookups. Confirm that the intended TLD uses AIvikings and that errors are visible to staff. Review premium-price display if your service will offer premium names.

Check the intended registrant separately. The module does not send the WHMCS customer's contact details in its registration request, so resolve the supported contact process before ordering on behalf of a client. A saved billing address is not registration evidence.

Prepare account funds and an explicitly approved candidate for any live test. A registrar Register command can make a real purchase even when the WHMCS order uses an offline payment method. The reviewed module does not expose a sandbox switch.

What proves the first workflow works?

For an authorized registration, verify the account's domain record, intended holder, term, and delegation. Check the corresponding WHMCS record and preserve a reference to the result. If a command is uncertain, inspect the account before trying again.

Test nameserver reads and a separately authorized replacement if those form part of the offer. Verify that the requested set is actually applied. DNS zone contents and website availability require their own checks.

Set up the renewal exception process before making the catalog broadly available. The installation is operationally ready when staff can handle both a successful order and a failure without guessing whether a paid action completed.

If you need the package or help establishing the contact workflow, contact AIvikings.