Did your Dexsport mobile bet go through?

Start with the record, not another submission

On a phone, several things may happen close together: you choose an outcome, review a stake, move to another app and return to the browser. That sequence can make a display problem look like a failed bet. Repeating the entire sequence immediately risks creating a second request instead of clarifying the first.

Dexsport’s official help page directs users to “My Bets” through their profile or the sports section. Look there using the same account as the original attempt. Check both unsettled and settled records. If your view provides date or status filters, make sure they are not hiding the relevant entry.

This site is a mobile-use guide. It cannot inspect an account, reverse a transaction or confirm acceptance on Dexsport’s behalf. The steps below help you gather the right evidence without making an additional wager.

Four things that can look similar on a small screen

A transaction identifier and a bet identifier may refer to different records. Keep their labels when copying them. Sending an unexplained string makes it harder for support to know whether your question concerns funding, submission or settlement.

Match the ticket to your original selection

Finding a recent entry is useful, but it is not enough if you attempted several selections. Open the record and compare six details: event, market, chosen outcome, stake, accepted odds and time. Also check the currency or asset unit. A number such as “10” has no monetary meaning until you know its unit.

Suppose you intended a fictional Team North win in the first half, using 5 units at decimal odds of 2.20. An entry for the same team in the full-match market is a different selection. A 5-unit ticket at 2.10 also deserves a closer look at the accepted details and any price-change message.

Use the ticket’s accepted price when reviewing a recorded bet. The current match page may show another price because the market has moved. A later price displayed on the home screen is not evidence that the original ticket changed.

Save a screenshot that includes the market and period, not just the potential payout. Crop unrelated personal details if you later share it with support. Do not post account information or transaction histories publicly to ask strangers to diagnose the issue.

If the mobile page froze or you changed apps

1. Return to the original tab. Avoid creating several parallel sessions while the first outcome is unclear.
2. Record what is currently visible. Capture any exact error text and note the local time with its time zone.
3. Check connectivity. Establish whether ordinary pages load; a missing signal is different from a message refusing access.
4. Open My Bets. Look for the matching ticket before considering a fresh submission.
5. Refresh only after preserving the evidence. Then compare the refreshed record with what you saved.

Dexsport’s acceptance rules explain that a connection problem does not undo an already registered bet. Closing a tab, clearing the browser or restarting the phone is therefore not a cancellation method.

If the account itself is inaccessible, our Dexsport login guide covers the entry step. Keep access troubleshooting separate from the question of whether a particular ticket exists. A successful new login does not, by itself, answer that second question.

When the ticket appears but remains unsettled

An accepted bet waiting for its result is different from a submission that you cannot find. First check whether the full event or the relevant period has actually ended. A broadcast break, a suspended match or the completion of one leg in a combo may leave a ticket unresolved.

The official settlement help article currently says some bets may take up to 20 minutes after an event concludes and asks users to send the bet ID to support when that period is exceeded. Treat that as published guidance, not a guaranteed deadline for every interrupted event or market.

Do not use an unsettled status as a reason to place another bet or add funds. The status describes an existing record. If the result appears inconsistent, read the market’s period and the settlement rules before comparing the ticket with a scoreboard.

If there is no matching entry

Confirm that you returned through the same sign-in method and are viewing the intended account. Check the currency context and any date or status filters actually offered in your view. A recently settled ticket may no longer appear in a view restricted to open bets.

If a complete search still shows no entry, describe the uncertainty rather than deciding it must have failed. You may have a pending request, a rejected attempt or a record that support needs to locate. Preserve the error and any reference supplied by the interface.

A useful stopping point is: “No matching ticket found after checking the account and filters; support asked to verify the attempt.” There is no need to repeat the stake to make the first attempt easier to trace. If you later make a new selection, review it as a separate decision at its then-current terms.

Fix a loading problem without losing the useful details

Dexsport’s loading and login help includes restarting the platform and clearing cache or cookies. Capture the ticket or error first. Clearing site data may sign you out, so make sure you know your legitimate sign-in method before doing it.

Change one browser setting at a time. That makes it possible to tell whether a reload, an extension or stored site data was involved. Do not install an APK, profile or browser extension offered by an unsolicited “support” account to repair a missing ticket.

If the message states that access is restricted, treat it as an eligibility issue. Do not change your apparent location to get past it. The mobile access guide describes ordinary browser use without promising availability in any particular country.

A support message you can prepare in two minutes

Dexsport’s support instructions ask for a nickname and the relevant reference: a bet ID for a bet, or a transaction hash for a funding transaction. Start from the support channel linked on the official platform.

• The approximate attempt time and time zone.
• The event, market, outcome and stake unit.
• The accepted bet ID, if one exists.
• The exact status or error text.
• The phone, operating system and browser used.
• The checks already completed and their results.

For example: “At 19:42 AEST I attempted the first-half result on North–South. My browser returned from another app to a blank panel. I checked settled and unsettled bets in the same account and found ticket X with status Y. Please confirm the recorded state.” Replace the placeholders with your actual details.

Never include a password, recovery phrase, private key or one-time sign-in code. A legitimate status enquiry can identify the record without handing over control of the account or wallet.

Quick answers

Does a spinning button mean the bet failed?

No. It means the interface has not given you a clear result. Check the account record before making another request.

Can reopening the browser cancel an accepted bet?

No. A local browser action is not a cancellation instruction for an existing ticket.

Should I send the current odds to support?

Include the accepted ticket details. A current price can provide context, but it does not replace the odds recorded for the original bet.