OnlineNIC

Connect your OnlineNIC reseller account to register eligible domains and manage customer domain services from WISECP.

Accessing the Screen

Open Products → Domain Names → Domain Registrars → All Modules → OnlineNIC: {admin}/module/registrars?module=OnlineNIC.

What Is on the Screen?

The screen contains account settings, default nameservers, connection testing and saving. It has no domain-import or extension-import tab, automatic cost update or cost-currency selector.

Prepare the Provider Account

Activate an OnlineNIC reseller account and confirm domain API access with the provider. The module uses XML over a TCP connection to onlinenic.com, port 30009. Allow outbound access to that port. This is the domain API, not the separate SSL REST API. Check the official domain API guide for connection requirements. PHP needs outbound socket access; intl supports internationalized domain names.

Settings

Available Actions

Connect and Check

1. On the OnlineNIC settings form, enter Account ID and Password, choose Test Mode if appropriate and check the nameservers.
2. Click Test Connection. It signs in to the XML gateway; success does not verify funds or a registry transaction.
3. Click Save Changes, reopen the form and check the saved settings. No separate WISECP server record is required.

Prepare Extensions and Prices

Open Products → Domain Names and configure an extension using the Domain Extensions guide. Assign OnlineNIC and enter registration, renewal and transfer prices in the intended currency. This module has no price feed or automatic price updates. Confirm that the extension is supported by this module and your account; the provider's full catalogue may be broader.

Keep a new sales extension inactive while checking its settings. This prevents storefront sales but does not prevent a manually submitted live operation from incurring charges. Existing account domains cannot be listed and imported through this module. Follow the Registrar Configuration guide for service mapping instead.

Manage a Domain

Open the domain under Orders → Services. Registration, incoming transfer, renewal, nameserver changes, WHOIS contacts, transfer lock and authorization-code retrieval are provided. Restore, DNS-zone records, DNSSEC, URL forwarding and email forwarding are not implemented. Do not enable customer options that depend on these unsupported features.

In WHOIS, contact data can be updated, but the registrant's name is not sent for an update. An ownership change requires the provider's process. In Transfer, authorization-code retrieval depends on the provider returning a code. Check the provider outcome before repeating a failed registration or transfer.

Child nameservers can be added and deleted, but the module does not retrieve their account list. A blank list does not prove that no hosts exist. Renaming is not supported. The current address-update request sends the old address as the address to add and the new address as the address to remove. Verify an IP change directly with OnlineNIC; do not assume it succeeded.

WHOIS privacy uses ID Shield. Purchasing its addon requests one year of protection; enabling or disabling privacy resumes or pauses existing protection. Cancellation pauses it and does not establish a refund. Customer actions depend on service settings, purchased addons and access permissions.

Check Synchronization and a Trial

1. For a trial, use Test Mode with nonempty test-only form values and a sales extension that remains inactive. Check the connection first.
2. Open a controlled domain service and read its dates, nameservers and contact information. Confirm the same values at the provider.
3. After a transfer completes, verify the expiry date and final service status. An accepted transfer request alone is insufficient.

Scheduled synchronization reads the expiry and status. Transfer completion can also apply saved nameservers, update contacts and order ID Shield when requested. It is not always a read-only operation. Connection failure can make an inactivity check appear inactive; confirm access before treating the domain as lost.

Important Notes

Required Permissions

Configuration requires Domain Registrars permission. Domain actions also depend on administrator or customer permissions and provider access.

Related Guides

• Registrar Configuration
• Domain Extensions
• Service WHOIS Contacts
• Service Transfers