Skip to main content

Ticket Errors

Ticket Status can get added to a ticket ether from

  • Internal Logic, for example detection that race has closed for the ticket. or
  • Failed Placement, which the source of the Error could come from ether
    • BetDirector
    • Wagering Plateform
    • Wallet API, rejected the placement

Internal Logic Status​

this is a incomplete list which we will provide more detail over time.

  • RACE_CLOSED - detected race is no longer open and will block placement on this bet/ticket
  • Stake Rounded - stake on a ticket rounded down inline with ToteProduct Rules on a race

Failed Placement Status​

the status returned from bet placement will be shown in the UI above the ticket/bet and breifly shown in a toast message. see image for example Betslip Error

Common Status From Wagering Tote Provider

Backend CodeUI CODEMessage To UserNOTES
2INVALID_COSTBet cost not allowed (2)Ticket cost unreasonable or wrong
3BETTING_OFFBetting Off (3)Betting off on race or pool/betType
29INVALID_CARDFailed to sell bet (29)Card number incorrect
31SALES_NOT_ALLOWEDFailed to sell bet (31)'The Tote is not prepared to sell or cash. Try again later'
34INVALID_BET_TYPEFailed to sell bet (34)An invalid bet type was sent
39INTERNAL_ERRORFailed to sell bet (39)Error of unclear origin; contact Tote support
67INVALID_RACEFailed to sell bet (67)An invalid race was sent to the Tote system
121TICKET_COST_NOT_ALLOWEDBet cost not allowed (121)An invalid bet amount was sent to the Tote
185INVALID_RUNNERFailed to sell bet (185)An invalid runner was selected
186SCRATCHED_RUNNERRunner scratched (186)A scratched runner was selected
187INVALID_LEGFailed to sell bet (187)Invalid leg number'

Wallet API Status​

this is currently under development and documentation will be provided at a later date. but rough Idea is that the response from the wallet API will be emitted as a window Event for the clients host wrapper to interpret and respond there own business logic