Google Pay not working in Android Auto: Australian fixes

If Google Pay is not working on Android Auto, the fault may be in the car connection, mobile wallet or payment card. Android Auto projects the phone’s apps, while contactless payments use near-field communication (NFC). Navigation can therefore work normally while a tap fails, or the wallet can work elsewhere but disappear from a vehicle display.

In Australia, Google Wallet is now the main Android app for features commonly called Google Pay, although some devices retain the old branding. The bank must support the selected card in Google Wallet. eftpos debit-card support varies by issuer, so a physical contactless eftpos card is not automatically eligible for mobile payments.

Vehicle setup adds another layer. Many newer Australian cars support wireless Android Auto, while older cars usually need a USB cable that carries data as well as power. A contactless transaction normally needs no mobile data, although an Optus or Telstra outage can prevent first-time card verification.

Public transport offers a misleading test. Sydney Opal and Melbourne myki readers operate within their own transport systems, so those gates cannot confirm whether an Android Auto problem is real. A contactless terminal at Coles or Woolworths, or a supported vehicle payment pad, provides a cleaner result and separates a card decline from a connection fault.

Separate car pairing from tap to pay

Begin by disconnecting Android Auto. Unlock the phone with its PIN, pattern or password, open Google Wallet and hold the back of the handset near the reader. If payment succeeds here, the wallet, NFC and card are probably sound; the problem lies in the car pairing or an app conflict.

Reconnect Android Auto and repeat the test. Bluetooth may be carrying the projection while NFC handles the payment, so a healthy Android Auto session does not prove the wallet can pay. If the two work separately but not together, close other wallet, banking or parking apps before trying again.

Confirm wallet, card and NFC settings

Open Google Wallet and confirm the card appears with a valid status, the phone has a secure screen lock, and the wallet’s country is Australia. In Android settings, turn on NFC and select Google Wallet as the default contactless-payment app. Also check the issuer’s app for a Google Wallet or Google Pay limit, block or expiry.

Update Android, Google Wallet, Android Auto, Google Play services and the Play system through Google Play. These updates matter because bank token provisioning and vehicle pairing can fail against outdated components. On managed work phones, an IT policy may disable NFC or background wallet access; that restriction also affects personal cards.

Repair the Android Auto connection

For a wireless connection, forget the car in Android Auto’s Bluetooth settings, toggle Bluetooth and Wi-Fi, then pair the vehicle again. For USB Android Auto, try another data-capable cable and another USB port. A charge-only cable common in an older Australian model can carry navigation data poorly or not at all.

Restart both the phone and infotainment system before testing. If Android Auto connects but errors whenever the wallet opens, clear the Android Auto app cache and re-pair from the vehicle menu. Menus differ across Holden, Kia, Toyota, Nissan and other brands, but the reinstall path is usually under Apps, Android Auto or Connections.

Run a focused recovery checklist

When the quick settings have not solved the issue, use this recovery order:

• Update the handset and listed apps, then reboot the phone.
• Set Google Wallet as the default NFC payment app and confirm NFC is on.
• Remove the card from Wallet, verify issuer eligibility, then add it again.
• Forget the vehicle and repeat Bluetooth pairing or the USB connection.
• Clear cached data for Wallet and Android Auto without uninstalling either app.
• Record the exact error, transaction amount and time before contacting support.

Work from the phone outward: handset settings, wallet and card, then the vehicle. Avoid removing several apps at once, because that makes it harder to identify the component that changed the result. Keep the bank’s app open until any identity or SMS verification has finished.

Reset apps and network components

Cache clearing is safe, but a full reset is not the first move. In Android’s app manager, clear storage for Google Wallet and Android Auto, then reboot. If the wallet closes when it opens, check battery optimisation and allow the app to run in the background. Samsung’s Knox policies and employer-managed devices can also block secure payments.

If a newly added card fails verification, switch between mobile data and Wi-Fi, briefly cycle airplane mode, and temporarily disable a VPN or private DNS setting. Check that the phone’s date and time are automatic. Some Australian banks send an approval SMS during card provisioning, so blocked messages or failed verification can look like an NFC fault.

A factory reset should remain a last resort because wallets and banking tokens must be restored and re-verified. Back up the handset first, reinstall only from Google Play, and recreate the Wallet card before reconnecting the car. If the same card works in another phone but not this one, the handset is the stronger suspect.

Verify the fix on supported readers

Test the repaired setup away from Android Auto, then reconnect it and test again. Use the Coles or Woolworths reader for the first comparison and save the receipt. If the wallet works at the store but not in the car, the vehicle’s NFC reader, firmware or compatibility list is the likely area to examine.

If it fails at both places, check the issuer’s block list, card limits, contactless status and Google Wallet support. Contact the bank with the declined amount and exact wording; some restrictions are visible only in the banking app. Vehicle problems belong with the manufacturer or dealer, while Android Auto pairing questions can be checked with Google.

A community reference for Android Auto troubleshooting may help when menu names differ across handset makers. A completed diagnosis identifies one of three outcomes: the wallet works independently, Android Auto pairs cleanly but the car cannot initiate payment, or the issuer refuses the token. Each outcome sends the fix to a different support team.