Accept international payments in WHMCS — one-time or recurring.

They share the same PayGlocal SDK, JWT security, and PayCollect checkout — the difference is the payment mode. PayGlocal handles one-time payments: the customer pays each invoice on PayGlocal's hosted page. PayGlocal Recurring uses Standing Instructions (SI) to set up a mandate on the first payment, then automatically charges subsequent invoices via a daily cron.

Not necessarily. If your customers pay invoices manually, the one-time module is all you need. If you want hands-off auto-renewals, use the recurring module. Many stores run both side by side — they share the same PayGlocal merchant account and RSA key pair, so customers can choose at checkout. Each module is licensed separately.

On a customer's first payment, the module creates a PayGlocal Standing Instruction mandate (VARIABLE type, ONDEMAND frequency) and stores it against the client. A daily cron then finds invoices nearing their due date and charges them automatically through the SI Sale API. You control how many days before the due date charges are attempted (1–5), and an amount guard prevents any charge above the mandate's configured maximum.

Because mandates are stored per client rather than per service, auto-charges work for hosting, domains, addons — any billable item.

No. Both modules use PayGlocal's PayCollect hosted checkout, so customers are redirected to PayGlocal's secure payment page to enter card details. Card data never touches your server, which keeps your PCI scope to a minimum.

Every request is encrypted with JWE (RSA-OAEP-256 + A128CBC-HS256) and signed with JWS (RS256) using RSA key pairs from your PayGlocal GCC Dashboard — there are no shared API keys. On the way back, each callback is verified by its JWS signature and independently cross-checked against the Transaction Status API before WHMCS marks an invoice paid, so a spoofed callback can't trigger a false payment.

Both modules support WHMCS 7.x and 8.x on PHP 7.2 or higher (PHP 8.x recommended). ionCube Loader is required for the encoded production build, along with the curl and openssl PHP extensions and a valid SSL certificate for the callback endpoints. These are standard on virtually all WHMCS-ready hosts, including all Relyweb hosting plans.

A PayGlocal merchant account (Merchant ID / MID) plus an RSA key pair from the GCC Dashboard: your merchant private key and PayGlocal's public key, each with its Key ID (KID). For the recurring module, your PayGlocal account also needs Standing Instructions enabled. You enter the MID, key file paths, and KIDs on the WHMCS Payment Gateways page — no custom admin panel to learn.

Each module is licensed per WHMCS installation. Monthly and Annual licenses include updates and support for as long as they're active; the Lifetime license keeps updates and priority support forever for that installation. All licenses include email and ticket support, and we offer a 14-day money-back guarantee — if it doesn't work for your setup, contact support within 14 days for a full refund. We're based in Ahmedabad and support is provided in English and Hindi.