Appearance
Updating
PayGlocal Recurring is a WHMCS payment gateway, so it updates manually — there is no in-app updater, no Check for Updates button, and no Update Now. You download the latest build from your relyweb.co client area and overwrite the gateway files.
Before you update
A manual update overwrites files in place, so take a backup first — see Backup and restore. At minimum, capture:
- A WHMCS database backup — your saved gateway settings and stored mandates live here.
- A copy of the module files you're about to overwrite, and your two RSA
.pemkeys with a note of their paths and KIDs.
Download the update
Sign in to your relyweb.co client area and open the PayGlocal Recurring product to download the latest release. Your entitlement to new versions follows your license:
- Leased — you can download updates for as long as your license is active.
- Lifetime — you keep your installed version forever; downloading a newer version needs an active Support & Updates plan. If it has lapsed, your current version keeps running — renew Support & Updates to download newer releases.
Install the update
Overwrite the existing gateway files with the new copies:
modules/gateways/payglocalrecurring.phpmodules/gateways/payglocalrecurring/(the whole directory)modules/gateways/callback/payglocalrecurring.phpincludes/hooks/payglocalrecurring_cron.php
Then open Setup → Payment Gateways → PayGlocal Recurring, confirm your License Key, Merchant ID, key paths and KIDs are still in place, Save Changes, and take a sandbox test payment to confirm the flow still completes.
Your settings and mandates are safe
Overwriting the files does not change the settings you saved on the gateway page or your customers' stored mandates — those live in WHMCS and its database, not in the files you're replacing. Re-check your settings after the upload.
If an update won't apply
- Make sure every file uploaded to the correct WHMCS path and the old ones were overwritten.
- Confirm the web-server user can read the new files.
- Check your ionCube Loader is 13.0.2 or newer — a newer encoded build may need a matching loader (see Requirements).
- If payments stop after the update, re-check the License Key and settings, then review Utilities → Logs → Gateway Log.
Related pages
- Backup and restore — back up before you overwrite
- Licensing — how your license type affects updates
- Configuration — the settings you re-check after updating
- Troubleshooting — resolving post-update problems