Appearance
Settings reference
Every PayGlocal setting lives on one page: Setup → Payment Gateways → PayGlocal. This is a quick reference to each field — what to enter and its default. For a guided walkthrough of filling them in, see Configuration.
| Field | What to enter | Default |
|---|---|---|
| License Key | Your PayGlocal license key from relyweb.co. Enables payment processing while active. | (empty) |
| Merchant ID (MID) | Your PayGlocal Merchant ID from onboarding. Must match your merchant account. | (empty) |
| Merchant Private Key File Path | Absolute path to your merchant RSA private key .pem, stored outside the web root (e.g. /home/user/keys/merchant_private.pem). | (empty) |
| Merchant Private Key ID (KID) | The KID of your merchant private key, from Key Management in PayGlocal's GCC dashboard. | (empty) |
| PayGlocal Public Key File Path | Absolute path to PayGlocal's public key .pem file. | (empty) |
| PayGlocal Public Key ID (KID) | The KID of PayGlocal's public key (common certificate). | (empty) |
| Test / Sandbox Mode | Yes = PayGlocal UAT (sandbox); No = live. Use UAT keys with Yes, production keys with No. | No |
Match keys to the environment
The key files and KIDs must belong to the same environment as Test / Sandbox Mode: UAT keys while it's Yes, production keys when it's No. A mismatch is the usual cause of a signature-verification failure.
Gateway Log
There's no dashboard or activity panel for this gateway — every payment attempt, including errors, is recorded in the Gateway Log at Utilities → Logs → Gateway Log. Check it first whenever a payment doesn't complete.
Related pages
- Configuration — a guided walkthrough of these fields
- PayGlocal key setup — where the paths and KIDs come from
- How payments work — the flow behind the scenes
- Troubleshooting — when a payment fails