The Public Pay module enables WHMCS clients to share a secure, unique link that lets third parties submit payments directly toward open invoices or account balances. As of build 2.0.1 the module automatically inserts the Public Pay link into the client area Shortcuts menu, positioned immediately above the Logout option. This applies to the native WHMCS 6 template and any templates built for it. Manual edits are unnecessary unless you need a custom location or run an older module build.

Automatic menu integration reduces setup time and ensures consistency across client accounts. The menu link is visible only to authenticated users, while the shareable public link uses a hashed identifier that routes payments without exposing login credentials. The module must be activated and configured for either link to resolve correctly. Proper placement improves client workflow and decreases the volume of payment-related support requests.

#Automatic Integration Since Build 2.0.1

Beginning with build 2.0.1 the Public Pay module registers its menu item directly with WHMCS. The link appears in the Shortcuts menu without requiring template changes. This behavior targets the standard clientareahome.tpl and related navigation includes used by WHMCS 6 and compatible custom themes. Administrators upgrading from earlier module versions will see the link appear immediately after the update completes and the cache is cleared.

The automatic addition preserves the original menu order and styling. No additional Smarty variables or hooks are needed in most installations. If your site uses a heavily modified template that overrides core navigation files, verify that the module's hook still fires; otherwise fall back to the manual insertion method below.

When custom placement is required or for installations running builds prior to 2.0.1, edit the client area template files directly. The most common location is clientareahome.tpl, which renders the main dashboard visible immediately after login. Open the file in a text editor, locate the section where navigation or shortcut links are rendered, and insert the link at the desired point in the markup. Save the file, clear WHMCS template cache, and reload the client area to confirm.

Follow these steps for safe editing: first back up the original template, second identify an appropriate unordered list or navigation block, third insert the link so it inherits existing CSS classes for consistent appearance, and fourth test both desktop and mobile views. The module must be activated and configured or the destination page will return an error.

html 
Public Pay (Group Pay)

Use the exact label shown above when adding the menu item so clients recognize the feature. Wrap it in a standard anchor tag that points to the module route if your template does not rely on WHMCS menu hooks. Maintain consistent spacing and HTML structure to prevent layout breakage across different screen sizes.

#Common Template Locations

  • clientareahome.tpl — primary dashboard displayed after login
  • clientarea.tpl — base layout that many pages extend
  • includes/navmenu.tpl or similar navigation partials

The menu link labeled Public Pay (Group Pay) is restricted to clients logged into the WHMCS client area. From that interface they generate or copy a public link that can be shared with anyone. This public URL follows a strict format containing a module identifier and a unique hash that maps the payment back to the correct client account or invoice group.

html 
index.php?m=public_pay&hash_id=xxxxxxx

The hash_id parameter is automatically generated by the module and should never be manually altered. Distribute this full URL to payers. It does not require WHMCS login, keeping the process simple for external users while protecting client account security. Log entries on the module page track all payments received through these links.

#Prerequisites and Troubleshooting

  • Public Pay module installed, activated, and fully configured inside the WHMCS admin area
  • WHMCS 6 native template or a derivative that respects core menu hooks
  • Clients must be logged in to see the Shortcuts menu link
  • Template cache cleared after any file modifications

If the link fails to appear, first confirm the module build number, then inspect the rendered HTML for duplicate or overriding navigation blocks. Templates that replace the entire header or menu may need an explicit include statement. Check error logs for Smarty compilation issues. Avoid placing the link inside conditional blocks that exclude certain user groups.

Test the public link end-to-end by generating a fresh hash from a test client account and completing a sample payment. This confirms routing, email notifications, and invoice status updates all function as expected.

Correctly exposing the Public Pay link simplifies third-party payment collection while preserving account security through hashed URLs. Review template changes after WHMCS core updates. Contact our support department with any questions about module behavior or template conflicts.