Skip to main content

Balances and restrictions

The Balances and restrictions tab presents the user's financial state without mixing funds that have different purposes.

Payment, bonus, referral, and marketplace data for the player

Cabinet balance​

Cards show available, bonus, and locked amounts together with cumulative totals. A manual adjustment targets a selected server and balance kind. Operation, amount, and reason are separate fields, which keeps debits distinct from credits.

Balance kind, operation, amount, expiry, and required reason

Debt​

The Debt column shows the outstanding amount after a spent top-up or payment-linked reward is returned. It is separate from available funds and bonuses. A project-wide balance applies to all project servers; for separate balances, check the relevant server.

The player has 1,500 units of debt and no available main balance.

Purchases and withdrawals are unavailable while the restriction applies. Main credits to the balance with debt, including manual credits, reduce debt first. Bonus credits do not repay debt. Setting an available balance is not a debt write-off.

The player sees a warning and can top up their balance. After an adjustment, reload the page and check both available funds and debt.

Referral balance​

Referral funds use a separate adjustment form. Compare the value with referral accruals and confirm that the operation has not already been processed.

If a reward linked to a returned payment has already been spent, its debt appears in Referral balances. Purchases remain restricted even when the ordinary balance has no debt. Topping up the ordinary balance does not repay referral debt: check which row contains the outstanding amount.

Referral debt is 1,500 and ordinary balance debt is 0; purchases remain restricted.
A separate operation for the selected player's referral funds

Marketplace wallets and restrictions​

The lower section shows marketplace wallets, available and reserved amounts, and active or completed restrictions. Open the linked record when a full operational history is required.

Before a manual change:

  1. Review recent payments, bonus-code redemptions, and activity.
  2. Select the correct project and game server.
  3. Enter a clear operational reason.
  4. Reload the tab after saving and verify the resulting value.
warning

Do not repeat an adjustment before checking the first result. Payment refunds, balance adjustments, and marketplace-wallet changes are separate operations.