Remove saved payment details before sharing a browser
Check local autofill and Google Wallet separately, stop unwanted saving and use an appropriate separate browsing session.
In brief
Turning off payment autofill stops automatic filling but does not necessarily delete the saved cards. Inspect where each method is stored before sharing a browser or passing on a device.
A separate user or guest session avoids mixing another person’s browsing with your signed-in payment and account context.
Identify the storage location
Chrome can show payment information saved locally or associated with Google Wallet. Use the method’s appropriate management action. When account-based changes sync to other devices, consider the intended result; do not delete a needed method everywhere just to lend one browser session.
Choose a better sharing boundary
Use a guest session for temporary browsing where appropriate, or a separate OS account for ongoing device sharing. A browser profile is convenient separation but is not strong isolation from another person who controls the same unlocked OS session. Sign out of sensitive accounts too.
Verify the cleanup scope
Check the relevant payment list again and review addresses and other autofill records if the device is changing hands. Do not test by entering real card details into an unfamiliar site. For unauthorized charges or exposed card data, contact the payment provider; deleting autofill alone does not resolve the payment incident.
Before you act
Removing a saved method does not cancel a subscription or refund a purchase. Google Wallet and local browser records can need different controls.
What to do next
- Open Chrome’s Passwords and autofill → Payments and inspect saved methods.
- Remove unwanted local entries; use Wallet’s controls for methods stored there.
- Review saving/filling settings and use a suitable separate session before another person browses.
