Skip to content

FAQ

Quick answers to the questions buyers ask most about PayGlocal Recurring. For step-by-step help, see Configuration and Troubleshooting.

Does the customer re-enter their card details for every payment?

No. The customer pays and authorises a mandate just once, on their first payment. After that, WHMCS charges future invoices automatically against that mandate — the customer never re-enters card details. See Payment flow.

What invoice types does it cover?

All of them. The mandate is stored per client, so one authorisation covers hosting, domains, addons and any other billable item that client is invoiced for.

How is the recurring amount capped?

You set a maximum with the SI Maximum Amount Per Payment setting, expressed as a multiple of the first invoice amount (1x–5x, default 2x). For example, at 3x a first invoice of 100 USD allows later charges up to 300 USD. Any invoice above the mandate's maximum is skipped automatically, so a customer is never charged more than they authorised.

When exactly are invoices charged?

The WHMCS daily cron attempts payment a set number of days before an invoice's due date, controlled by the Days Before Due Date to Charge setting (1–5 days, default 2). At 2 days, an invoice due March 20 is charged on or after March 18.

Do I need the WHMCS cron running?

Yes — it's essential. The WHMCS daily cron is what performs the automatic recurring charges. Without it, first payments still work but renewals won't be charged. If renewals aren't happening, see Troubleshooting.

Is card data stored in WHMCS?

No. No card data is stored. Payments happen on PayGlocal's hosted checkout, and the gateway keeps only the mandate identifiers needed to charge future invoices. See Security.

What happens if my license lapses?

The license-gated feature is payment processing itself — if the license becomes inactive, payment processing is disabled until it's active again. Re-enter or renew your key in Setup → Payment Gateways → PayGlocal Recurring. See Licensing.

How do I test before going live?

Set Test / Sandbox Mode = Yes to use PayGlocal's UAT (sandbox) environment while you set up, then switch it to No for live. Your RSA keys must match the environment (UAT keys for sandbox, production keys for live). The going-live guide walks through the switch.

How do updates work for a payment gateway?

Manually — there's no in-app updater. Download the latest version from your WHMCS client area, then overwrite the gateway files in your WHMCS modules/ and includes/ directories, and confirm your settings are intact. See Updating.

Where do I enter my license key?

In the gateway configuration itself — the License Key field under Setup → Payment Gateways → PayGlocal Recurring — not in an addon panel. See Configuration.

What happens to a mandate if I deactivate the gateway?

Deactivating the gateway stops WHMCS from taking new payments and from running auto-charges, but it does not revoke existing mandates at PayGlocal. If you need to revoke a mandate, do so in PayGlocal. See Uninstalling.

What happens to a mandate if I delete a client?

Deleting a client in WHMCS automatically revokes that client's active mandate with PayGlocal, so no further charges can be made against it.

Can a client have more than one active mandate?

No — there's only one active mandate per client. Authorising a new mandate supersedes the old one. See How recurring mandates work.

Do UAT and production use the same keys?

No. The RSA keys and their KIDs must match the environment: UAT keys for sandbox and production keys for live. Using the wrong set causes signature verification to fail — see Troubleshooting.

Documentation for the Relyweb app catalogue.