Native WHMCS Integration
Accept PayGlocal payments through the standard WHMCS invoice and gateway workflow.
PAYMENT GATEWAYWHMCS 8.x and compatible WHMCS 9.x releases
ANGLEMODULES / PAYGLOCAL-PAYMENT-GATEWAY
PayGlocal for WHMCS
Accept international payments securely through PayGlocal’s hosted checkout directly from WHMCS, with signed callback verification, automatic invoice payment confirmation and production-ready transaction validation.
MODULE OVERVIEW
Built for serious WHMCS operations.
PayGlocal for WHMCS connects your WHMCS billing system with PayGlocal’s hosted PayCollect checkout.
Customers can open an unpaid WHMCS invoice, select PayGlocal and continue to a secure hosted payment experience. After payment, the module verifies PayGlocal’s signed callback before applying the transaction to the corresponding WHMCS invoice.
The integration validates the invoice reference, merchant identity, payment amount, transaction identifier and cryptographic signature. Unsigned or altered callback data cannot mark an invoice as paid.
Administrators can configure the merchant credentials, environment, key-file locations, payment-button text and diagnostic logging from the standard WHMCS payment gateway settings.
The module includes AngleModules domain-bound licensing with RSA-signed validation and a controlled offline grace period. The licence key and current status are managed directly from the PayGlocal gateway settings.
This release is designed for secure customer-initiated invoice payments. WHMCS will continue generating renewal invoices normally, and customers can pay those invoices through PayGlocal. Automatic recurring card charging is not included unless PayGlocal supplies and approves a separate tokenisation or mandate API for your merchant account.
Customers can open an unpaid WHMCS invoice, select PayGlocal and continue to a secure hosted payment experience. After payment, the module verifies PayGlocal’s signed callback before applying the transaction to the corresponding WHMCS invoice.
The integration validates the invoice reference, merchant identity, payment amount, transaction identifier and cryptographic signature. Unsigned or altered callback data cannot mark an invoice as paid.
Administrators can configure the merchant credentials, environment, key-file locations, payment-button text and diagnostic logging from the standard WHMCS payment gateway settings.
The module includes AngleModules domain-bound licensing with RSA-signed validation and a controlled offline grace period. The licence key and current status are managed directly from the PayGlocal gateway settings.
This release is designed for secure customer-initiated invoice payments. WHMCS will continue generating renewal invoices normally, and customers can pay those invoices through PayGlocal. Automatic recurring card charging is not included unless PayGlocal supplies and approves a separate tokenisation or mandate API for your merchant account.
Compatibility
- Current version
- 1.1.6
- Platform
- WHMCS 8.x and compatible WHMCS 9.x releases
- Requirements
- WHMCS 8.x or newer
PHP 7.4 or newer
PHP cURL and OpenSSL extensions
HTTPS-enabled WHMCS installation
Active PayGlocal merchant account
PayGlocal Merchant ID and Key IDs
PayGlocal public key in PEM format
Merchant private key in PEM format
Active AngleModules licence
PRODUCT TOUR
See the module in action.
Product screenshots are being prepared.
CAPABILITIES
Everything included.
Hosted PayGlocal Checkout
Customers continue from their WHMCS invoice to PayGlocal’s hosted payment page.
Automatic Invoice Confirmation
Successfully verified payments are automatically applied to the correct WHMCS invoice.
RSA-Signed Callback Verification
PayGlocal callback tokens are cryptographically verified before an invoice can be marked paid.
Invoice and Amount Matching
The module confirms the invoice reference and paid amount before recording a transaction.
Duplicate Payment Protection
WHMCS transaction checks prevent the same PayGlocal transaction from being credited twice.
Encrypted Payment Requests
Payment initiation data is encrypted and signed before transmission to PayGlocal.
UAT and Production Modes
Switch between PayGlocal testing and live environments from the gateway configuration.
Sanitised Debug Logging
Optional diagnostics remove keys, signatures and tokens before information enters the WHMCS gateway log.
LICENSING
Choose how you want to own it.
Monthly
INR 499.00- 1 production installation(s)
- 1 staging installation(s)
- Plan-defined updates
- Customer portal downloads
Monthly
USD 4.99- 1 production installation(s)
- 1 staging installation(s)
- Plan-defined updates
- Customer portal downloads
Support
Technical support is provided while your AngleModules licence and applicable support entitlement remain active.
Support covers module installation guidance, configuration assistance, licensing issues, confirmed defects and compatibility problems involving supported WHMCS and PHP versions.
Support does not include PayGlocal account approval, merchant onboarding, KYC, settlement disputes, chargebacks, custom API development, server administration, WHMCS customisation or problems caused by third-party themes, hooks, modules or modified source files.
PayGlocal controls merchant eligibility, supported currencies, transaction approval, settlement timelines and production credentials. These matters must be handled directly with PayGlocal.
Customers may be asked to provide sanitised WHMCS gateway logs, PHP error logs and environment details. Private keys, complete credentials and cardholder data must never be submitted in support tickets.
Updates and compatibility fixes are provided according to the purchased licence plan. A valid licence may be required to download updates and receive technical support.
Refund policy
Because this is downloadable software containing licensable source code, purchases are generally non-refundable after the module has been downloaded, activated or used in a production environment.
A refund may be considered when:
• A duplicate payment was made.
• The wrong licence was supplied and has not been downloaded or activated.
• A reproducible defect prevents the module’s primary advertised functionality and AngleModules cannot provide a reasonable correction.
• A refund is required under applicable law.
Refunds are not provided when:
• PayGlocal rejects or delays merchant approval.
• The merchant account does not support a requested country, currency, card type or payment method.
• Production credentials or API access have not been issued by PayGlocal.
• The customer’s server does not meet the published requirements.
• The module was installed incorrectly or modified by the customer or a third party.
• The customer expected automatic recurring charging, tokenisation or mandate functionality that is not advertised as included.
• The customer changes their mind after downloading or activating the software.
Eligible requests must be submitted within seven days of purchase with sufficient diagnostic information. Approved refunds are returned through the original payment method where technically possible. This policy does not limit statutory consumer rights that cannot legally be excluded.
Secure licensing
RSA-signed validation, domain-bound activations and an offline grace period protect both your installation and the product.
YOUR QUESTIONS
Frequently asked questions.
What does this module do?
It connects WHMCS invoices to PayGlocal’s hosted PayCollect checkout and automatically applies successfully verified payments to the appropriate invoice.
Does the module collect card information inside WHMCS?
No. Customers are redirected to PayGlocal’s hosted checkout. Payment information is handled within PayGlocal’s payment environment.
Does it automatically mark invoices as paid?
Yes, but only after the module verifies the signed callback, invoice reference, transaction ID, merchant ID and payment amount.
Does it support WHMCS renewal invoices?
Yes. When WHMCS generates a renewal invoice, the customer can use PayGlocal to pay it like any other unpaid invoice.
Which currencies are supported?
The module sends the currency assigned to the WHMCS invoice. Actual currency acceptance depends on the currencies enabled and approved for your PayGlocal merchant account.
Can I test it before going live?
Yes. Select the UAT/Sandbox environment and use the UAT credentials and keys supplied by PayGlocal.
Are separate production credentials required?
Yes. Production normally requires the production Merchant ID, Key IDs and PEM keys issued or approved by PayGlocal.
Where should the PEM files be stored?
Store them outside the publicly accessible web directory wherever possible. The files must remain readable by the PHP/WHMCS process.
What happens if the same callback is delivered twice?
The module uses WHMCS duplicate transaction checks to prevent the same transaction from being credited multiple times.
Can I change the payment-button text?
Yes. The customer-facing button text can be configured from the PayGlocal gateway settings.
What happens if the licensing server is temporarily unavailable?
A previously verified RSA-signed response can remain valid during the server-defined offline grace period. A new installation without a valid signed cache requires successful online validation.
READY TO DEPLOY?