*Settings › Advanced* # Log Entries What the payment gateways, carriers and webhooks actually said back to your store, searchable and safe to share. 5 parts. Quick links - [What is in the log](https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/#what) - [The counters](https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/#counters) - [Finding the entry you want](https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/#finding) - [Reading an entry, and what is hidden](https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/#payload) - [Exporting and clearing](https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/#keeping) **Where to find it:** WP Admin › EasyCart › Settings › Advanced › Log Entries *The record* ## What is logged and how healthy it looks What lands in the log, and the four counters that say whether anything is going wrong right now. ### What is in the log One entry for every reply your store received Every time your store talks to something outside itself — a payment gateway, a shipping carrier, a webhook arriving from Stripe — the reply is written here. The log is read-only. Nothing on this screen changes an order, a payment or a shipment; it only tells you what was said. That makes it the first place to look when a customer says a card was refused and you cannot see why, or when a carrier stops returning rates. The order screen tells you an order failed. This tells you the sentence the gateway sent back. Each row shows **When** it happened, the **Source** that sent it, the **Order** it belongs to, a **Result** of OK or Error, and the first meaningful line of the **Response**. Entries from the last day also show how long ago they arrived. ![Settings › Log entries with the EasyCart menu: the counters, retention, filters and the latest entries.](https://docs.wpeasycart.com/wp-content/uploads/2026/11/log-entries-what-607.jpg) > **💡 Note:** This screen changes nothing. To act on what you find, go to the order under [Order Management](https://docs.wpeasycart.com/docs/administrative-console-guide/order-management/) or to the gateway under [Settings › Payments & Taxes › Payments](https://docs.wpeasycart.com/docs/administrative-console-guide/payments-setup/). ### The counters Four numbers that say whether anything is wrong right now Above the list sit four figures. **Errors · 24h** and **Errors · 7d** are the ones to read first: a store that is working normally shows a small, steady number, and a jump means something changed today. **Entries** is the total held, and **Oldest entry** tells you how far back the record actually goes, which is the honest answer to whether the log can still explain last month’s problem. Clicking a counter filters the list to it, so the error figure is also the fastest route to the errors themselves. *Using it* ## Finding, reading and keeping entries Narrowing the list to the entry you want, reading the full reply safely, and deciding how long the log is kept. ### Finding the entry you want Filters and a search built for the things merchants actually type Three filters narrow the list. **Result** has a single Errors only pill. **Source** picks one gateway or carrier. **When** offers the last 24 hours, 7 days or 30 days. The search box takes an order number, a gateway name, a transaction id or the text of an error. Words are matched independently and in any order, so *stripe declined* finds a Stripe entry whose reply says the card was declined. Wrap words in **“quotes”** to keep them together. A number also matches the order and the entry id, and **#1234** means order 1234 and nothing else. Changing the search or a filter returns you to the first page rather than stranding you on page nine of results that no longer exist. > **💡 Note:** Use #1234 to pull up one order, and “quotes” to search for an exact phrase from an error message. ### Reading an entry, and what is hidden The full reply, with card numbers and keys masked The Response column shows a one-line summary. **expand** opens the complete reply, formatted so it can be read, and **Copy payload** puts it on the clipboard, which is exactly what to paste into a support ticket. **View order** jumps to the order the entry belongs to, when it has one. What you see is masked before it reaches the screen. Card numbers keep only their last four digits, security codes are replaced, and Stripe keys, webhook secrets, passwords, API keys, access tokens and licence keys are blanked out. The masking is applied to the display and to the export, never to what is stored. So a payload is safe to copy into a support conversation, and it is still worth reading before you send it. Access tokens are never stored at all. When the store renews its connection to Square, PayPal or a shipping carrier, the entry is a short summary: the answer’s status, whether new access came back, when it runs out, and any error the service gave. Tokens that older versions wrote into the log are replaced with REDACTED after updating. > **💡 Note:** Payloads are masked before they are shown or exported, so a copied entry can go into a support ticket without exposing card numbers or API keys. Read it before you send it anyway. For a step by step walkthrough, see [How to Fix Payment Failed and Gateway Errors](https://docs.wpeasycart.com/docs/how-to-guides/how-to-fix-payment-failed-and-gateway-errors/). ### Exporting and clearing How long entries are kept, and how to take them away **Export filtered CSV** downloads exactly what the current search and filters are showing, masked the same way as the screen. Filter first, then export; exporting without filtering gives you the whole log. **Keep entries for** sets retention, with choices of 7, 30, 90 or 180 days, one year, or forever. The default is 90 days. Anything older is removed by a daily task, so the log does not grow without limit. Choosing forever stops that task entirely, which on a busy store means a table that only ever gets bigger. **Clear older than…** removes old entries straight away rather than waiting for the daily run. It deletes permanently and there is no undo, so export anything you might need before clearing. > **⚠️ Careful:** Clearing entries deletes them permanently and cannot be undone. Export what you need first. Setting retention to forever stops the daily cleanup, which on a busy store leaves a table that only grows. *Keep going* ## Related panels - [Diagnostics](https://docs.wpeasycart.com/docs/administrative-console-guide/diagnostics/): The health checks, for problems the log only hints at. - [Order Management](https://docs.wpeasycart.com/docs/administrative-console-guide/order-management/): The orders these entries belong to. - [Payments](https://docs.wpeasycart.com/docs/administrative-console-guide/payments-setup/): Gateway setup, the usual source of payment errors. - [Rates](https://docs.wpeasycart.com/docs/administrative-console-guide/shipping-rates/): Carrier rates, the usual source of shipping errors. - [Store Status](https://docs.wpeasycart.com/docs/administrative-console-guide/store-status/): Whether the store is set up to take an order at all. - [Admin](https://docs.wpeasycart.com/docs/administrative-console-guide/admin/): Admin options, including what else is recorded. ## Ready to run your store on WP EasyCart? Everything in this guide works with the free plugin. PRO and Premium add subscriptions, memberships, wholesale pricing and more. Try every PRO feature free for 14 days. [Start your free trial](https://www.wpeasycart.com/wp-easycart-professional-14-no-risk-trial/) · [See what is included](https://www.wpeasycart.com/wordpress-shopping-cart-pricing/) ![The WP EasyCart admin: orders and offers](https://docs.wpeasycart.com/wp-content/uploads/2026/09/cta-wpeasycart-pro-v2.jpg) --- Source: https://docs.wpeasycart.com/docs/administrative-console-guide/log-entries/ ( updated 2026-11-06 )