Withdrawal Issues: 70,000 HUF at Playbet.io

StatusUnresolved

Amount70,000 HUF

Player—

Opened2026-10-16

Resolution time—

What Happened

A player says a 70,000 HUF withdrawal from Playbet.io has been stuck for about three weeks, though their ID and selfie checks were approved. Card payouts kept failing, and support blamed the payment providers. On 9 October an agent agreed to pass the request to the finance team for a manual bank transfer, and the player sent their bank details. They say nothing has happened since.

How It Developed

Automatic card payouts failed several times. Support said payment providers were blocking them.
2026-10-09Support agreed to send the request to finance for a manual bank transfer, and the player gave their account details.
Complaint opened after more silence. The player says live chat agents could not see the request or closed the chat. No replies appear on the page yet.

Unresolved

AskGamblers lists it as unresolved, but the page shows no replies at all. Nothing shows the 70,000 HUF was paid.

What Has (and Hasn't) Helped

Too early to tell: no one has replied on the page yet. If card payouts keep failing, ask support to confirm in writing the new payout method and a date, then quote that in any complaint.

Same issue, other cases

Related Cases

2026-05-30 Playbet.io: Withdrawal Issues · €25,154 (about 0.4 BTC)
A player from Ireland says Playbet.io held a 0.4 BTC withdrawal, requested on 18 April 2026, for six weeks over a supposed game glitch, without naming rounds or rules. Unresolved 2026-07-22 Playbet.io: Withdrawal Issues · C$2,230
A player from Ontario says they deposited C$400 at Playbet.io, won about $1,592 on roulette, and had the withdrawal rejected three times. Abandoned 2026-10-11 Playbet.io: Withdrawal Issues · amount n/a
A player from Australia says every withdrawal they have tried at Playbet.io for a couple of months has been rejected. Ongoing 2018-05-15 FortuneJack: Withdrawal Issues · 1.68 BTC
A player from Norway says their first FortuneJack withdrawal was paid, but the next one was stopped for security reasons with no explanation. Unresolved