7 points

The loophole seems to be having an app pinned to the screen (I’ve never done this, but it presumably keeps the phone from locking) while requiring you to have an unlocked phone to use NFC payments. This doesn’t seem to be a common scenario (I can imagine doing this in some sort of kiosk mode, or giving the phone to a kid and locking the app so he can’t wander around).

permalink
report
reply
-2 points

This is why Samsung pay is king, the NFC only turns on when you’re using Samsung pay otherwise it stays off

permalink
report
reply
24 points

Turn off NFC unless you are using it at that moment.

permalink
report
reply
8 points

Woah, first I learned of this. https://www.lifewire.com/turn-off-nfc-to-secure-your-android-smartphone-2532822

Kinda sucks that there’s no quick button for that. I can turn off Bluetooth, wireless, auto-rotate, etc in a single setting but not NFC?

permalink
report
parent
reply
1 point

You can try using Tasker to create a task that turns on NFC and launches Google Wallet / Pay afterwards.

After that, create another profile to turn off NFC when the screen is locked.

permalink
report
parent
reply
22 points

permalink
report
parent
reply
2 points

Which system do you have, with the NFC quick toggle?

permalink
report
parent
reply
3 points

I’m so envious of you. I don’t have that.

permalink
report
parent
reply
1 point
*
Deleted by creator
permalink
report
parent
reply
1 point

You can diasble all sensors and make a quick button for it in dev settings, dont remember how exactly it is called tho

permalink
report
parent
reply
6 points

Many Samsung devices have a quick button for NFC toggling in their drop down menu, not sure about other phones though.

permalink
report
parent
reply
2 points

I have a Samsung Galaxy Watch, it has a button for that too. But also the Wallet app on the watch has to be manually opened to use it anyways, it’s not passive background app. I think I might just disable NFC on my phone and stick to using my watch for payments.

permalink
report
parent
reply
68 points

I thought Google wallet generated a unique card id for every transaction.

This is a interesting bug, but I think fairly niche. Not many people use app pinning at all.

permalink
report
reply
Deleted by creator
permalink
report
parent
reply
12 points

If the PoS supports tokens, it’ll use unique tokens for each payment. If the PoS doesn’t support tokens, the phone has a virtual credit card number linked to the real one, so if it does get stolen, you can just remove the card from your Google Wallet to deactivate it. Your real card number is never exposed.

Even then, credit card numbers on their own aren’t that useful anymore. Any online payment needs the CVC and PoS devices usually require chip or tap cards, which don’t use the number. On top of that, credit card companies have purchase price restrictions when using swipe because of the security risks vs chip (which is why most PoS devices don’t support swipe anymore).

permalink
report
parent
reply
1 point

“which is why most PoS devices don’t support swipe anymore”

huh?

permalink
report
parent
reply
1 point

Great explaination. Thank you

permalink
report
parent
reply
10 points

I didn’t even realize “app pinning” was a thing.

permalink
report
parent
reply
18 points

great

permalink
report
reply

Android

!android@lemdro.id

Create post

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it’s in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it’s not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website’s name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don’t post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities
Lemmy App List
Chat and More

Community stats

  • 1.5K

    Monthly active users

  • 2.8K

    Posts

  • 34K

    Comments