Module and release scope
This guide covers PKNIC Assisted Sample 1.0.0, Extension API 1, from the reviewed product source. Its declared core range is 1.3.5–1.3.99. Use the matching released core and signed provider package; a version label alone does not install the required contracts. Source availability does not mean the module is bundled in every currently downloadable product, installed on your server, enabled or certified for your merchant/server account. Nothing in this guide enables a provider or changes your existing connections.
Open System → Domain registrars (newer source may group these as Payments, Domain services or Hosting services). Install the reviewed signed package through Modules & addons or the integration workspace's Install tab, enable the module separately, add an account/connection, save its own credentials, run its stated Test and explicitly enable the connection. Saving or retesting disables the connection until you enable it again. Start with the provider's test environment where supported; otherwise use an isolated account or server.
Exact connection fields
These are the fields declared by this module. Secret values are entered privately and encrypted by the application. Defaults are configuration hints, not approved live merchant settings. Internal fields are populated by the module and are not operator-editable.
| Key / label | Type | Required | Default / guidance |
|---|---|---|---|
account_email — PKNIC account email |
text | Yes | Use the account-specific value described below. |
portal_url — PKNIC portal URL |
url | Yes | Default: "https://www.pknic.net.pk/" |
default_ns1 — Default nameserver 1 |
text | No | Use the account-specific value described below. |
default_ns2 — Default nameserver 2 |
text | No | Use the account-specific value described below. |
This is source for an API-1 registrar plugin, not an automated PKNIC connector or a WHMCS plugin. It provides .pk namespace checking and manual registration, renewal and nameserver instructions. Availability is manual_check, never assumed available. A sync explicitly returns manual: true and does not echo local data as a confirmed remote response. The connection test validates configuration only; it does not verify login or domain ownership.
Set account_email and portal_url (normally https://www.pknic.net.pk/). Optional default nameserver fields are examples and are not submitted remotely. No credentials are embedded and no paid or DNS-changing operation is performed.
For automated integration, replace the assisted implementation using your PKNIC partner protocol documentation or an existing licensed plugin's documented service interface. Do not invent PKNIC endpoints or treat public DNS as authenticated registrar ownership. A real sync must return confirmed domain, nameservers (2–13 hosts), expires_on (YYYY-MM-DD) and an appropriate registration status; failures must not return stale local data as successful remote confirmation.
To make an installable package, sign this source using php tools/build-package.php SOURCE_DIRECTORY PRIVATE_KEY_JSON OUTPUT.zip, then install through Modules using the archive SHA-256 and a trusted publisher key. The supplied source ZIP itself is not a signed installer. Keep signing keys outside the package. Install this sample separately for development; it does not replace the existing PKNIC connection automatically.