Legal status
As with Apple Pay, nothing in the Gambling Regulation Act 2024 addresses Google Pay specifically. The card behind it determines the rules: a debit card is standard funding, a credit card behind Google Pay is caught by the same Section 165 ban as any other credit card deposit.
What Google Pay actually is at a casino cashier
Google Pay's own user policies prohibit gambling payments directly from a Google Pay wallet balance. Instead, when you select Google Pay at checkout, it auto-fills the debit or credit card details already stored in your wallet into the casino's card field, confirmed via PIN or biometric authentication. The transaction that actually processes is a normal card payment — Google Pay is the autofill layer, not the payment rail.
Why withdrawals work the way they do
Google Pay won't accept a payment directly to the wallet balance. Where an operator supports Google Pay for withdrawals at all, funds return to the same underlying card used for the deposit, and usually only after at least one real-money deposit has gone through that route. Treat it the same way as Apple Pay: check the cashier's specific withdrawal options before assuming symmetry with the deposit method.
Why a deposit gets declined
- The underlying card is declined — a bank gambling block or credit-card restriction applies exactly as it would to a manually entered card.
- The operator doesn't support Google Pay at all — availability is narrower than Apple Pay at many operators.
- Outdated app or OS version on the Android device.
Fees
Google doesn't charge for Google Pay transactions itself. As with any wallet layered over a credit card, your card issuer may apply its own fee structure to a gambling-coded transaction, particularly if it's classified as a cash advance.
Related reading
See Apple Pay for the iOS equivalent, and debit cards for the rules that actually govern the card sitting behind the wallet.