Getting Started with Google Pay
If you have an Android device, you can use Google Pay to make contactless payments at checkout terminals without needing to carry your physical debit or credit card. Commonwealth Bank cards are fully compatible with Google Pay, allowing you to use your phone to pay for goods and services anywhere you see the contactless symbol.
Setting this up is a straightforward process that links your card securely to your device. Rather than using your actual card number, Google Pay creates a unique, encrypted "token" for every transaction. This ensures your card details remain hidden from merchants, which adds a layer of safety to your daily spending.
Key Details for Setup
| Category | Details |
|---|---|
| Methods | CommBank App or Google Wallet app. |
| Processing Time | Available for use immediately after verification. |
| Eligibility | Compatible Android device (NFC enabled) and an eligible CommBank card. |
| Requirements | Device must have a screen lock (PIN, pattern, or biometrics) enabled. |
To start working with Google Pay on your mobile you should:
- Download the application on your Android device from Google Play
- Log in to the app
- Tap "+"
- Enter details of your card from CBA
- Confirm the procedure with an SMS code or via the Commonwealth app
Troubleshooting Common Issues
MFA / Login Issues
If you do not receive the verification code needed to finish your setup, this is typically caused by mobile network delays. A simple fix is to check that your mobile number in the CommBank app is up to date and try again. If it still fails, toggle your phone's airplane mode to refresh your network connection before requesting the code again. If this fails, call the bank to confirm your contact details are correct.
Browser or App Errors
If the app displays an error while trying to add the card, it usually happens because your CommBank app version is outdated or your phone's software has pending updates. Try updating both the CommBank app and the Google Wallet app from the Google Play Store. If that does not work, clear your cache for these apps, restart your phone, and attempt the setup once more.
Locked Account / ID Issues
If your card is locked or you cannot access your account to add it to Google Pay, you will need to resolve the account status first. You can check your card status within the CommBank app. If the card is restricted, follow the on-screen prompts to unlock it. If you continue to face access issues, you will need to contact the bank's support team to verify your identity and restore access.
Pro-Tip: To save time at the register, make sure you set your preferred CommBank card as the "default" payment method within your Google Wallet settings. This ensures your phone uses your chosen account whenever you tap to pay, rather than asking you to select a card each time.
Frequently Asked Questions
Why was my payment declined at a terminal?
Even if your phone indicates a successful payment, the transaction might be declined by the terminal. This can occur if the merchant’s system doesn't support contactless payments, or if you have hit your daily transaction limit. Additionally, check that your device's NFC (Near Field Communication) is turned on in your phone's settings. If you’re unsure why it failed, check the transaction history in your CommBank app; if it doesn't show up, it likely means the issue was with the merchant's machine, and you should try a different terminal or your physical card.
Is my information shared with the merchant when I pay?
No, the system works by using a digital token rather than your actual credit or debit card number. When you tap your phone, the merchant receives this token to process the payment, which prevents them from seeing or storing your sensitive banking details. This protects you in the event of a merchant's data breach. If you ever lose your phone, you don't necessarily need to cancel your physical card, but you should still use the "Find My Device" feature to secure your account or call the bank to suspend the digital tokens associated with your phone.
