Gift Codes
Gift Codes are a core cabinet feature and do not require a separate add-on. The buyer pays from their balance, and the recipient redeems the code once through Bonus Codes.
Administrator panel
Open Users -> Gift Codes. The overview lists every game server, program status, and the number of available packages.
Server settings
Click Settings for a server. The Enabled switch controls new purchases on that server. When disabled, the player menu entry disappears and new purchases are unavailable. A purchase already started completes under its saved terms or refunds the original charge.
Each package has:
- a localized name and description;
- the issued code denomination;
- the price charged to the buyer;
- Popular and Available flags;
- its position in the package list.
You can also allow a custom denomination. Set its minimum, maximum, and price rate. For example, a rate of 0.1 makes a code with a denomination of 500 cost 50.
Enter a package name in at least one language. Unused translations can stay empty; descriptions are optional.
Changes take effect after saving. There is no separate publish or upload step. Changing the price, package or balance mode does not alter a purchase already started.
Statistics
Open Users -> Gift Codes -> Statistics. Paid purchases, paid amounts, refunds and issued codes are shown separately. A code's face value is not its price: buying a code worth 250 for 25 adds 25 to the paid amount and 250 to the issued face value.
Report filters
| Field | Selection |
|---|---|
| Project | All available projects or one project. |
| Game server | All servers of the selected project or one server. |
| Period | A preset range or custom dates. |
| From / Through (UTC) | Start and end dates; the end date is included. |
| Grouping | Automatic, daily, weekly, monthly or yearly. |
| Balance unit | A project's balance unit. Automatic selection uses the first available unit with data. |
| Packages per page | 10, 25, 50 or 100 distribution rows. |
Use the refresh button to apply filters. Reset restores the initial selection. Compare different balance units separately; their display names follow project settings.
Payments and issuance
Paid amount is the amount charged for purchases, Returned amount is the amount refunded during the selected period, and After refunds is their difference. The difference can be negative when a refund relates to an earlier purchase.
The next section shows buyers, average paid amount, issued codes and their total face value. The table separates main and bonus funds. A free code increases the issued count and face value, but not the paid amount.
Packages and custom amounts
Each row shows the package, project, server, paid purchases, paid and returned amounts, and issued codes. Custom denominations share a separate row. Expand Details to see buyers, original prices, average payment, free issuance and the fund allocation.
Previous and next pages become available for larger package lists. Totals and the chart cover the whole selected period, not just the visible package page. Refresh the report if the page has expired.
Calendar
The chart shows payments and refunds across the selected range. Expand Values by period for exact amounts, payment counts, issued codes and face value. Periods without activity remain visible with zeros; the current period contains data received so far. Choose months or years for a longer range.
If there are no purchases or refunds, change the period or server. An updating notice means recent purchases may appear shortly. Retry refresh if the report could not load; select one project or a coarser grouping for a report that is too large.
Player cabinet
When enabled, Gift Codes displays packages, the custom-denomination option, current balance, and purchase history. Package text follows the cabinet language.
After payment, the code appears in the result dialog and in purchase history. The copy button copies the entire code. The available balance includes both main and bonus funds.
If the connection drops, check purchase history. If no result appears yet, retry the original purchase without changing the package. Pending issuance continues after closing the page. If issuance fails, the main and bonus funds charged are returned to the balance.
The recipient enters the code through Bonus Code. After successful redemption, the purchase history state changes from Active to Used.
When the administrator disables the program, its menu entry is hidden. A direct link shows the unavailable state and cannot start a purchase.
Before launch, test the real flow with two users: purchase, one balance charge, code transfer, one recipient credit, and the updated history state.