7 min read

A tap, an accepted entry and a settled result are different events
A button press records what you tried to do. It does not, by itself, establish whether a Crash entry was accepted or which round received it. Acceptance concerns the entry; settlement concerns its later result. When the screen appears stuck between those stages, first identify the event you are asking about. “Was my entry accepted?” and “What did my accepted entry return?” require different records. A public multiplier history cannot answer both questions on its own.
This guide uses submitted, accepted, pending, rejected and settled as reading categories, not a promise that your app displays those exact labels. A pending message may describe a request awaiting confirmation or an accepted entry awaiting its result. The surrounding text determines which. Master Crash’s actual wording and processing rules must be checked in the game. If only an unexplained spinner appears, record that observation without inventing an acceptance status or assuming that the stake is safe to submit again.
Match the game, round and entry before interpreting the message
Open the personal entry or bet history available in the game or account, then look for the relevant time and amount. Record the game title, provider if shown, currency or unit, round reference and entry reference. These fields serve different purposes: several entries can belong to one round, while a similar amount can appear in many rounds. Use our round-history guide to separate the shared round outcome from the record belonging to your own entry.
Stake’s official casino-help page, for example, explains how its users open a casino bet record and copy its Bet ID for support. That supports the value of a specific reference; it does not make Stake’s menu path universal. An ID is useful for locating a record, but its presence alone should not replace reading the status attached to it. If no matching entry appears, note the filters and time range checked. A missing row is an observation, not automatic proof of rejection.
Conceptual reading tree, not a product interface. After a submitted request, check whether a matching entry was accepted. For a rejected request, preserve the reason and balance record. For an accepted entry, check its settlement record. A pending label can concern either confirmation or settlement; its full message is needed.
Pending and rejected need different follow-up questions
For an unclear or pending submission, ask whether the original request created an accepted entry, whether it belongs to the current or another round, and where its final status will appear. Avoid a second submission while that remains unresolved. The second tap could be a fresh request; there is no basis for assuming that every product treats it as a harmless retry. If an automated sequence is involved, use the documented control to stop future submissions and check any entries already accepted.
For an explicitly rejected request, preserve its exact reason. A message about an invalid amount calls for checking the field and the documented limits; a message about a closed entry window concerns timing. These are examples of how to read a stated reason, not diagnoses for your account. Do not raise the stake, change accounts or send several requests to test a guess. Confirm that any related balance movement is explained before deciding whether a later, separate entry is appropriate.
Swipe across to see all columns.
| Reading category | What remains to establish | Useful next record |
|---|---|---|
| Submitted / unclear | Whether an entry was accepted | Matching request or entry reference |
| Accepted / unresolved | The entry’s final settlement | Entry ID, round ID and result |
| Pending | Whether the label concerns acceptance or settlement | Full message and surrounding fields |
| Rejected | Reason and any related balance adjustment | Rejection message and account record |
| Settled | Return, stake and any separate adjustment | Completed personal entry record |
A balance movement does not explain the entry by itself
Consider an invented account showing 100 units before a 10-unit request. It later shows 90 while the request status remains unclear. That observation alone cannot distinguish an accepted stake, a temporary reservation or another adjustment; use the actual record and the operator’s definition. Do not label the missing 10 units a settled loss or promise that they will be refunded. A screenshot of the balance helps establish what appeared, but it needs the time and related reference to be useful.
If the completed record instead confirms a 10-unit accepted entry and a 15-unit total return, its net result is +5. With no other activity, the example account ends at 105: 100 − 10 + 15. If a different record explicitly shows rejection and a 10-unit reversal of a prior deduction, it would restore 100 under the same assumptions. These are separate hypothetical records, not possible payments to add together. Keep entry settlements, balance reversals and bank withdrawals in separate lines.
Send a short timeline with the disputed entry reference
A useful report states what you requested, what the screen displayed and what the account record currently shows. For example: “At 14:06 IST, I submitted 10 units. The panel showed Pending. At 14:08 IST, entry E-208 still had no final result in my history.” These identifiers and times are fictional. Replace them with your own observations and include the date. An exact status message is more helpful than a conclusion such as “the game took my balance.”
Attach the relevant entry ID, round ID if available, device and app or browser details, and a cropped screenshot showing the issue. Ask the account operator to confirm acceptance and final settlement for that reference. Our support-request checklist explains how to organise the evidence. Use the official support route and omit passwords, one-time codes, full payment credentials and unrelated personal information. No specific response time, refund or result can be promised from the screenshot alone.
Close the question with a record, not another test bet
The issue is clearer when one reference has a stated outcome: accepted and settled, rejected with its balance treatment explained, or still under review by the account operator. Record the outcome against the original request rather than replacing the first screenshot with a later balance. If support provides an adjustment, keep its reference separate from the game return so that the total is not counted twice. A changed balance without an explanation still leaves the original acceptance question open. If the game entry is settled but an account transfer is unclear, check cash out and withdrawal records separately instead of reopening the round result.
This article concerns entry status, not a universal network repair. If the app also disconnected or the display froze, the connection-problems guide covers what to preserve before trying device-level troubleshooting. Reinstalling an app or changing the network does not by itself establish what a previous request became. For Master Crash, use the actual game’s record and its operator’s reply. Public results, another player’s outcome and an unrelated withdrawal screen do not substitute for your entry’s final status.
Sources and scope
- Stake Help — opening a casino bet record and copying its ID for support
- Master Crash — public round history and personal entry records
- Master Crash — preparing an evidence-based support request
Product-specific controls remain subject to the installed app. Illustrations are explanatory and do not represent measured game results or genuine app screenshots.
How we edit and correct these guides
Quick questions
Does pending mean the bet was accepted?
Not from that word alone. The message may refer to confirmation of a request or settlement of an accepted entry. Read the full message and match its reference with the personal record.
Should I tap the bet button again if nothing changes?
Avoid resubmitting while the first request’s status is unclear. A second action may create a separate request. Check the original reference or ask official support to clarify it.
Will a rejected request always refund immediately?
No universal timing or refund rule is established here. Check whether there was a deduction, reservation or adjustment and what the account operator records for that request.




