Skip to content

Finance ​

Finance shows the money and the gems that move through the whole platform: Stripe payments from every community, and the gems players spend. Every platform role can read it and export it; only the operator can refund a payment.

Two books ​

The page has two tabs that never mix amounts.

BookContent
Real moneyReal money paid through Stripe, across every community: gem packs, subscriptions, upgrades. Amounts are never added across currencies.
GemsGems spent in community stores (Gem spends) and gems taken back after a refund or dispute (Refund clawbacks). Gems only, no money.

Real money: statistics ​

A period switch sets the window: 7 days, 30 days, 90 days or 1 year. With several currencies, a currency switch appears. The totals:

NumberMeaning
RevenueMoney collected in the period.
After refundsRevenue minus refunds.
RefundedThe refund rate and amount; the rate turns amber at 5% or more.
Per paying playerAverage revenue per paying player, and how many players paid.
PaymentsNumber of payments.
Subscriptions per monthEstimated monthly value of subscriptions.

Charts: Revenue per day, Revenue per month, Gem packs and subscriptions (the split by payment type) and By community (top communities by revenue).

The payments list ​

Both books have a searchable list below the totals.

ControlWhat it does
SearchSteam ID or payment reference (Real money); Steam ID (Gems).
CommunityOne community or all.
TypeReal money: Gem packs, Subscriptions, Upgrades, Legacy. Gems: Gem spends, Refund clawbacks.
StatusSucceeded, Partly refunded, Refunded, Disputed, Failed, Pending (gems: succeeded, refunded, disputed, failed). A won dispute shows Dispute won.
From / ToDate range.
Export CSVDownloads the list; with filters set it reads Export filtered CSV.

Columns: Date, Player (opens the player), Community, Type (with the payment reference), Amount (with "refunded" amounts) and Status. Pages of 25.

Refund a payment ​

Operator only. A Refund button appears on payments that are refundable: Stripe payments of type gem pack, subscription, upgrade or legacy, with status Succeeded or Partly refunded and an amount left.

  1. Click Refund. The dialog shows the player, community, amount charged, amount already refunded and Can still refund.
  2. Enter Amount to refund (a partial refund is allowed; Everything left fills the maximum).
  3. Write a Reason (at least 3 characters, up to 300; it is kept in the audit log).
  4. Tick "I understand a refund cannot be undone" and click Refund.

What happens:

  • The money goes back to the player's card through Stripe, on the Stripe account that took the payment.
  • The gems of the payment are taken back from the player's balance, only what is still there. This appears as a Refund clawback in the Gems book.
  • Refunding a subscription payment in full ends the subscription at once.
  • A retry of the same click never refunds twice.

Rules ​

  • Refunds and disputes are applied once: Stripe notifications are de-duplicated, so changing refund logic never re-applies it to old events.
  • Platform billing (community plans) is currently off, so subscription revenue is currently small; gem packs and kits are the main flows.

Troubleshooting ​

ProblemFix
No Refund buttonYou are not the operator, or the payment is not refundable (already fully refunded, failed, or not a Stripe payment).
"No Stripe payment found for this entry"The payment has no Stripe charge to refund.
A figure is missing from the totalsIt is in another currency: use the currency switch.