How to withdraw at Ezz
Getting money out is always more administrative than putting it in, and that asymmetry is not a platform quirk — it is the effect of the identification duties that sit on any operator. This page follows a withdrawal request the way it is actually processed: who approves it, which documents support the approval, which states it can rest in, and by which route the money physically returns. Rails and calendars are compared on the payments page.
Open the Ezz cashierSubmission, review, execution
- Submission. The amount leaves the playable balance the moment the request is created. It can no longer be wagered, and it has not yet left the platform.
- Review. The operator's finance team checks the request against the identity file and against recent account activity, particularly any unfinished bonus.
- Execution. The instruction goes out to the payment provider. Only from here does the outside calendar — wallet, network or business days — govern the timing.
Mixing up stages two and three is behind most complaints about slowness. A request approved on Friday evening can be executed immediately and still land in a bank account on Tuesday, with nobody having delayed anything.
The rails that only take money in
Multibanco and Paysafecard do not pay withdrawals. This is not an operator policy: a reference is a collection instruction and a prepaid code is a bearer credit, and neither is an account that can receive funds. Anyone who deposited through them is paid by bank transfer to a PT50 IBAN in the account holder's own name. That adds two steps which did not exist on the way in — registering the IBAN in the cashier, and waiting for the banking calendar. The individual files cover each case: Multibanco and Paysafecard.
The hold on the first payout
A first request triggers account verification, and until the file is complete the request is held rather than refused. What is asked for is consistent:
- Citizen card, front and back, with all four corners visible and no glare covering a field.
- Proof of address issued within the last three months — a utility bill or a bank statement, with the name and address legible.
- Evidence of the payment instrument used to deposit: a card statement with the middle digits masked, a wallet screenshot, or an IBAN certificate.
A tax number may be requested in addition. Files go to the operator's own account area and are reviewed by its team; this notebook never receives or stores documents. Blurred or cropped photographs are the most ordinary reason a file is sent back, and each round trip adds a full review cycle to the wait.
How long each return route takes
| Return route | Floor | After approval |
|---|---|---|
| E-wallet (Skrill, Neteller) | €20 | 1–12 hours on a business day |
| MB WAY or the account behind Multibanco | €20 | Same business day |
| SEPA transfer to a PT50 IBAN | €20 | 1–3 business days |
| Visa or Mastercard | €20 | 1–3 business days |
| Litecoin or USDT | €20 | Up to 24 hours |
Why requests come back
Four causes account for nearly all of them: a name on the destination that does not match the gaming account, one wrong character in an IBAN that surfaces as a return days later, a request made while a bonus campaign is still running, and an amount below the €20 floor. None of these makes money disappear. All of them send the request back to the balance with the delay of the full round trip attached.
The habit that costs the most
Cancelling a request in order to keep playing is the single most expensive reflex on this page. Every cancellation returns the amount to the playable balance and restarts the entire review cycle when the request is submitted again. Deciding a payout figure and leaving it alone measurably shortens the wait and the number of conversations with support. Limit tools are described under responsible gambling, and the permanent option under self-exclusion.