---
url: /payglocal-whmcs/faq.md
description: >-
  Common buyer questions about PayGlocal for WHMCS — hosted checkout, card data,
  one-time vs recurring payments, sandbox testing, updates and license lapses.
---

# 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?

This gateway handles **one-time international payments**. If you need automatic renewals (standing
instructions), that's the separate **PayGlocal Recurring** product.

## 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?

Every result is **dual-verified**: PayGlocal sends a signed (JWS) callback, and the gateway
verifies that signature *and* cross-checks the outcome against PayGlocal's status API before the
invoice is marked paid.

## 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](/payglocal-whmcs/guides/going-live).

## What keys do I need, and where do they go?

You need a pair of **RSA `.pem` keys** — your merchant private key and PayGlocal's public key, each
with a Key ID (KID) — generated in the PayGlocal GCC dashboard. Their paths and KIDs go into the
gateway settings. The [key setup guide](/payglocal-whmcs/guides/payglocal-keys) walks through it.

## 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 WHMCS client area at relyweb.co and
overwrite the module files — there's no in-app updater. See [Updating](/payglocal-whmcs/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. There's no day-count; renew or re-enter your key and save to restore
processing. See [Licensing](/payglocal-whmcs/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. Full details are on [Requirements](/payglocal-whmcs/requirements).

## Related pages

* [Requirements](/payglocal-whmcs/requirements)
* [Configuration](/payglocal-whmcs/configuration)
* [How payments work](/payglocal-whmcs/features/payment-flow)
* [Licensing](/payglocal-whmcs/licensing)
* [Troubleshooting](/payglocal-whmcs/troubleshooting)