Orion Stars Backend Tutorial for New Operators

Your first week as an Orion Stars backend operator will involve a steep but manageable learning curve. The backend portal is packed with tools, and the stakes are real—you are processing transactions involving actual money. This guide walks you through every step of your early operations, from first login through running your first shift report, and flags the mistakes new operators make most often.

What Your First Day Looks Like

Before you log in for the first time, make sure you have three things ready: the portal URL bookmarked in your browser, your Account Name and Password from your distributor, and a clear understanding of your credit balance. Your distributor will have transferred an initial credit allocation to your account after setup. The size of that allocation is the credit budget you have to work with on day one.

Keep a simple ledger—a notepad or spreadsheet—for your first few shifts. Record every credit in (recharge to player) and every credit out (redemption from player) alongside the corresponding cash collected or paid. This manual reconciliation habit will protect you against accounting errors while you are getting used to the platform's reports.

First Login and Immediate Password Change

Log into the portal at the official URL your distributor provided. Your distributor will have given you an initial password—this is a temporary credential. The first thing you should do after a successful login is navigate to your account security settings and change it to a private password that only you know.

Choose a password that is at least 10 characters and combines uppercase letters, lowercase letters, numbers, and a symbol. Write it down somewhere secure—not on a sticky note near your computer. Never share this password with employees. If you need employees to access the backend, you will create separate cashier accounts for them (covered later in this guide).

A Tour of Your Dashboard

After logging in, your dashboard displays an overview of your store's current state. The exact layout varies slightly by platform version, but all dashboards share a common structure. Take a few minutes to orient yourself before making any transactions:

• Credit balance: Displayed prominently, usually at the top. This is the total credits available in your store account—the "inventory" you can distribute to players.
• Player list or search: A searchable list of all player accounts under your store. New stores start with no players until you create them.
• Transaction panel: The tools for recharging (adding credits to a player) and redeeming (removing credits from a player).
• Reports: Usually in a dedicated sidebar or top navigation section. This is where shift reports and daily summaries are generated.
• Settings: Account password, cashier management, and limit configuration.

Click through each section without making any changes—just familiarize yourself with where everything is. You do not want your first transaction to involve a hunt for the right button while a player is waiting.

Creating Your First Player Account

Players cannot register themselves. You create every player account in your store. Here is how:

1. Navigate to the Player Management section of your dashboard.
2. Click "Create Player" or "Add Account" (the label varies by version).
3. Enter a username for the player. Many operators use a consistent naming convention (a short code plus a number, for example) to keep the player list organized.
4. Enter an initial password for the player account. The player will use this to log into the game app.
5. Confirm the account creation. The new account will appear immediately in your player list.
6. Provide the player with their username and password through your preferred communication channel (in person is most secure).

A few important notes on player account creation: The username must be unique within the platform—if you try to create a username that already exists elsewhere, the system will reject it. Keep a private record of the usernames you create. If a player forgets their username, you can look it up in your player list, but you cannot recover a password you did not record—you will need to reset it instead.

Your First Credit Recharge: Adding Credits to a Player

A recharge is when a player pays you cash (or another agreed-upon payment method) and you add the corresponding credits to their account. This is the most frequent transaction you will perform. Here is the process:

1. Collect payment from the player first. Do not add credits until you have received and confirmed the payment. This sequence is non-negotiable—credits given before payment are credits you may never recover.
2. Search for the player's account in your backend. Use their username to locate them.
3. Verify the username carefully before proceeding. A single-character typo can send credits to a completely different player. If you are unsure, ask the player to confirm their username.
4. Enter the recharge amount (in credits, typically equivalent to the cash amount collected).
5. Confirm the transaction. The player's balance will update immediately in the game app.
6. Note the transaction in your ledger: date, time, player ID, amount credited, cash received.

The backend maintains a full log of all transactions, but your own manual record is a useful cross-reference and provides a backup if you ever need to dispute a transaction detail.

Redemptions: Paying Out Winnings

A redemption is the reverse of a recharge—a player requests to cash out their credits, and you pay them in real currency. The process in the backend mirrors a recharge in structure:

1. The player requests a redemption and tells you their username and the amount they want to cash out.
2. Search for the player's account and verify their current credit balance. Do not pay out more than their current balance shows.
3. Enter the redemption amount and confirm the transaction. The credits are removed from the player's account immediately.
4. Pay the player the agreed-upon cash equivalent.
5. Note the transaction in your ledger: date, time, player ID, amount redeemed, cash paid out.

A common mistake new operators make is processing a redemption before verifying the player's balance. If a player claims to have more credits than the system shows, do not pay the discrepancy—pay only what the system confirms. Discrepancies in the player's favor are almost always fraudulent.

Running Your End-of-Shift Report

The shift report is one of the backend's most important tools. At the end of each operating period—whether that is a 4-hour cashier shift or a full business day—you generate a shift report that summarizes all activity during that period. Here is how to use it effectively:

1. Navigate to the Reports section of the backend.
2. Select "Shift Report" or "Daily Report" from the options.
3. Set the time range to cover your operating period.
4. Generate the report. It will show total credits added (recharges), total credits removed (redemptions), and the net credit movement.
5. Compare the net credit movement to your physical cash position. If you added more credits than you removed, you should have collected more cash than you paid out—and the difference should be sitting in your cash drawer.

If the numbers do not reconcile, investigate before closing the shift. A small discrepancy is usually a recording error. A large discrepancy—particularly if a cashier was operating—warrants a transaction-by-transaction review. The backend's detailed transaction log (accessible in the reports section) allows you to review every individual credit movement during the shift period.

Common Mistakes New Operators Make

After working with many new store operators, these are the errors that appear most consistently during the first few weeks:

• Processing a recharge without first collecting payment. If a player disappears after receiving credits but before paying, those credits are a loss. Collect first, always.
• Failing to verify player usernames before transactions. Sending credits to the wrong player means chasing down a refund. Always confirm the username with the player before confirming the transaction.
• Sharing backend login credentials with cashiers. Cashiers should have their own sub-accounts with appropriate limits. Sharing your main account credentials removes your ability to hold cashiers accountable for specific transactions.
• Not running shift reports. Without shift reports, you cannot verify that your cash position matches your credit movements. This is how small discrepancies become large undetected losses.
• Keeping excessive credits in a player's account. If a player has accumulated a large balance and then requests redemption, you need the cash to pay them. Encourage regular partial redemptions rather than allowing balances to accumulate indefinitely.
• Not bookmarking the backend URL. Navigating to the backend via Google each time increases the risk of landing on a phishing site. Bookmark the URL after your first successful login and use only that bookmark.

Setting Up a Cashier Account

If you plan to employ someone to handle credit processing on your behalf, set them up with a cashier sub-account rather than sharing your main login. Here is the process:

1. Navigate to Account Settings or the sub-account management section of your dashboard.
2. Select "Create Cashier" or "Add Sub-Account."
3. Enter a username and initial password for the cashier.
4. Set credit limits: the maximum amount the cashier can recharge or redeem per transaction, and optionally a daily maximum. Start with conservative limits and adjust based on the volume your cashier handles.
5. Provide the cashier with their credentials and instruct them to change their password upon first login.

Monitor cashier activity through the shift reports. If a cashier's reported credits do not reconcile with the cash they hand you at the end of their shift, investigate immediately. The transaction log will show every individual transaction the cashier processed during their shift.

Your First Week Goals

By the end of your first week of operations, you should be comfortable with the following:

• Logging in securely from your bookmarked URL without hesitation
• Creating a new player account in under two minutes
• Processing a recharge and a redemption correctly and verifying the transaction in the log
• Running a shift report and reconciling it with your physical cash position
• Knowing how to contact your distributor if something looks wrong

The backend becomes intuitive quickly once you have run through these operations several times. Most operators feel fully comfortable within two to three weeks of daily use. If at any point you encounter something that does not make sense—an unexpected balance, a transaction that does not appear in the log, a screen you do not recognize—stop and contact your distributor before proceeding. It is always better to pause an operation than to compound an error.