Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Wireless Networking Communications

NFC Release 15 Extends Tap-to-Pay Range From 0.5cm To 2cm (nfc-forum.org) 24

The NFC Forum has released NFC Release 15 (that's what it's calling it), extending the operating range of Near Field Communication connections from 0.5 centimeters to 2 centimeters -- a fourfold increase that reduces the precision required for device alignment.

The global standards body, whose board includes representatives from Apple, Google, Huawei, Infineon, NXP, Sony, and ST Microelectronics, designed the enhancement to accelerate transaction speeds and improve reliability across NFC-enabled devices. The expanded range addresses technical challenges in smaller form-factor devices like wearables and smartphones while maintaining compatibility with existing ISO/IEC 14443 standards.

The standard also incorporates support for NFC Digital Product Passport specifications, allowing single NFC tags embedded in products to store and transmit sustainability data throughout their lifecycle.

NFC Release 15 Extends Tap-to-Pay Range From 0.5cm To 2cm

Comments Filter:
  • Dangerous? (Score:5, Insightful)

    by Excelcia ( 906188 ) <slashdot@excelcia.ca> on Wednesday June 18, 2025 @02:10PM (#65458951) Homepage Journal

    The right equipment already can extend that range further... in some cases up to 30cm with a high Q antenna. This is what malicious actors use to get people's cards in sketchy airports and markets the world over. I'm not sure the extra range from .5 to 2cm in nominal use is worth giving thieves more range to work with.

    How about vendors who are having problems just start using better equipment. I use square in my little restaurant and have never had an issue with it. This seems to be solving a non-problem at the expense of introducing more.

    • Yup. I can see the use case being smart phone NFC and a thick phone case.

      • by taustin ( 171655 )

        If your phone case is over .5 cm thick, I don't think the range of NFC is your problem.

        • If your phone case is over .5 cm thick, I don't think the range of NFC is your problem.

          I like to ensure my phone is well protected. My phone case [specialtycases.com] even has wheels... :-)

        • by tlhIngan ( 30335 )

          If your phone case is over .5 cm thick, I don't think the range of NFC is your problem.

          It's not the phone case distance, it's coil to coil. And the case of the payment terminal might be 1mm thick, while your phone and case might easily be 2mm thick so that's 3 mm of the 5 with it physically touching. Add in a slight distance from misalignment of the coils and it could make it hard to read.

          While 2cm would be you only have to bring your phone close to the terminal, not having to align the coil of your phone w

  • Works fine here at least 1cm away on a 2yr old phone..
    • From TFA:

      Q: Are there NFC devices in the marketplace today that operate at 2 cm? And if yes, why is NFC Release 15 needed now?

      A: Yes, some devices can already operate at ranges of 2cm or more. However, the role of the NFC Forum role is to define a consistent, reliable industry baseline that applies across the full range of NFC-enabled devices and use cases â" including small-form-factor products like wearables and smartphones.

      tl;dr: Not every manufacturer does the bare minimum.

    • It is probably the specification minimum that is referenced in TFS and is extended by the new spec.

    • Works fine here at least 1cm away on a 2yr old phone..

      Congrats on not understanding what is being discussed. The question wasn't distance, the question was one of alignment. And yes you can see it daily on phones from every manufacturer where people wiggle it around looking for the actual sweet spot for a payment to work.

      • The question wasn't distance, the question was one of alignment. And yes you can see it daily on phones from every manufacturer where people wiggle it around looking for the actual sweet spot for a payment to work.

        Ouch. Yes. I see this every day. Although most of the time the phones or watches work really well. It is the people with an actual card that try over and over to find the spot -all the while moving their card way too fast for the reader.

        • Putting the card into the reader solves this issue. The slot is there for a reason.

          • by hwstar ( 35834 )

            The slot's contacts get contaminated with dirt and debris on peoples cards. (Looking at you Wal-mart, who don't support tap-to-pay on their CC terminals) Need to get rid of the contacts, and do close-in NFC in the slot instead. That way, the action has to be willful.

        • Yeah I would love to see an NFC standard that didnt extend the range, but instead specified where in the (*^^*&^#@ the reader was on the POS system, or at least a lit up nfc logo where you want me to tap.... Every POS I go up to has it somewhere else, and finding it is a pain

    • That's what she said!
  • The standard also incorporates support for NFC Digital Product Passport specifications, allowing single NFC tags embedded in products to store and transmit sustainability data throughout their lifecycle.

    You've got to be shitting me! Their solution to sustainability is to embed an electronic chip into every single thing?! Man, this planet is truly fucked!

    • Uh, chill out. It's not harmful. What is your concern? It's a tiny amount of silicon and some metal. Less resource consumed than making a few beads of glass. Or have you lost your marbles?

      • by kackle ( 910159 )

        Less resource consumed than making a few beads of glass.

        But not less than no tag at all for a dubious purpose.

  • for someone to extract a payment that I did not intend from my 'phone ? This seems to me to be a security risk, a gift to crooks.

    • Your phone doesn't look for authorization from you before just giving your money away via an NFC transaction?

      Or do you just blindly (and boldly) approve every box that comes up asking for authentication regardless of if you took an action that would require authentication?

      • Your phone doesn't look for authorization from you before just giving your money away via an NFC transaction?

        Or do you just blindly (and boldly) approve every box that comes up asking for authentication regardless of if you took an action that would require authentication?

        The whole idea of NFC is "convenience" which is usually inverse to security.

        Many cities allow NFC for public transport, for example. If you have to authorise every single tap-on and tap-off when using your phone to pay for the subway or bus. this is *not* convenient and I would expect that ~99% of people who use their phones for this job have the authorisation turned off.

        Note that I am not suggesting that using your phone to pay for stuff like this is a good idea, just stating what I have seen other people

    • by linuxguy ( 98493 )

      > This seems to me to be a security risk..

      Aren't you usually required to have your phone unlocked for most of these NFC things to work? My phone is always locked, unless I am using it. And when I make a transaction, my phone immediately tells me and makes sounds as well. I am trying to thing of ways the .5 -> 2cm change can be abused and I am coming up empty.

      If you have a particular case in mind that would actually work, please share.

      • I have credit and debit cards with NFC chips. No authentication required to tap and pay, up to a certain amount.
      • I would assume the risk is someone taking a payment from your physical credit card through your pocket/wallet. But I donâ(TM)t know if the new standard changes the cards or just the minimum distance the reader must be able to reach. If the latter, then there really wouldn't be any effect on security.

    • by AmiMoJo ( 196126 )

      Doesn't your phone need to be unlocked to make a payment? Mine requires biometric authentication.

      Recently an update introduced an option to not unlock for public transit. I haven't looked into it, presumably there is some security mechanism in there, but I didn't enable it anyway.

Always try to do things in chronological order; it's less confusing that way.

Working...