Match one accepted ACE66 ticket to its exact status, event state and balance entry, then decide whether to wait, verify a rule or contact support.
Bet status fundamentals
Start with the accepted ticket
The accepted ACE66 ticket is the baseline for deciding whether a wager is Pending, Open, Processing or finally settled.
First check whether the wager exists in ACE66 history with a unique bet ID. A selection displayed in a bet slip before final confirmation is not necessarily an accepted transaction, and an animation or temporary balance change cannot replace the ticket.
Match the ACE66 selection, market, odds or price, stake, event and accepted timestamp. If any field differs from what was intended, preserve the record and avoid placing a duplicate wager while the first submission remains unclear.
A clear ACE66 record lets the status, event state and balance entry be reviewed against one transaction. Use the label as an audit clue rather than a promise about the final result.
Bet status meanings
Compare common status labels
| Status | Usual meaning | What to check |
|---|---|---|
| Pending | Submission, result or another step is waiting. | Confirm the ACE66 bet ID, timestamp and event state. |
| Accepted / Open | The wager exists but is not finally settled. | Match the ACE66 selection, accepted price and stake. |
| Processing | A result feed, rule or accounting entry may be under review. | Check the official result and ACE66 settlement scope. |
| Settled | The ticket reached a final or currently final accounting state. | Open the detailed ACE66 outcome rather than relying on the icon. |
| Won / Lost | The selection met or did not meet the market condition. | Verify the ACE66 line, period, result and accepted price. |
| Void / Push / Refund | A rule may return or neutralise the affected stake. | Identify the ACE66 reason and whether one leg or the whole ticket changed. |
| Rejected / Cancelled | The wager was not accepted or was removed under a stated procedure. | Check the ACE66 deduction, reversal and reason code. |
Pending and open bets
Separate Pending from Accepted or Open
A Pending ACE66 bet can mean that submission confirmation, provider acknowledgement or a settlement step has not completed. The word alone does not reveal which stage is waiting, so check whether the ticket already has an accepted price and unique ID.
An Accepted or Open ACE66 bet normally exists while the event or market remains unresolved. A full-time football selection can stay Open during the match, while a season outright can remain Open for weeks or months.
For a multiple, some ACE66 legs can show a result while the combined ticket remains Open. Read every leg because one unresolved selection can keep the whole multiple unsettled.
If Pending remains after the event ends, compare the official event status, market scope and published processing information. Record the ACE66 ticket ID and last visible update before contacting verified support.
Processing status
Check why a settlement is delayed
Processing can appear while ACE66 waits for a final data feed, applies a market rule or reviews an irregular event. Live markets may need correction after an initial scoreboard update, especially when the official source changes a goal, card, point, map or player statistic.
A delay is not proof of an error. The ACE66 market may use regulation time, extra time, a named map, a specified inning or another defined period. A scoreboard can look complete while the accepted market is still unresolved.
Postponed, suspended and abandoned events often follow event-specific resumption windows. Do not import one sport's procedure into another ACE66 ticket; check whether completed markets settle separately or affected selections become void.
When the official result is disputed, ACE66 may keep the ticket Processing until the controlling source is final. Read the timeline from acceptance to the latest update without filling missing stages with assumptions.
Settled bet results
Read Won, Lost and Settled separately
Won means the ACE66 selection satisfied the market condition after the stated settlement scope was applied. The credited amount can contain both profit and returned stake, so gross return should not be described as net profit.
Lost means the ACE66 selection did not satisfy that condition. Before disputing a loss, confirm the precise market, handicap, total, participant, period and accepted price because a correct event prediction can still refer to a different market.
Settled is an umbrella state. Open the ACE66 ticket detail to see whether the outcome is Won, Lost, Void, Push, Refund, Cash Out or another defined result; a completed icon cannot reconstruct the calculation.
A result may be corrected or resettled if the controlling data source changes. Compare the first and revised ACE66 entries, official correction time and resettlement rule before deciding that a credit is missing.
Void and cancelled bets
Distinguish Void, Push, Rejected and Cancelled
A Void ACE66 status commonly means that a stated rule removed the selection from ordinary win-or-loss settlement. A single may return its accepted stake, while a void leg in a multiple may be recalculated at neutral odds when the rules say so.
A Push can occur when a whole-number handicap or total lands exactly on the line. That is different from a win, and the ACE66 treatment can depend on whether the wager is a single, multiple or split-line market.
Rejected usually indicates that ACE66 did not accept the attempted wager at the submitted terms. A price change, closed market, limit or incomplete confirmation can be possible causes, but only the displayed message identifies the actual reason.
Cancelled can describe a bet removed before acceptance, an accepted selection later voided by rule or another feature-specific action. Never infer the ACE66 money treatment from that word alone; match the reason code to the transaction history.
Multiple and revised status
Audit every leg and adjustment
One ACE66 multiple can contain a Won leg, a Void leg and a Pending leg while the combined ticket remains Open. The final calculation should use each leg's accepted price and the stated treatment of a void or push outcome.
Some products may offer early settlement or Cash Out. If displayed and accepted, that ACE66 transaction can close the ticket at the shown amount before the event's final result; availability and mechanics must not be assumed.
Partial settlement can also appear when independent ticket components settle separately. Review every ACE66 component, stake, return and adjustment before calculating the combined net result.
If an official correction changes a result, preserve the earlier ACE66 screen and the revised entry. Evidence should show the full non-sensitive context rather than a cropped amount with no ticket reference.
RM status examples
Separate potential return from a final credit
| Illustrative ticket | Status treatment | Illustrative accounting |
|---|---|---|
| RM50 single at decimal odds 1.80 | Won under the stated terms | ACE66 example: RM90 gross return, including RM50 stake and RM40 profit. |
| RM50 single at decimal odds 1.80 | Fully Void with stake returned | ACE66 example: RM50 returned and RM0 profit; it is not a win. |
| RM100 single at decimal odds 2.20 | Won under the stated terms | ACE66 example: RM220 gross return and RM120 net profit. |
| RM100 ticket still Pending or Open | No final settlement | Do not add the potential ACE66 return to the available balance. |
Unsettled bet checklist
Check a status in a fixed order
Identify the ticket
Record the bet ID, event, market, selection, accepted price, stake and submission time.
Read the exact label
Note whether the ticket shows Pending, Accepted, Open, Processing, Settled, Won, Lost, Void, Rejected or Cancelled.
Check the event state
Confirm whether the event is scheduled, live, finished, postponed, suspended, abandoned or officially corrected.
Read the market rule
Match the settlement scope, overtime treatment, source, postponement window and void condition.
Audit the money
Compare the stake deduction, gross return, net result and any reversal in transaction history.
Support evidence
Prepare a safe status record
Keep the full context
Save the event, market, selection, price, stake, status, bet ID and relevant timestamps.
Preserve the controlling wording
Capture the market rule and event-status notice that apply to the ticket.
State one discrepancy
Explain which status or amount does not reconcile and show the calculation.
Remove sensitive details
Never disclose a password, PIN, OTP, recovery code or complete payment credential in a support request.
Use verified support
Submit the minimum evidence through the verified contact route and keep its reference.
Responsible-play boundary
A status check is not a reason to bet again
Bet status FAQ
Answer common status questions
Why is my bet still Pending?
Pending can refer to acknowledgement, an unfinished event, a delayed official result or another review step. Match the ACE66 ticket ID, event state and market rule before escalating.
Is an Open bet already accepted?
Open often means accepted but not finally settled, although wording can vary. Confirm that ACE66 history shows an accepted stake, price and unique ticket.
Does Void mean the bet won?
No. Void usually removes ordinary win-or-loss settlement under a rule. The ACE66 stake or leg treatment depends on the bet type and controlling terms.
Why can a result change after settlement?
The controlling data source can correct an event or statistic. The ACE66 resettlement rule and revised history should explain any balance adjustment.
What evidence should be sent about an unsettled bet?
Send the ACE66 bet ID, event, market, selection, accepted price, stake, status and timestamp through verified support, without passwords, OTPs or complete payment details.