Total YooKassa revenue, refunds and receipts right in chat

The agent calls the YooKassa API version v3 and reads everything that belongs to accepting payments: the payments themselves and their statuses, refunds, fiscal receipts and payment methods. Its first request goes to /me and confirms whose shop is connected — so the summary does not turn out to be about a neighbouring shopId. After that it totals revenue for a period, cancellations and refunds, breaks down a single payment by date, amount or status and sends a summary on a schedule.

A refund in YooKassa is a separate object linked to a payment, not an edit of the payment itself. So the agent counts revenue as the payments of the period minus the refunds tied to them, and separately flags the refunds that arrived later than the original charge: otherwise the month closes prettier than it really is. And an accepted payment is not yet money on the current account: it reaches the account as a payout, and that is visible in the banking connector.

On this key pair the agent works read-only: it counts, matches and explains — ties refunds back to the original payments, shows which payment methods generate the most of them, and finds the payment the accounting department is asking about. Payouts are out of reach over the API: YooKassa Payouts is a separate product with its own agent_id and key, and the agent does not pretend it can dispose of the shop's money.

Access is a shopId and secret key pair: it is attached to every request and is bound to one shop only, so a summary is always about that shop and never about a neighbouring one. Webhook subscriptions cannot be set with this pair — notifications are configured in the YooKassa account — so the agent fetches data itself, on request and on a schedule, paging through the payment list with a cursor. If there is no data for the period, it says so directly instead of showing an empty table.