How we protect a payment in the V1 Casino cashier

Updated
We treat the security of a payment as a stack of layers. No single layer is enough, and a member who understands all five can tell which one is acting at any moment. The cashier is the same for every route, and the layers apply to it in the same order.
| Layer | What it does | Who holds it |
|---|---|---|
| 1. Instrument | The payment comes from something in the member’s own name | The member |
| 2. Authorisation | A bank or provider approves the payment outside our site | Bank or provider |
| 3. Confirmation | The cashier shows method and AUD amount before release | Us |
| 4. Ceilings | Limits cap what can be paid in or lost | The member |
| 5. Finality | The route decides whether a payment can be reversed | The route |
Play nowLayer 1: the instrument must be the member’s own
We ask members to pay and withdraw with an instrument held in their own name. A card, wallet, bank account or crypto wallet that belongs to someone else breaks the link between the person who registered and the person who is paid, and it is the most frequent reason a withdrawal is held for review. Our cashier lists no casino fee for any route, and a bank or provider may charge separately.
Layer 2: authorisation outside our site
Most routes hand the member to a second party before money moves. A card payment is checked by the issuing bank. An e-wallet payment is approved inside the wallet. A bank route asks the member to sign in at the bank and approve the amount. We never see those credentials, and we never ask for them. A message that asks a member for a bank or wallet password in our name is not from us.
Layer 3: confirmation in the cashier
- Read the method named on the confirmation screen and check that it is the one intended.
- Read the amount and check that it is in AUD.
- For a voucher, check that the code is entered in full.
- For crypto, compare the first and last characters of the address with the one the cashier shows.
- Release the payment only after these checks.
- Wait for the balance to update before starting a second payment.
Two errors account for most of the payments that need correction: a payment sent by the wrong method, and an address typed by hand.
Layer 4: ceilings that the member sets
A deposit limit caps what can be paid in during a chosen period, and a loss limit caps what can be lost. Both sit in account settings and can be set before the first payment. A limit that is already in place stops a rushed deposit without any further action by the member.
Layer 5: finality
What can be undone depends on the route.
| Route | Can the payment be disputed or reversed? | Where the request goes |
|---|---|---|
| Card | Through the issuing bank | The bank |
| E-wallet | According to the provider’s rules | The provider |
| Bank route | By the bank, if the transfer is wrong | The bank |
| Voucher | No, because the code is spent when used | Nowhere |
| Crypto | No, because confirmed transfers are final | Nowhere |
A member who chooses a route with no reversal should check every digit before release.
Which layer matters most on each route
| Route | Layer to watch | Why |
|---|---|---|
| Cards | 2, authorisation | The bank decides whether the payment passes |
| E-wallets | 2, authorisation | The wallet password guards the money |
| Bank routes | 3, confirmation | The account details must be exact |
| Vouchers | 5, finality | The code is the money |
| Crypto | 3 and 5 | The address must be exact and the transfer is final |
Messages that are not from us
We do not ask for a card number, a bank password, a wallet password or a voucher code in an email, a chat or a call. A message that does is not from us. A member who receives one should not reply, should not follow its links and should forward it to [email protected].
Withdrawals under the same layers
- The instrument must be the member’s own, as it must be for a deposit.
- Where the route allows it, funds go back by the route that was used to pay in.
- Sign-in details of a wallet are kept apart from the casino password.
- A member signs out of the account after a withdrawal on a shared device.
When a payment needs our review
A failed or missing payment is first checked where the money moved: the bank, the provider or the network. A member who has done that and still has no answer writes to [email protected] and states the method, the amount in AUD, the date and the reference. Withdrawals follow the speed of the route. Skrill and Neteller are completed the same day, Trustly in one to two business days and cards in one to three business days.
Reporting a payment error
An error that we made is corrected in AUD on the account, and we confirm the correction in writing. An error that the member made, such as a payment to a wrong address, is not ours to reverse on a route that is final, and we say so plainly when the member writes.
Keeping a record
We advise members to keep a short record of each payment: the date, the method, the amount in AUD and the reference. The record lets our support team answer a question in one reply and lets the member compare the account with a statement from the bank or the wallet.
FAQ – V1 Casino
Layer 2: the issuing bank. Contact the bank first.
No. We do not see bank or wallet credentials.
No. The code is spent when it is used.
Confirmation on the network. We cannot recall it.
Yes. Set it in account settings.
Layer 1 requires an instrument in the member’s own name.













