What the Logs screen shows
Go to FaltaPay > Logs. This shows a plain text log of what FaltaPay has sent to and received from your payment gateway, plus any errors. It is a debugging tool, not a transaction ledger: FaltaPay has no separate screen listing every payment. To see a specific payment’s outcome, look at the order, membership or donation it belongs to in WooCommerce, ProfilePress, or whichever plugin you sold it through; the log is for working out why something went wrong, not for browsing what has been paid.
Errors are recorded automatically: a failed checkout, a declined refund, a renewal that could not be charged, a webhook that failed verification, or a payment result that could not be matched to an order. Successful requests and responses are only recorded when Log API requests and responses is switched on under FaltaPay > Settings > Advanced. Turn this on while you are setting up or troubleshooting, and off again once things are stable; it captures every API call, so the file grows quickly with it on.
Reading a log line
Each line is timestamped in UTC and starts with its level, INFO or ERROR, followed by a message and, where relevant, a block of context data as JSON:
[2026-08-06 09:14:22] ERROR: WooCommerce renewal failed: Card declined {"subscription":482}
Credentials and card data are never written to the log, even in debug mode. Access tokens, entity IDs, webhook secrets, card numbers and CVVs are replaced with *** before a line is saved, so the log is safe to share when asking for support.
Tying a log entry to an order or membership
The fastest route is usually the reverse of what you might expect: start at the order, not the log.
- Open the order, transaction or subscription in WooCommerce, ProfilePress, or whichever plugin took the payment.
- Read its notes. A successful payment always gets a note with the FaltaPay transaction ID and whether it was confirmed on the shopper’s return to your site or by the gateway’s webhook, for example “FaltaPay payment completed. Transaction ID: 8ac7a4c8… (webhook)”. A failed one gets a note with the gateway’s own error message.
- If you need the raw request or response behind that note, open FaltaPay > Logs and search the page (Ctrl+F or Cmd+F) for the order ID, subscription ID or transaction ID from the note.
The context data on an error line usually includes the internal ID FaltaPay was working with at the time: order_id, txn_id or subscription, depending on which plugin raised it. Match that against the order or subscription you are investigating.
Where log files live
Log files are stored in wp-content/uploads/faltapay-logs/, one file per calendar day, named with a random per-site suffix so the file cannot be guessed from its URL. A .htaccess file in that folder blocks direct web access to anyone but you. The Logs screen only displays the current day’s file; earlier days remain on disk and are not shown in the admin, so ask your host or use an FTP/file manager to reach them if you need to look further back than today.
A file over roughly 200 KB is shown from the end only, since the most recent entries are the useful ones on a screen that keeps growing.
Clearing logs
Click Delete all logs on the Logs screen to remove every log file, not only the one currently shown. Do this after you have finished troubleshooting, or on a schedule if you keep debug logging switched on for an extended period, since nothing else clears these files automatically.
Troubleshooting
Nothing logged yet, even though a payment was just attempted. Errors are always logged, so a genuinely empty log after a failed payment usually means the request never reached FaltaPay at all; check the payment method actually appeared and was selected at checkout. For a successful payment to appear here, debug logging has to be switched on first.
I cannot find a specific transaction in the log. If debug logging was off at the time, only errors were recorded, so a payment that succeeded without incident will not appear at all. Check the order’s own notes instead; that is where a successful transaction ID is always recorded regardless of the debug setting.
The log file is enormous and hard to search. Turn off Log API requests and responses once you have finished setting up, then click Delete all logs to start clean.