Appearance
FAQ
Quick answers to the questions buyers ask most about PayGlocal for WHMCS.
Is this hosted checkout or on-site card entry?
It's hosted checkout. Customers are redirected to PayGlocal's secure PayCollect page to pay, then returned to WHMCS with the invoice marked paid. Card details are never entered on your site.
Is card data stored in WHMCS?
No. No card data is stored by the module. Because payment happens on PayGlocal's hosted page, sensitive card details never touch your server.
Does it handle one-time or recurring payments?
Both. The module ships two gateways: PayGlocal for one-time PayCollect payments, and PayGlocal Recurring for automatic renewals via PayGlocal Standing Instructions (SI). They install together, share one license and one set of credentials, and you activate whichever you need. See How recurring payments work.
How do recurring charges work?
The customer authorises a mandate on their first payment; after that the WHMCS daily cron auto-charges eligible unpaid invoices assigned to PayGlocal Recurring. One active mandate per client covers all their invoices, and any charge above your configured SI Maximum Amount Per Payment is skipped. See How recurring payments work.
What payment methods can customers use?
PayGlocal's PayCollect checkout accepts credit and debit cards and alternative methods for international payments, on PayGlocal's own hosted page.
How do the payments get verified?
- Callback verification: PayGlocal sends a signed JWS callback, verified before marking invoices paid.
- Status cross-check: The gateway queries PayGlocal's status API to confirm the transaction state and details.
Can I test before going live?
Yes. Set Test / Sandbox Mode = Yes to use PayGlocal's UAT environment with your UAT keys. Switch it to No with production keys when you're ready to go live. See the going-live guide.
What keys do I need, and where do they go?
- Key pair: Merchant private key and PayGlocal public key in
.pemformat from the GCC dashboard. - Identifiers: Each key has an associated Key ID (KID).
- Setup: Enter absolute paths and KIDs in gateway settings. See Key Setup.
Where do I put the keys on the server?
Upload both .pem files to a secure directory outside the web root, set chmod 640, and point the gateway's file-path fields at them.
How do updates work?
Updates are manual. You download the new version from your relyweb.co client area and overwrite the module files — there's no in-app updater. See Updating.
What happens if my license lapses?
Payment processing is disabled while the license is inactive — new PayGlocal payments won't be taken until it's active again. Renew or re-enter your key and save to restore processing. See Licensing.
Where do I see what happened to a payment?
In Utilities → Logs → Gateway Log. Every PayGlocal attempt is recorded there, which is the first place to look when a payment fails.
Does it need anything special on my server?
PHP 8.2+, WHMCS 8.13+ (or 9.x), the ionCube Loader, curl and openssl, and SSL on your WHMCS domain for the callback. Recurring billing additionally needs the WHMCS daily cron running. Full details are on Requirements.