After a connection drop, a bet may already be recorded even though your confirmation never appeared. A frozen screen leaves the result unknown. The account’s bet history resolves that uncertainty. Check for an accepted slip before making another submission.
Reconnect and open the account record
First, restore a stable connection and sign in through the operator’s normal app or site. Open My Bets, Bet History or the equivalent page. Use the time of the attempt and the stake to find the slip. An unsettled event belongs under Open or Running, not the settled Won and Lost filters.
Betano Nigeria says its bet statuses include Open, Won, Lost and Void or Cancelled in My Account → History → Bets. BetKing’s tutorial uses a Bet Search with outcome and date filters. Both services place accepted slips in signed-in account history, though their menu labels differ.
- Note the attempted selection and stake. Use the amount you meant to submit, not a refreshed current odd.
- Search bet history around that time. Include open or running bets.
- Open any matching slip. Record its bet ID, accepted odds and status.
- Compare wallet activity. A stake debit can support the record, but the slip is the clearer evidence.
Check what the operator accepted
If a matching bet ID exists, the operator has a record of the wager. Read the accepted odds and selections on that slip. The accepted price can differ from the pre-submit screen when odds move. The receipt gives the final selections and price used for settlement.
Two taps can produce two similar slips. Their bet IDs, timestamps and accepted stakes reveal whether the operator recorded two wagers. If both exist and one was unintended, send both IDs to support and ask how the operator handles repeat submissions after a connection failure.
| You find | Likely next step |
|---|---|
| One accepted bet ID | Keep the slip and follow its normal status |
| Two accepted bet IDs | Record both and contact support if unintended |
| No slip, no stake movement | Check again after account refresh before deciding |
| Stake movement, no slip | Raise a support case with transaction details |
When history shows no bet
Refresh once or sign out and back in, then search the correct date range. Also check whether you were using a different account, product or bet-history filter. An empty bet list and unchanged wallet suggest the placement failed. Search the date range again after the account refresh, then decide whether a new bet makes sense.
A stake debit without a matching slip needs support tracing. Send the transaction time, amount and error screenshot. Ask whether a bet ID exists for that debit; its existence decides whether there is a wager to settle.
Avoid a second unwanted bet
A second tap can create a second live wager rather than “retry” the first. Wait until the first attempt is resolved in bet history or by support. A closed market blocks a fresh submission. A reopened market can offer a new price. That is a fresh wager with new odds.
Reliable bet-history search is a useful account feature when comparing betting sites in Nigeria. After a connection drop, the accepted bet ID is the decisive record.
