Why PayID and bank transfer give you proof and a card does not
This is the part worth remembering for next time, because the rail you choose decides what evidence you will have if something goes wrong.
A PayID or bank transfer leaves a statement line with the payee, the amount, the timestamp and your own reference. It also shows you the recipient's registered account name before you confirm — the single best pre-deposit check available, and the reason to read that name rather than tapping through it. A completed transfer with a matching reference is a fact that no support agent can argue with.
A card deposit leaves a merchant descriptor, which is often a payment-processor name with no obvious connection to the casino. That is normal and not a sign of fraud, but it is weak evidence: it proves money went to a processor, not what it was for. And a crypto deposit leaves the weakest position of all — no reversal, no recall, and a blockchain record that proves a transfer happened without proving what it was for. Credit cards, credit-linked wallets and cryptocurrency have in any case been banned for online wagering in Australia since 11 June 2024, which our page on the credit card ban sets out in full.
A cashier where the rails are stated before you deposit
If the reason you are on this page is a rail that left you without proof, the fix is upstream. The operator we rate first takes PayID in and bank transfer out, states the payout window before you deposit, and asks for verification up front rather than at the first payout.
View the current AUD offer ↗
Raise one ticket, not five
Support queues are worked per ticket. The same question sent through live chat, email and a web form becomes three tickets, each of which has to be opened, read, cross-referenced and closed — and in a queue that work comes out of the time available to answer you. Pick one channel, give the four facts, and ask for the answer in writing.
Two things not to put in the first message: an accusation, and a deadline. Neither speeds anything up, and the first changes the tone of a thread that may need to run for several days. Keep the ticket number.
Never send the payment again
This is the most expensive mistake available on this page. A second identical payment does not fix the first: it creates two reconciliation problems instead of one, the refund of the duplicate joins the same queue, and to a risk system two identical payments from the same account in quick succession look like a card-testing or layering pattern rather than like an impatient customer.
If you have already done it, say so in the ticket immediately. A disclosed duplicate is bookkeeping. An undisclosed one is a flag on the account, and a flag on the account is what holds a balance.