Lol... I guess I lost the guessing game then xP
Bet refunded
Started by Insignificant [136254] on in Bugs & Issues.
Posts archived: 31 / 31 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Lol... I guess I lost the guessing game then xP
[image: i250.photobucket.com]%5BURL=https%3A//s250.photobucket.com/user/breakmyfootoff/media/Capture.png.html%5D%5BIMG%5Dhttps://i250.photobucket.com/albums/gg248/breakmyfootoff/Capture.png%5B/IMG%5D%5B/URL%5D
I guess this rule no longer applies. We should be seeing a cancel/refund bet button any day now.
I dont know why but betfair exchange api returns this result:
object(stdClass)#93 (3) {
["jsonrpc"]=> string(3) "2.0"
["result"]=> array(1) {
[0]=> object(stdClass)#96 (16) {
["marketId"]=> string(11) "1.151942799"
["isMarketDataDelayed"]=> bool(false)
["status"]=> string(6) "CLOSED"
["betDelay"]=> int(0)
["bspReconciled"]=> bool(false)
["complete"]=> bool(true)
["inplay"]=> bool(false)
["numberOfWinners"]=> int(1)
["numberOfRunners"]=> int(2)
["numberOfActiveRunners"]=> int(0)
["totalMatched"]=> float(0)
["totalAvailable"]=> float(0)
["crossMatching"]=> bool(false)
["runnersVoidable"]=> bool(false)
["version"]=> int(2536442426)
["runners"]=> array(2) {
[0]=> object(stdClass)#97 (5) {
["selectionId"]=> int(50186)
["handicap"]=> float(0)
["status"]=> string(7) "REMOVED"
["removalDate"]=> string(24) "2018-11-29T18:06:39.000Z"
["ex"]=> object(stdClass)#100 (3) {
["availableToBack"]=> array(0) { }
["availableToLay"]=> array(0) { }
["tradedVolume"]=> array(0) { }
}
}
[1]=> object(stdClass)#99 (5) {
["selectionId"]=> int(50189)
["handicap"]=> float(0)
["status"]=> string(7) "REMOVED"
["removalDate"]=> string(24) "2018-11-29T18:06:39.000Z"
["ex"]=> object(stdClass)#98 (3) {
["availableToBack"]=> array(0) { }
["availableToLay"]=> array(0) { }
["tradedVolume"]=> array(0) { }
}
}
}
}
}
["id"]=> int(1)
}
As you can see, the runner status is "REMOVED" for both runners. It means that we have to refund bets or set result manually. I understand that it looks unfair when your bet won but we added API to increase bet abilities and handle it automatically.
I checked another matches from this thread. They are also marked as "REMOVED".
["removalDate"]=> string(24) "2018-11-29T18:06:39.000Z"
It also says they've been removed almost 2 weeks ago. Why does torn keep showing bets that have been removed for weeks?
Wow. Just wow
Hi Kopites,
Thank you for the response. Are these bets (Chicago Bears, Seattle Seahawks, and Dallas Cowboys) going to be manually fixed?
Eh, probably not m8, tis my guess that money will not be sent out as the money we placed was refunded n not taken from us... we were just unlucky... I do believe however that Kopites had a long discussion with a few programmers on betfair's end about making sure that this doesnt happen again.... my suggestion is that they (betfair) should not remove/cancel bets simply because of a wording error i.e. Chicago is listed as the title instead of Chicago Bears... simple enough... matches should only be canceled if there is a serious error like the betting odds are wrong or the match doesn't even exist in RL or matches that are actually canceled in RL.. That's my suggestion anyways.
The match was not deleted due to the title. I can show you 20+ bets that were listed the same way that were not deleted. This absolutely should be fixed it is just a matter of whether someone wants to spend the time doing it.
So Isn't it right to set result manually? We bet according to rule, and it will be only fair to fix the result for those problems? INSTEAD of refund. And in betfair, this game was REMOVED 2 weeks ago. Instead of saying unfair for winner, and blame for betfair...we can't blame betfiar isn't ?
Update?
We are planing to migrate to another bet api provider.
So we close all reports related to the any suggestions and missed games, bets or start time
as it will be fixed by the next API provider.
So we close all reports related to the any suggestions and missed games, bets or start time
as it will be fixed by the next API provider.