Log requests for Merchant and Autopayouts
The “For Merchant” and “For Autopayouts” sections display integration logs showing how the system interacts with external services. Both pages share the same structure and logic, differing only in context: Merchant logs — for operations on the merchant side (wallet generation, transaction creation/processing, payment integrations). Autopayouts logs — for automatic payouts executed through integrated providers.
The main purpose of these sections is to provide detailed error explanations, reduce support inquiries, and ensure transparent tracking of integration requests.
1. When a log is created
A log is generated automatically when:
A request to an external service returns an error.
Wallet generation fails.
An auto-payout is not executed (error, timeout, invalid details, etc.).
A provider returns an incorrect or unexpected response.
A link to the corresponding log appears directly inside the related order in the admin panel, connecting the log to the specific operation.
2. Column descriptions
Both sections contain the same set of fields:
Request ID
External identifier of the order associated with the log. Allows administrators to quickly understand which request the log refers to.
Status
Current status of the integration request. Possible values:
success — provider returned a successful response
error — an error occurred
Provider
The name of the service or payment module used for the request (payment system, crypto provider, auto-payout service).
Response
Raw response data returned by the external service. May include:
error code
error message
technical payload
HTTP status
API-level metadata
Information
Displays a human-readable error explanation if available.
Logic:
If the provider has documentation and the system can interpret the error code, the field shows a readable message (e.g., “Insufficient balance”).
If the provider does not provide structured codes, the field shows the raw English-language response.
This field is essential for administrators or support agents to understand the issue quickly.
Creation Date
The timestamp when the error or event was logged. Displayed in the format: DD.MM.YYYY, HH:MM:SS
3. Purpose and benefits
The logs provide the ability to:
quickly diagnose technical issues without involving developers;
see in detail what the external service responded;
identify the cause of failed auto-payouts or wallet generation;
reduce support requests such as “check why the payout failed”;
maintain a full chronological history of integration errors.
4. Usage in daily operations
An administrator can:
open the log from the order and immediately see the cause of the problem;
resend the payout/request if supported by the system logic;
give the client an accurate explanation based on the interpreted error;
forward the log to developers if the provider returned a non-standard response.
Якщо хочеш, можу зробити це у форматі Markdown-документа або адаптувати під ваш внутрішній стиль документації.
Last updated