A format-first guide to the 4Tuna lobby, live tables, account offers, cashier workflows, and mobile play.
| Area | Practical distinction |
|---|---|
| Before deposit | Method, currency, amount, destination, instructions |
| After submission | Transaction identifier and exact status |
| Withdrawal | Account record plus any verification prompt |
| Bonus balance | Tracked separately from cash |
| Support details | Identifier, method, amount, time, destination, status |
Starting a deposit correctly
Start inside the cashier and select the route presented for the account. Review the method, currency, amount, destination, and any displayed instruction before confirmation. Payment intent is transactional: choose a route, read its instructions, confirm the amount and destination, submit once, and retain the resulting record. Game-category browsing is secondary to the cashier state.
If an external service opens, complete only the intended flow and return to the cashier. Check for an existing request or account credit before submitting again. Available methods, limits, currencies, fees, verification steps, and processing messages can vary by account and selected route. None should be supplied from a generic game overview.
Creating and tracking a withdrawal
A withdrawal is not complete merely because a request button was pressed. The account should create a durable record with an identifier and a readable status. Deposits should be initiated from the cashier so the selected method, amount, and destination are presented in one flow. A successful external handoff is not the same as a confirmed account credit.
Follow status changes in that record and respond to any designated verification prompt. Do not substitute guesses about processing time, limits, or fees. Withdrawals need a persistent request with a status that can be checked later. Pending, approved, completed, cancelled, or declined wording should be read exactly as shown rather than inferred from a balance change.
Payment records versus game rounds
Game history records rounds; cashier history records transfers. Slots, Megaways, jackpots, crash rounds, tables, and video poker do not become payment mechanisms. Slots, Megaways, jackpots, Dream Drop, Crash Games, Table & Cards, and Video Poker produce rounds with different mechanics, but payment records should remain outside those mechanics. A deposit does not alter a game's rules.
New Games and Top Games are catalogue shelves with no inherent cashier privilege. A game's lobby position should never be used to infer withdrawal treatment. New Games and Top Games likewise have no special cashier meaning. Their role is catalogue discovery, and placement on either shelf should not imply a deposit condition or withdrawal privilege.
Bonuses and balance labels
Cash and promotional credit should not collapse into one unexplained number. If an offer is active, its conditions and progress belong in the bonus area. Where a promotion is used, cash and promotional balances must remain distinguishable. The promotion terms may affect account availability, but they do not turn a game category into a payment method.
The cashier should still identify what amount can be requested and what status follows submission. Club levels or Wheel interactions are not transaction confirmations. Club progression and Club Wheels are account features, not proof that a transaction has settled. A level change or wheel interaction should never replace the cashier's transaction identifier and status.
Verification and external handoffs
Use the verification route shown in the account and match documents to the stated request. Sensitive information should not be sent through unrelated game controls. Verification requests should be followed through the account's designated route. Documents and personal details should not be sent through an unrelated game screen or inferred from unofficial instructions.
After a handoff to a bank, card page, wallet, or another service, return to the existing cashier record. A duplicate request can make the history harder to interpret. When a bank, card, wallet, or other service opens externally, returning to the cashier and checking the existing request is safer than immediately creating a duplicate submission.
Building a useful support record
For a payment question, retain the transaction identifier, method, amount, time, destination where relevant, and exact status text. A useful support report includes the transaction identifier, method, amount, time, destination where appropriate, and exact current status. Game titles and round references belong only when the issue concerns game history.
Add a game title, provider, round time, and round reference only when the issue concerns a game result. Separating the two records helps support investigate the correct system. The clean separation is deliberate: the lobby explains formats, the cashier records money movement, the promotion area explains conditional balances, and the account history links actions to durable records.
Common questions
Payments questions
Which payment methods are available?
Use the cashier methods shown for the specific account; this page does not invent a method list.
Where are payment limits and fees checked?
Read the instructions displayed after selecting the relevant cashier route.
What should be confirmed before a deposit?
Confirm the selected method, currency, amount, destination, and any route-specific instructions.
How is a withdrawal tracked?
Use the persistent account record, transaction identifier, and exact status shown after submission.
Should a payment be repeated after an external handoff?
First return to the cashier and check whether a request or credit already exists.
Do game categories change payment rules?
No general link should be assumed. Game formats and cashier workflows are separate.
Is a club level proof that a deposit settled?
No. Club progression is not a substitute for a cashier transaction record.
What information helps with a payment query?
Provide the identifier, method, amount, time, destination where relevant, and current status.