The error log in the Settings tab
What this tab is for
Your shop does a lot of work behind the scenes: it takes payments, fulfils orders, sends notifications to Discord, runs the AI assistant. If any of these tasks fails, the shop records it here — along with information about where and when the problem happened and exactly what went wrong. That way you don’t have to guess. Instead of asking “why didn’t the customer get their rank?”, you open Errors and see the exact reason.How the page is laid out
The page has two parts, one above the other:Filtering
A panel at the top with three dropdown lists. It narrows down the list so you can quickly find the errors you care about.
Shop errors
The list of entries below the filters. Each row is one recorded problem — newest at the top, oldest at the bottom.
What kinds of errors end up here
The log gathers problems from several different areas of the shop. Each area has its own coloured category badge, so you can see at a glance what an entry is about:Payment
Problems when starting a payment, receiving confirmation that money has come in, or making refunds. This is the most common category.
Order
Errors while fulfilling an order — for example when a purchased item couldn’t be delivered in-game.
Webhook
Cases where an outgoing notification — most often a message to your Discord server — wasn’t sent.
AI Assistant
Problems with the assistant that helps you inside the panel.
System
Other technical shop errors that don’t fit into the groups above.
Older entries, recorded before categories were introduced, are treated as Payment. That’s why payment errors are often the largest group on the list.
How to read a single entry
Each error on the list is one entry. On the top line of the entry, side by side, you’ll see small badges, and beneath them the full text of the error. Together they tell you everything you need:1
Category badge
The coloured label at the start of the row — it immediately shows what the error is about (e.g. Payment, Order, Webhook, AI Assistant, System).
2
Source name
The bold text next to the category — it tells you where the error came from, such as the name of the payment gateway that reported it.
3
Payment stage
For payment errors, there’s a second badge showing the stage where something went wrong: Initiation, IPN / Notification, or Refund (we explain what each one means below).
4
Response code
If the error came from the outside (e.g. from a payment provider), you’ll see an extra badge with a short numeric code. It helps determine whether the problem was on the shop’s side or the partner’s side — just give this code to support.
5
Date and time
On the right side of the row you’ll see the exact moment the error happened. Handy when you want to match it to a specific order or a customer’s report.
6
Error text
Below the badges, in a highlighted box, you’ll find the full description of what happened — the most important part of the entry. If the description is long, you can scroll the box. This is where to look for a hint about what to fix.
Payment error stages
When an entry falls under the Payment category, the second badge tells you which stage the problem happened at. This helps you understand the error more quickly:Initiation
Something failed right at the start — when trying to begin a payment. In practice this means the customer may not have been redirected to pay at all.
IPN / Notification
A problem receiving confirmation of payment from the provider. This notification tells the shop “the customer has paid” — when it fails, the order may not be marked as paid.
Refund
An error while trying to refund money to the customer.
Filtering the list
When there are many errors, use the Filtering panel at the top to quickly find the ones you care about. You have three dropdown lists at your disposal:Category
Show only errors from a chosen area — e.g. just payments, just orders, or just notifications (Webhook).
Payment error type
Narrow payments down to a specific stage: Initiation, IPN / Notification, or Refund.
Payment gateway
Show errors reported by a chosen payment provider. The list suggests the providers you have configured in your shop.
You can combine filters. For example, choose Category: Payment and Gateway: your provider to see only problems with one payment method. Every filter change refreshes the list below right away.
When the list is empty
If there’s nothing on the list, you’ll see a “No errors” message noting that no problems were recorded for the selected filters. That’s good news — either your shop is running flawlessly, or nothing simply matches the filters currently set.If you’re expecting some errors but see “No errors”, check the filters first. You may have narrowed the list down, for example, to a single gateway or a single payment stage. Set everything to “All…” to see the full log.
Common situations
The customer paid but didn't get their item
Check the Order and Payment categories. For payments, pay attention to the IPN / Notification stage — that’s the one that confirms payment. The error text usually tells you whether the problem was delivering the item or receiving the payment confirmation.
No notifications on Discord
Filter by the Webhook category. If entries appear here, it means the messages aren’t getting through — check your Discord connection settings.
Payments don't start at all
Choose Payment error type: Initiation and the relevant Payment gateway to see why customers can’t get to the payment step.
The AI Assistant isn't responding
Look in the AI Assistant category — you’ll find the reason why help in the panel isn’t working at the moment.
Frequently asked questions
What does the "Webhook" badge mean?
What does the "Webhook" badge mean?
It’s the category for notifications sent to the outside — most often messages to your Discord server (e.g. an alert about a new order). If you see entries here, it means one of those notifications wasn’t delivered. Check your Discord connection settings.
I see a numeric code next to an error — what do I do with it?
I see a numeric code next to an error — what do I do with it?
It’s a response code from a partner (e.g. a payment provider). On its own it doesn’t require any action — it’s best to copy it together with the error text and pass it to support. With it, we can determine more quickly which side the problem was on.
Will an entry disappear on its own once the problem is fixed?
Will an entry disappear on its own once the problem is fixed?
No. The log is a history of events — entries stay, even when the problem no longer occurs. The newest errors are always at the top, so if no new entries with the same reason appear after a fix, that’s a sign everything is working.
Why do almost all errors have the "Payment" category?
Why do almost all errors have the "Payment" category?
For two reasons: payments are the most common source of problems, and on top of that, older entries recorded before categories were introduced are treated as payments. Use the category filter to check.
Who on my team can see this tab?
Who on my team can see this tab?
The Errors tab is mainly about payments, so it’s visible to people with access to that area of the shop. If a colleague doesn’t have it in their menu, it means you haven’t given them the right permissions.