Clients can easily generate temporary PINs in the client area and share them with the support team whenever verification is required.
Staff can verify the provided PIN directly in WHMCS, helping them protect client accounts while delivering support without unnecessary delays.

We will guide you step by step through the whole installation and configuration process.

The content of the package to upload should look like this.

The file is located in 'modules/addons/Supportpin/license_RENAME.php'. Rename it from 'license_RENAME.php' to 'license.php'.

Enter your license key between quotation marks as presented on the following screen. You can find your license key in our client area → 'My Products'.

Log in to your WHMCS admin area. Go to 'System Settings' → 'Addon Modules'. Afterwards, find 'Support PIN' and press the 'Activate' button.

To do so, click on the 'Configure' button, tick 'Full Administrator' and press 'Save Changes'.

You can access your module under 'Addons' → 'Support PIN'.
Note: Expired PINs are swept automatically by the standard WHMCS daily cron task — no additional cron command needs to be configured for this module.

In this guide, we will walk you through every section and option of the module in detail.

• Active - PINs currently valid and not yet used up.

• Used - PINs that have reached their configured verification limit.

• Expired - PINs past their expiration time.

• Revoked - PINs manually revoked by staff.

Each counter has its own 'View PINs' button, which filters the table below to just that status.

• Client ID - the client the PIN belongs to, linked to their profile.

• Status - "Active", "Used", "Expired" or "Revoked".

• Length - how many digits the PIN has.

• Single Use - whether the PIN is invalidated the first time it is used.

• Created At - when the PIN was generated.

• Expires At - when the PIN will stop being valid.

• Used At - when the PIN was verified by staff, if it has been.

Use the trash icon on a row to 'Revoke PIN' on that single entry.

• PIN Length - the number of digits generated for each new PIN.
• PIN Expiration Time (Hours) - how many hours after generation a PIN remains valid.

• Allow Multiple Active PINs - determines whether a client can have several active Support PINs at the same time.
  • When disabled, generating a new PIN automatically revokes the client's previously active PIN. Only the latest PIN remains active.
  • When enabled, generating a new PIN does not revoke previously active PINs. Several PINs may remain active simultaneously, up to the configured limit.

• Expire PIN After X Uses - determines how many successful verifications are allowed for each PIN before its status changes to 'Used' .
  • Enter 1 to make each PIN single-use.
  • Enter a higher value to allow the same PIN to be successfully verified that many times.
  • Enter 0 to allow unlimited verifications until the PIN expires or is revoked.

These settings work independently. 'Allow Multiple Active PINs' determines whether a client can have only one or multiple active PINs at the same time, up to the fixed limit of five.
In contrast, 'Expire PIN After X Uses' determines how many times each PIN can be successfully verified.

• Require PIN Verification For Client Access - when enabled, staff members cannot access a client's profile, services, domains, invoices, quotes, or tickets until they successfully verify that client's Support PIN.
  Once verified, access remains valid for the rest of the staff member's current login session.

• Deny Admin Access After PIN Expiration - when enabled, access granted through PIN verification is revoked as soon as the verified PIN expires.
  The staff member must then verify another active PIN to regain access. When disabled, verified access remains valid until the staff member's current login session ends.

• Hide Full PIN - when enabled, each PIN is displayed only once, immediately after generation.
  After that, the full PIN is masked and cannot be displayed again in either the client area or staff-facing client views, including when an administrator logs in as the client.

• Enable Generate PIN Button - shows or hides the 'Generate Support PIN' button in the client area. When disabled, clients cannot generate new PINs themselves.

Enter a valid Support PIN to open the associated client's profile directly. Unlike verification from the Client Summary page, this action does not count toward the PIN's usage limit.
If the widget is not needed, it can be disabled in the dashboard widget settings available in the top-right corner of the WHMCS dashboard. Disabling the widget does not affect any other module features.

Unlike the Home Widget verify field, a successful verification here does count against the PIN's use limit.

• is added to the bundle of maximum of 5 active PINs (option: "Allow Multiple Active PINs" is On), or
• replaces the current PIN (option: "Allow Multiple Active PINs" is Off).

For detailed guidance on using this tool, check its dedicated article, which is available here.

Staff only ever need to verify a PIN a client reads aloud, not to read it back themselves - the value is a one-way hash regardless and can never actually be redisplayed.

Combined with "Deny Admin Access After PIN Expiration", staff will need to re-verify the client for every new support interaction.

Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.

Opt for the Open Source version of your Support PIN For WHMCS module to unlock these benefits.
Simply click on either the Get Source Code or Upgrade To Lifetime button found on the product's page in our client area to complete the one-step upgrade process, with a dedicated discount already applied.

Follow a comprehensive guide covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized.

Check 'Settings' → 'Client Area' → 'Enable Generate PIN Button' is turned on.

This happens when 'Require PIN Verification For Client Access' is enabled and the previously verified PIN has expired. Ask the client to read out their current PIN again, or generate a new one, and verify it from the Client Summary panel or the module's Dashboard.

This is expected with the default policy: 'Expire PIN After X Uses' is 1 out of the box, so a PIN is spent after its first successful verification. Raise that value (or set it to 0 for no limit) in 'Settings' → 'PIN Lifecycle' if clients need to be verified more than once per PIN.