Solved SatoshiDice 3 BCH win paid

[sukbir]

Hi guys, I am writing behalf of my mate. He was betting on 1000x that is less than 65 bet roll, luckily he won that bet but payment stuck for more than 12 hrs. I have been playing SD for long time but never face issue like this.

I told my mate it will paid after few blockchain confirmation but it was not paid till now. I checked in the gamed id it was showing "Error Message: Rebuilding transaction" . I was thinking due too many transaction his winning transaction was stuck but it was not.SD hasn't broadcast any payment transaction in bch network. I think must be issue with SD internal system.
Do you guys have same experience like this ??


update: finally paid


 I have shared his game id

[1714691258]

1714691258

[1714691258]

1714691258

[alegotardo]

Your friend must have taken a big scare!!
If it went with "any" other site I would say it was a scam, but when it comes to satoshidice.com that would be really strange.

More than 12 hours of waiting is a long time, probably the payment was "stuck" waiting for some manual verification to confirm that everything was ok before releasing the payment, but in these cases, I believe that your friend should at least receive an email about the possibility of late payment.

[sukbir]

Thank you for reply mate. issue have been solved

[numanoid]

Thank you for reply mate. issue have been solved

Then lock this thread, since the problem has been solved. Your friend is lucky he still got his withdrawal, while there are few users who still having trouble with their withdrawal from this site.

[romero121]

You friend is truly a lucky person, he won a big multiple value. Second thing, the issue has got solved in little time. Internal server errors were common, but a notification regarding the same will make the platform more trustworthy. In this case, player would've got a thought big wins won't be paid. Such thoughts will won't encourage people to spend further.

[boyptc]

issue have been solved

Time to lock this thread if the issue has been solved. Glad to see that issues like this have been solved after a few days.