Error reference

When PayGlocal Recurring processes a payment — whether a customer's first authorisation or an automatic renewal charged by the cron — it records the outcome as a transaction status in the Gateway Log (Utilities → Logs → Gateway Log). This page lists each status you may see, what it means, and what to do about it. Filter the log to PayGlocal Recurring and match the status against the table below.

Transaction statuses

Status	Meaning	What to do
SENT_FOR_CAPTURE	Payment successful.	Nothing — the invoice is marked Paid and, on a first payment, the mandate is stored.
INPROGRESS	The payment is still processing.	Wait; it's logged as pending. If it never resolves, re-check the log for a follow-up status.
ABANDONED	The customer left PayGlocal's checkout without finishing.	Logged as failed. Ask the customer to retry and complete the payment.
ISSUER_DECLINE	The card issuer (bank) declined the payment.	Logged as failed. The customer should check with their bank or try another card.
CUSTOMER_CANCELLED	The customer cancelled during checkout.	Logged as failed. Ask them to retry when ready.
AUTHENTICATION_TIMEOUT	3-D Secure authentication timed out.	Logged as failed. Have the customer retry and complete the bank authentication promptly.
GENERAL_DECLINE	The payment was declined by the risk engine.	Logged as failed. Usually customer-side; the customer may retry or use a different card.
REQUEST_ERROR	The request data sent to PayGlocal was invalid.	Logged as failed. Check your gateway settings — MID, KIDs and key paths — and see Troubleshooting.
SYSTEM_ERROR	A PayGlocal system issue occurred.	Logged as failed. This is on PayGlocal's side; retry later, and contact PayGlocal if it persists.

Where these appear

Each status is written to the Gateway Log for the exact attempt it belongs to, so you can trace a specific invoice or renewal to its outcome.

Common failure conditions

Beyond the per-transaction statuses above, two configuration problems account for most gateway-wide failures:

• Key or KID mismatch. If your Key IDs (KIDs), key file paths, or the environment your keys belong to don't match, PayGlocal rejects the request or signature verification fails. This often surfaces as a REQUEST_ERROR or a "JWS verification failed" entry. Re-check both KIDs and both key paths against the PayGlocal GCC dashboard, and confirm UAT keys are used in sandbox and production keys in live.
• License inactive. Payment processing is disabled while the license is inactive, so charges won't run at all. Re-check the License Key and confirm the server can reach relyweb.co over HTTPS. See Licensing.

For step-by-step fixes, see the Troubleshooting page.

Related pages

• Troubleshooting — fixes for each symptom
• FAQ — common questions answered
• Settings reference — every gateway field
• How recurring mandates work
• Payment flow