YooKassa payments report for your client

YooKassa payments report for businesses and agencies

Online stores, schools and service companies in Russia use YooKassa to accept payment for goods, courses, bookings and subscriptions. Its data answers the owner’s main question: how much did customers actually pay? Those numbers usually stay in the merchant dashboard while the marketing report is assembled from ad accounts and Yandex Metrica. Reportkey joins the two halves by reading payments and refunds through the YooKassa API and placing them in the same document as ad spend, delivered on schedule as a link or PDF.

Which YooKassa payment statuses count as money

A YooKassa payment has four states. It stays pending until the buyer completes checkout. With two-stage payments the money is first held on the card in the waiting_for_capture status, and the store decides whether to capture or release it. Money is received only in the succeeded status, while canceled means the payment failed or was voided.

The receipts block uses successful payments only and dates them by capture time (captured_at) rather than creation time. For stores with two-stage payments this matters: an order placed on Friday and captured on Monday lands in the week when the money actually became available.

Amount after YooKassa fees

The most common reconciliation question is why the report and the bank statement differ. Each payment carries amount, the buyer’s payment, and income_amount, the sum after the YooKassa fee. The report shows:

• Successful payment total — the turnover the buyer sees on the receipt.
• Net of fees — what the store keeps; the gap between the two lines is the period’s fee.
• Average payment — turnover divided by the number of successful payments.
• Change versus the previous period next to every number.

YooKassa refunds and net receipts

Refunds live in a separate API list and reference the original payment. They can be partial and can arrive a month after the purchase, so the report counts them in the period when they were issued. The block shows refund count, refund amount and net receipts, meaning successful payments minus returned money. For online schools with a money-back guarantee this is often the most useful line.

Payment methods: card, SBP, YooMoney

The payment_method.type field splits turnover by method: bank card, SBP fast payments, YooMoney wallet, SberPay, T-Pay and any other enabled method. The table lists payments, amount and share for each one, which helps decide whether SBP deserves a more prominent spot on the checkout page.

Cancelled payments and their reasons

A cancelled YooKassa payment stores a reason in cancellation_details: issuer decline, insufficient funds, expired waiting time or cancellation by the store. The block calculates the cancellation share and groups it by reason and payment method. A sudden jump for one method is a reason to check the checkout before the client notices lower revenue.

YooKassa API data caveats

• These are payments from your client’s customers, not Reportkey’s own billing.
• A payment is a money result, not an ad conversion; the traffic channel is unknown unless the site passes an order number or tags in metadata.
• Payments flagged as test are dropped during the build.
• Payment and refund lists cover the last three years.

YooKassa next to ads and web analytics

Money reads best next to what drove it. Add Yandex Direct spend and campaigns, VK Ads campaigns and website visits and goals in Yandex Metrica. To link a payment to its channel, use Roistat end-to-end analytics; if the project also takes payments through a second provider, add CloudPayments payments and declines. Branding, scheduled delivery and AI insights are available, though not on every plan. See a finished example in the in-house team demo report, browse other stores and payment providers in the ecommerce integrations section, and check trial terms on pricing.