safari web nfc

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free
• Remember language

Web NFC API

Limited availability.

This feature is not Baseline because it does not work in some of the most widely-used browsers.

• See full compatibility
• Report feedback

Experimental: This is an experimental technology Check the Browser compatibility table carefully before using this in production.

The Web NFC API allows exchanging data over NFC via light-weight NFC Data Exchange Format (NDEF) messages.

Note: Devices and tags have to be formatted and recorded specifically to support NDEF record format to be used with Web NFC. Low-level operations are currently not supported by the API, however there is a public discussion about API that would add such functionality.

Interface that represents NDEF messages that can be received from or sent to a compatible tag via a NDEFReader object. A message is composed of metadata and NDEF Records.

Interface that enables reading and writing messages from compatible NFC tags. The messages are represented as NDEFMessage objects.

Interface that represents NDEF records that can be included in an NDEF message.

Specifications

Browser compatibility.

BCD tables only load in the browser with JavaScript enabled. Enable JavaScript to view data.

You can make a difference in the Apple Support Community!

When you  sign up with your Apple ID , you can provide valuable feedback to other community members by  upvoting helpful replies and User Tips .

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

NFC-tag notifications from website

Hi community,

Can anyone tell me how to turn off NFC-tag notifications from a specific website?

Safari has already sent me 60 notifications today. It’s getting out of hand.

iPhone 12, iOS 14

Posted on Oct 18, 2021 11:58 AM

Posted on Oct 20, 2021 10:51 PM

I did some investigation myself as well. I deleted my browser history and also disallowed app clips:

Setting- Screen time - limitations and restrictions- content limitation-app clips- disallow.

If you can add this information on the general support site, that would be great. It’s not very easy to find the right steps to solve this problem.

Best regards

Similar questions

• SPAM Showing Up In Notifications Refer to the attached screenshot...I visited a site that seems to have caused this notification to pop up every 5 minutes. Clicking "Show" brings you to a website. How can I stop this from happening? (aside from just turning off notifications) 631 2
• Notifications from Payette Forward I am getting adware in Notification Center from "Payette Forward" like below - I can't figure out where it's coming from and how to stop it - any suggestions? OS/X 10.14.6, MacBook Pro 319 2
• Undesired notifications. For some time now, i’ve been getting notifications of “events” from calendar. I do not want to get these notifications with links to porn sites. 223 1

Loading page content

Page content loaded

Oct 20, 2021 10:51 PM in response to Lissy_12

Oct 19, 2021 10:05 AM in response to Carsten163

Hi Carsten163,

We understand you need help with NFC tags. To clarify, are you referring to App Clips. If so, we recommend the following resource that can help:

Learn More About App Clips

As noted in the above resource "You can also manage notifications for all App Clips by going to Settings > Notifications > App Clips"

Hope this helps!

Have a great day.

Oct 24, 2021 6:17 AM in response to Lissy_12

I’ve solved the issue. There was a payment card in my phone wallet that activated the nfc-tag. By removing the card I no longer receive the notifications.

Oct 21, 2021 2:27 PM in response to Lissy_12

Hi Lissy, unfortunately the ufc-tag messages still keep popping up. Do you have another solution?

Oct 23, 2021 7:17 AM in response to Carsten163

Carsten163,

We appreciate you trying those steps. We recommend that you reach out to Apple Support directly. Please reach out here:

Get Support

This API allows a website to communicate with NFC tags through a device's NFC reader.

• ❌ 4 - 79 : Not supported
• ❌ 80 - 88 : Disabled by default
• ❌ 89 - 128 : Not supported
• ❌ 129 : Not supported
• ❌ 130 - 132 : Not supported
• ❌ 12 - 79 : Not supported
• ❌ 89 - 127 : Not supported
• ❌ 128 : Not supported
• ❌ 3.1 - 17.6 : Not supported
• ❌ 18.0 : Not supported
• ❌ 18.1 - TP : Not supported
• ❌ 2 - 129 : Not supported
• ❌ 130 : Not supported
• ❌ 131 - 133 : Not supported
• ❌ 9 - 66 : Not supported
• ❌ 67 - 75 : Disabled by default
• ❌ 76 - 110 : Not supported
• ❌ 111 : Not supported
• ❌ 5.5 - 10 : Not supported
• ❌ 11 : Not supported

Chrome for Android

• ✅ 128 : Supported

Safari on iOS

• ❌ 3.2 - 17.6 : Not supported
• ❌ 18.1 : Not supported

Samsung Internet

• ❌ 4 - 24 : Not supported
• ❌ 25 : Not supported
• ❌ all : Not supported

Opera Mobile

• ❌ 10 - 12.1 : Not supported
• ❌ 80 : Not supported

UC Browser for Android

• ❌ 15.5 : Not supported

Android Browser

• ❌ 2.1 - 4.4.4 : Not supported

Firefox for Android

• ❌ 127 : Not supported
• ❌ 14.9 : Not supported

Baidu Browser

• ✅ 13.52 : Supported

KaiOS Browser

• ❌ 2.5 : Not supported
• ❌ 3 : Not supported

Many devices are not equipped with NFC readers. They won't return any data, even though an installed browser might support this API.

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

• My W3C Account

Community & Business Groups

• Home  / 

Web NFC Community Group

The Web NFC Community Group will create a Near Field Communication API that is browser-friendly and adheres to the Web's security model. We believe that means the API will not expose full, low level NFC functionality, but rather a higher level subset that is safe for Web pages, protects user privacy, and does not annoy users with unnecessary or complex permission requests. See the Web NFC Community Group Charter and the Web NFC specification for more information.

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

Drafts / licensing info

Chairs, when logged in, may publish draft and final reports. Please see report requirements .

Web NFC API ships in Chrome

Inspired by the community’s enthusiastic response to the previous milestone that made the Web NFC API available to early adopters , the team behind the Web NFC API has been busy during 2020 perfecting the API for the next major milestone!

Today, I am beyond excited to announce the Web NFC API is shipping in Chrome 89 for Android by default! Thanks to the early adopter feedback received during 2020, the new API in Chrome 89 is even easier to use and offers the most flexible NDEF support optimized for your key use cases.

If you’re a web developer and want to learn more, please check out the most excellent developer documentation that explains with easy to understand code examples how to scan and write to NFC tags and interface with other exciting capabilities of this API.

The Web NFC API is available now in Chrome Dev and Canary channels and is coming to Beta in Jan 28 – Feb 4, 2020 and hits Stable in March 2, 2020.

Happy hacking with this new web capability! 🚀

Anssi Kostiainen , Web NFC Community Group Chair

Web NFC reaches a key milestone

Since its inception in 2015, the Web NFC Community Group has been exploring means to allow web sites to read and write to nearby NFC (Near Field Communication) devices (e.g., tags and phones) in a secure and privacy preserving manner.

I’ve had an honor to lead this passionate group of people on this journey and see how the early (some said crazy!) idea has grown and gathered a passionate community and fans around it. Thanks to encouraging feedback from a diverse group of browser engineers, spec authors, web developers, NFC technology, usability and privacy experts, and the inventor of the Web, Tim Berners-Lee himself , the Web NFC capability is now exposed through an ergonomic yet capable API able to support both emerging and established NFC use cases. What has remained throughout the years is the focus on a lightweight binary message format called NDEF that works across different tag formats, and provides a stable foundation to build on in the future.

Today, I’m thrilled to announce the group has reached the point at which it feels the Web NFC specification ( explainer ) and its Chromium implementation are ready for broader ecosystem feedback. You should see Web NFC pop up in Chrome’s Active Trials in January 2020, and if you just can’t wait, you can try Web NFC already today using Chrome Canary on Android by toggling the “enable-webnfc” flag.

Happy experimentation!

First Draft of Web NFC API published by Web NFC Community Group

On 2015-05-15 the Web NFC Community Group published the first draft of the following specification:

• Web NFC API .

Participants contribute material to this specification under the W3C Community Contributor License Agreement (CLA) .

If you have any questions, please contact the group on their public list: [email protected]. Learn more about the Web NFC Community Group .

Call for Participation in Web NFC Community Group

The Web NFC Community Group has been launched. See the Web NFC Community Group Charter and NFC input specification for more information. Anssi Kostiainen will be the initial Chair.

In order to join the group , you will need a W3C account .

This is a community initiative. This group was originally proposed on 2015-03-11 by Wayne Carr. The following people supported its creation: Wayne Carr, Jeffrey Yasskin, Zoltan Kis, Aswini S, Anssi Kostiainen. W3C’s hosting of this group does not imply endorsement of the activities.

Read more about how to get started in a new group and good practice for running a group .

We invite you to share news of this new group in social media and other channels.

If you believe that there is an issue with this group that requires the attention of the W3C staff, please email us at [email protected]

Thank you, W3C Community Development Team

Tools for this group

• @ public-web-nfc
• @ public-web-nfc-contrib
• @ internal-web-nfc
• Contact This Group

Get involved

Anyone may join this Community Group. All participants in this group have signed the W3C Community Contributor License Agreement .

Anssi Kostiainen

Participants ( 45 )

View all participants

• January 2021
• December 2019
• Announcements

Remember me

Log in or Request an account

Download Free

Browser Terms Explained: Web NFC API

It's free and super easy to set up

In today’s world, we are surrounded by digital devices that help us in various ways. One of the most prevalent technologies that are being used these days is Near Field Communication or NFC. It enables us to transfer data wirelessly between two devices. To simplify the use of NFC in our web applications, a new technology was introduced years ago called Web NFC API. In this article, we will explore this technology in-depth and understand its implementation, use cases, and real-world applications.

Understanding Web NFC API

Web NFC API is a technology that allows web applications to read and write data to NFC tags. It provides a seamless experience for the users as they no longer need to install any external applications on their devices to interact with NFC tags. This technology makes use of the NFC hardware that is integrated into modern-day devices, like smartphones and other electronic gadgets, to create two-way communication between these devices.

What is NFC Technology?

NFC or Near Field Communication is a wireless technology that allows two devices to communicate with each other when they are placed close together. It operates on radio-frequency identification (RFID) technology and is used in various applications like contactless payments, access control, and IoT device management.

How Web NFC API Works

Web NFC API is integrated into web browsers like Google Chrome, Mozilla Firefox, Safari, and Microsoft Edge, and enables web applications to access the device’s NFC hardware. When a user taps an NFC tag with their device, it automatically triggers a web application that is capable of reading NFC data. The application can then read the data from the NFC tag and respond to it accordingly. It can also write data to the NFC tag if required.

Use Cases for Web NFC API

Web NFC API has several use cases that make it a necessary technology for web applications. Some of them are as follows:

Building contactless payment systems.

Smart posters and advertising interactions.

Access control and authentication.

IoT device management.

Browser Support for Web NFC API

Web NFC API is available in most of the modern-day web browsers, such as Google Chrome, Mozilla Firefox, Safari, and Microsoft Edge. Let’s take a look at how each of these browsers supports Web NFC API.

Google Chrome and Web NFC API

Google Chrome first introduced the Web NFC API in version 81 for Android and Windows devices. It is available as an experimental feature that needs to be enabled manually. To enable the feature, the user needs to go to the ‘chrome://flags’ page and search for ‘WebNFCAPI’. Users can then enable this feature to access Web NFC API.

Mozilla Firefox and Web NFC API

Mozilla Firefox announced support for Web NFC API in version 72 and above. As of Firefox version 89, Web NFC API is enabled by default for users on desktop and Android devices. However, users on iOS devices will not have access to Web NFC API as iOS devices do not have support for NFC hardware.

Safari and Web NFC API

Safari has announced support for Web NFC API in its iOS 14. NFC tags can be read and written using Safari on iPhones that have built-in NFC hardware, such as iPhone 7 and later.

Microsoft Edge and Web NFC API

Microsoft Edge announced support for Web NFC API in version 89. Web NFC API is enabled by default for desktop users but not yet supported on mobile devices.

Implementing Web NFC API in Web Applications

Implementing Web NFC API in web applications is not a complicated task. Developers need to follow a few simple steps to get started.

Basic Web NFC API Implementation

The basic implementation of Web NFC API involves registering an event listener that listens for a reading event. In this event listener, developers fetch the records from the NFC tag and show them to the user. Below is a code snippet that shows a simple implementation of the Web NFC API.

navigator.permissions.query({name: "nfc"}).then(permissionStatus => { if (permissionStatus.state === "granted") { // add an event listener // for the nfcfound event nfc.addEventListener('reading', ({message, serialNumber}) => { console.log(`Found NFC tag with serial number: ${serialNumber} and data: ${message.url}`); }); } });

Reading NFC Tags with Web NFC API

Reading NFC tags with Web NFC API is a simple process. When an NFC tag is detected, it sends a ‘reading’ event to the application. Developers can then fetch the records from the NFC tag and show them to the user. Below is a code snippet that shows how to read NFC data using Web NFC API.

// add an event listener for the nfcfound eventnfc.addEventListener('reading', ({message, serialNumber}) => { console.log(`NFC tag with serial number: ${serialNumber} and data: ${message.url}`);});

Writing NFC Tags with Web NFC API

The Web NFC API also allows developers to write data to NFC tags. The process involves creating an NDEF message containing the data and writing it to the NFC tag. Once the data is written successfully, the ‘writeend’ event is sent to the application. Below is a code snippet that shows how to write data to an NFC tag.

// Create an NDEF messageconst message = [ new window.NDEFRecord.createTextRecord("Hello, world!"),];nfc.write(message).then(() => { console.log('NFC tag has been written');}).catch((err) => { console.error(`Error while writing NFC tag: ${err}`);});

Security Considerations for Web NFC API

Developers should be mindful of the security risks while implementing Web NFC API in their applications. NFC tags can potentially carry sensitive information, and therefore, it is essential to ensure that the data is encrypted and safe. Developers should also be wary of ‘clickjacking’ attacks and ensure that the user is aware of the NFC interactions. In addition, security best practices like CORS should be followed to prevent cross-site scripting attacks.

Real-World Applications of Web NFC API

Web NFC API has several real-world applications that make it a necessary technology for web developers. Let’s take a look at some of them.

Contactless Payments

Web NFC API is being widely used in contactless payment systems, enabling users to make payments using their smartphones. This technology eliminates the need for users to carry cash or cards, making the payment process more convenient and seamless.

Smart Posters and Advertising

Web NFC API also enables smart posters and advertising interactions. These interactions allow users to interact with posters and advertisements to receive further information or special offers.

Access Control and Authentication

Web NFC API can also be used for access control and authentication purposes, allowing users to access restricted areas or sensitive information by tapping their phones. This technology is useful for organizations that require secure access to certain areas or information.

IoT Device Management

Web NFC API can be used for IoT device management, enabling users to perform operations like device configuration, firmware updates, and data retrieval. This technology simplifies the management process, making it more efficient and cost-effective.

To conclude, Web NFC API is a technology that simplifies the use of NFC in web applications. It enables seamless data transfer between NFC tags and web applications, eliminating the need for external applications. This technology has several real-world applications, including contactless payments, smart posters, access control, and IoT device management. Developers should be mindful of the security risks when implementing Web NFC API in their applications and follow security best practices to ensure the safety of user data.

Let's set you up !

Working on the web!

Student Tips

Startup Tools

Browser Glossary

Browser Tips

Web NFC - interacting with NFC tags from a browser

What is Web NFC ? 

Web NFC provides the ability for users to interact with NFC tags via a browser. This is a significant development and has the potential to change both how and where NFC tags are used. 

Web NFC Background

As most readers will know, reading an NFC tag from a mobile phone is typically done in two ways. With the latest iPhones (Xs, Xr, 11) or almost any Android phone, it's possible to simply wave the phone over an encoded tag to, for example, launch a website. The second method is to use an App. In which case, the App is opened first and then the tag can be scanned or encoded. 

In the first instance, where the phone scans the tag without an App, then the tag is always simply just 'read'. No encoding is possible with this method. To encode tags, an App is always required. Additionally, an App is always required to access a NFC tag's UID (the 7 byte unique ID locked onto the tag during manufacture). 

Web NFC changes this by allowing NFC tags to be scanned and written directly from a browser . This means that no additional Apps need to be downloaded to read an NFC tag, write to an NFC tag or access the UID. 

Why this is useful

We can see a number of powerful use cases for this but two of the most important are user experience and ease of development. The ability to add NFC tag interaction to existing websites can be completed with a few lines of code. No requirement for complex App development, testing or messing about. The technology also allows access of the tag UID, which can be used as an additional level of authentication and identification. In fact, in combination with the NTAG424 authentication chip , users can access a website, scan an NFC tag and get authentication of a product or item without any additional downloads. 

What it can't do

At the moment, the scope for the WebNFC project is limited. While it's possible to write NFC tags, it's not possible to lock them - which might limit the benefits of being able to write to the tags. However, with access to the tag UID, in location tag deployment via the browser can still be undertaken as the UID cannot be overwritten. 

>>Update : As of Chrome 100 on Android, it is now possible to lock NFC tags as well as encode. 

Using Web NFC

Right now, it's not in full release. At the time of writing, the current version of Chrome for Android (81) has the technology built in but only under development registration. The current plan is to build the tech into release 84. However, clearly, this technology can only currently be used on Android phones and therefore widespread use of the tech is not likely to happen any time soon. 

Without Apple iPhone support, it would be difficult to build a consumer based application around it. But, if Apple did adopt the tech, it might solve one of the signicant barriers on the older iPhone 7 and 8 which currently require an App download to read a tag. By allowing NFC tag scan from a browser, users can have an easier, more steamlined experience without the hassle of having to download an App to scan a tag. 

Regardless, Seritag think that the tech has a substantial appeal to companies with internal intranets, websites, web applications and so on that can see use cases for NFC but don't want the effort of App development. 

More information

Seritag will be producing a video in the next few weeks for our NFC Pro Series video tutorials. More information can also be found at  https://web.dev/nfc/ . This will be an interested new technology. At the very least, developers can add NFC functionality to existing websites without having the cost and expense of developing an App. At best, the project will move forward to encompass more features and more widespread adoption. 

Latest Articles

• NFC Tutorials
• News & Blog
• Ixkio Tag Management

• Email: [email protected]
• Tel: + 44 (0) 20 3773 2791
• WhatsApp: + 44 7760 356103

This document provides a collection of use cases and usage scenarios for web pages and applications using Near Field Communication (NFC). More information about Web NFC can be found here .

This specification defines an API to manage selected NFC use cases from Web applications and pages, and to enable new use cases based on NFC technology.

Low-level I/O operations (e.g. ISO-DEP, NFC-A/B, NFC-F) and Host-based Card Emulation (HCE) are not supported within the current scope.

This document provides informative background to the Web NFC specification . Comments on the document should be filed as issues at https://github.com/w3c/web-nfc/issues .

Terminology

For NFC terminology see the Web NFC specification .

A few NFC user scenarios have been enumerated here . For the Web NFC API in particular, a few examples of intended user scenarios follow next. Some of them are not supported in the current scope.

Reading generic information in a museum

The user touches an NFC capable device to information points of works of arts in a museum, obtaining information about the exposed items. Also, by touching information points in halls, the user can get suggested itineraries, schedule and other information to the personal device for later consultation.

Reading information in administration office

In a population administration office, the user touches in information point in order to save a list of documents required for renewing a passport, and obtaining a the next queuing number for the clerk.

Updating tag information

A museum employee touches information points with a special device which can write to the museum's NFC tags in order to update (read, then write) information on them.

Sending image to another Web NFC capable device

While a user is actively interacting with web site, e.g. https://images.example.com/, and if the user taps the device with another device where another user is actively interacting with the same web site https://images.example.com/, then they can initiate sending an image from one device to the other, using the NFC connection or by handover to Bluetooth or WiFi connection. The second device may be for instance a TV set to show the picture, or a personal computer for image processing.

This use case is not supported within the current scope of the specification.

Handover to Bluetooth

NFC supports handover protocols to Bluetooth or WiFi connectivity for the purpose of larger volume data transfer. The user touches another NFC capable device, and as a result configuration data is sent for a new Bluetooth or WiFi connection, which is then established between the devices.

A related use case for gaming has been described here . Other use cases may include bulk transfer of contacts cards, photos, and other data.

Scenarios along side payment

Payment using NFC should be handled at a platform level due to security considerations and is thus not within the scope of Web NFC. On the other hand it is possible to associate the payment status with a web page in order to have secondary actions. For instance, the user buys goods in a store, and payment options include contactless payment using NFC technology.

In general, touching the device to the point of sales terminal receiver area will result in a transaction between the secure element from the device and the point of sales terminal. With Web NFC, if the user navigates to a web site before paying, there may be interaction with that site regarding the payment, e.g. the user could get points and discounts, or get delivered application or service specific data (e.g. tickets, keys, etc) to the device.

Payment to another user

The user navigates to a web site which manages seller and buyer accounts and touches the device to another device of another user. A payment can be made between the two users' accounts.

Payment for services

On an automated point of sales terminal, such as ticketing machines, the user navigates to a web site which offers the paid service. By touching the receiver area of the point of sales, the payment can be done and the ticket can be delivered electronically to the user's device.

Acknowledgments

The editors would like to express their gratitude to Jonas Sicking and Jeffrey Yasskin.

Jeff 0 Comments

Website NFC Tag Messages Meaning, and Can You Stop Them?

This article explains the meaning of a message or alert with ‘Website NFC tag’ or ‘NFC Tag Detected’, the meaning of related messages, and what to do if you want to stop those messages. They can appear on your phone and might confuse or annoy you. However, they can also be useful. To understand, use, and perhaps prevent Website NFC tag messages on your lock screen, read on!

NFC Tag Explained

‘nfc tag detected’ explained, website nfc tag meaning, how to use a website nfc tag.

Why you get a Website NFC Tag Found Apple.com Notification

Stop Website NFC Tag Notifications

A website NFC Tag is a close (near, but non-contact) communication of a website address via a physical tag with some electronic capability. If that doesn’t mean much to you or help you yet, then read on.

NFC tags are becoming more prevalent. One reason is the recent potential low cost of the tag. Because they are now cheaper, it means many more are being used. Many more people are only coming in contact with them in recent times.

Apple has used NFC for apple pay for quite some time (going as far back as 2015!).

As a sign that it is becoming more common, Apple switched on NFC tag reading automatically in one of the recent-ish iOS updates. (For more on problems relating to that, see this article .)

It seems it has confused or annoyed some people.

They can be helpful or it can be another pathway for marketers to get into your pocket – well, if you keep your phone in your pocket that is, LOL.

But seriously, what is that message “Website NFC Tag”? And what about “NFC Tag Detected”? I’ll cover NFC Tag first, then explain the meaning of those website-related messages.

Not all NFC tags are for websites. Let’s take a quick step back to explain what an NFC tag is.

Of course Wikipedia has a long and detailed explanation of NFC. If you are up for some quite technical information, see https://en.wikipedia.org/wiki/Near-field_communication .

For smartphones and NFC tags see this section of that article.

In simple terms, it is a wireless transmission method very much like Wi-Fi or Bluetooth.

Important Note: It ONLY works over a very short distance , less than 2 inches (around 4 cm). This short distance of operation is good to know; don’t worry, someone is not trying to hack you from a long way away.

It’s nice to know you don’t have to worry about that!

It is very often set up to operate automatically and different devices have one of a number possible modes of NFC operation.

Several systems use cards or tags that don’t have their own battery. They rely on the power supplied by the field generated by the NFC Tag reader. They may have a printed coil circuit that receive power a little like induction chargers for some more modern msartphones,

NFC is often used to transmit basic (or a small amount of) information. This is because of the following reason:

NFC is only able to share a small amount of information in a short time. That is, it has a (s) low data transfer rate .

This small amount of information could be enough for its own purpose, or it could be a small amount of information to make some kind of connection for a larger amount of information transfer via another method.

Are you wondering “what does NFC Tag Detected mean?”

NFC Tag Detected is what your iPhone (or other smartphone) might have at the top of the banner when it gives you a message asking whether to “Open found.apple.com link”. See further below for exactly what that specific apple website link means.

If you get a message indicating ‘NFC Tag Detected’, it means your phone (or other NFC enabled device if not a smartphone) has come within quite close range to an NFC tag. Close enough for the communication system to to flag its presence. This can be only around two inches (or a few centimeters) range, as indicated above.

Such basic information can be something like a phone number, contact details, banking details (pay by phone), or (drum-roll please…) a website address !

As explained above, NFC stands for Near-Field Communication. It is for very short distance communication between enabled devices. Devices could include your phone (if you pay via your phone then it can do it!) or a cheap tag made for NFC in a shop or business.

They can even be in the form of a sticker rather than a tag.

We have all seen those anti-theft device stickers in stores by now right? Think of something a little like that.

With this in mind, now I want to to explain what a website NFC tag is.

Downloading an entire website page or video is not practical via NFC . This is due to its quite limited communication capabilities (I mean low speed or data transfer rate).

However, sending you only the link to the website page works fine. This is because your smartphone internet browser can then do the high data transfer rate work. It just needs the website address, and then it uses the much greater capacity Wi-Fi or other broadband connection for downloading all the website code, data, images, video and such.

If you see a message appear on your phone starting with “Website NFC” it means your phone has been very close to an automatic NFC tag.

The tag has told your phone (via near-field communication) of a website address that the tag owner thinks you might like to visit. Often it relates to a product or a store website with more information for you to read or watch – if you want to .

To open a website for you would be too much like spamming, and open to misuse.

Instead, then system is designed to give you the option to open it if you approve .

Many modern phones have NFC capability. It can activate just by holding it close to the tag or sticker (in a shop for example).

Once you have the message come up, you can do the following.

You can tap the message on your phone and tap again to accept to go to the website in your browser app. For those of you with an iPhone that would mean it will probably open the site in Safari.

This can be handy because you don’t have to type anything.

In the old days, if the shop had a website you wanted to go to, you might have to type in the website address yourself. S-L-O-W. Not to mention the problems with typos. Not good.

I suppose in practice it is much like a website QR code, that you scan with your phone or QR code app, and it can take you to a website. The difference is that you do not have to open the camera or any other app to scan a website NFC tag. It is automatic.

But sometimes it seems these tag notifications can annoy or worry some people.

It is important to know you might help someone if you pay attention. Why? Read the next section.

Also Read: How to find recently added contacts on your iPhone .

Why You Get a Website NFC Tag Found-Apple.com Notification

Apple’s AirTag system uses Bluetooth and/or NFC (which by reading the above, you now know stands for Near Field Communication).

The system is designed to help someone find their Apple Air Tag, in case they can’t find their keys or lose their wallet, or EVEN THEIR PET! You get the idea.

If your NFC-enabled phone goes near to an Apple AirTag, you will get the notification “Found.Apple.Com”

By going to the website, it allows Apple’s AirTag-finding system to record that a certain tag was ‘found’ at a certain location. If it doesn’t bother you, please consider going to the site. Apple.com is regarded as a safe website.

You might really help someone find their keys , wallet, bag or whatever.

You should not get that message if your phone recognises your own AirTag. So, it comes up only for AirTags that your phone doesn’t already recognise, of it recognises the AirTag as a lost one.

It could be one from someone sitting next to you or a colleague at work or someone you walk past.

It could be that you were near someone’s gear they left behind, or their bike. Whatever someone left behind that their Apple AirTag inside.

The good news is you can turn them off! Sort of. Here is what you can do and how to do it.

Stop Website NFC Tag Notifications.

If you have an android phone.

If you have an android phone (with Chrome, for example):

Go to Settings , then

Connected Devices .

If you see an on/off toggle switch, switch it to off .

I write “if” because not all android phones have this.

If you have an iPhone

If you have an iPhone (with Chrome, Safari or other browser as default) this could help.

Has someone left their AirTag (or some other NFC tag) near you?

If you get an AirTag, you will want to register it to be associated with you. When your iPhone recognizes one that isn’t registered to you, you will get an alert. So if you have one, make sure you register it. Note if your partner has one registered but you carry it, it might explain your problem (see below). 

It could be the reason why you keep getting NFC tag notifications , as it has found a website NFC Tag and is checking if you want to open the page link in Safari.

For that example, it will be asking to open the ‘found’ subdomain of the apple.com website, as explained above.

You might get very many notifications! Annoying. (I hope Apple will understand and resolve this issue.)

It seems you can do something.

Here are a few options to try to see if it stops them. My preferred method is to manage these notifications (see further below).

Firstly, it might relate to App Clips, because the AirTag notification system is part of an in-built app, I suppose.

An App Clip is a small part of your app that’s discoverable at the moment it’s needed (hence the pop up when your phone is near an AirTag. )

To change settings, go to:

Settings > Notifications > App Clips

I’m not sure this is what is bothering most people.

If you can’t see App Clips or it doesn’t work for you, then try the next method.

Another option for these AppClips could be to disable in Screentime Settings.

• Go to Settings, then Screen time (at the end of the block starting with Notifications), Content and privacy Restrictions.
• Here tap the slider to turn on Content and privacy Restrictions, if it isn’t on already.
• Now go to Content Restrictions, App Clips, then Hit Don’t Allow.

If you find an AirTag that you can’t find the owner for, and suspect someone is trying to track you. Then feel free to open it and take out the battery!

If that’s too hard you can find an option to stop the AirTag from working to send location data to the registered owner.

Manage iPhone Notifications to Stop them

I’m not sure if website NFC tag notifications are classed like other notifications and whether you can turn them off the same way. I write this because I didn’t see an app that you can turn off notifications specifically for NFC Tags within Settings.

NOTE: NFC is included automatically by default for iPhones 11 and later. There is no app icon in the Control Center.

However, there is something you can do to try to prevent NFC notifications causing interruptions.

For most notifications, you can prevent them from appearing on the lock screen of an iPhone. This method can stop specific notifications from playing any sound, lighting up the screen, appearing on the lock screen, or presenting a banner.

These are the steps to prevent the NFC tag message on the lock screen, but rather send it to the Notification Center on an iPhone:

Step 1: When you have received a website NFC tag notification on your iPhone lock screen :

swipe left on the notification.

Step 2: Then select one of the two options below.

Deliver Quietly

Step 1: Tap Manage , then

Step 2: tap Deliver Quietly .

Turn Off Completely

To turn off completely notifications for an app, swipe left on the notification.

Step 2: tap Turn Off .

NOTE: you will want to check if this will interfere with notifications of actions you do want, like Apple Pay. It should be app specific, but make sure your check.

If you use the above method to stop Website NFC Tag notifications, it should be notification group specific. None-the-less, it is a good idea you check things like Apple Pay still work!

I have shown you what is a Website NFC tag notification, explained what NFC means, the meaning of various messages, and five ways to stop NFC Tag notifications that should be worth a try. We explained why you might get the common Found.Apple.com Tag notification.

These Tag notifications could be coming from an Apple AirTag near you, or a store NFC tag trying to send you to a website. Don’t worry, Near Field Communication is short range only. Learn more!

NFC stands for Near Field Communication. A tag near you is picked up by your phone and is offering to send you to their website. There are some things you can try to stop them, depending on your device, if that is what you want.

An NFC tag notification is your phone offering to send your browser to a website or perform some other function that the NFC is programmed to do. Your phone senses the tag and notifies you. There are some things you can try to stop them depending on your device, if that is what you want to do.

You can’t turn off NFC completely. It’s built-in to your iPhone. There are some things you can do with these notifications to affect how they appear on your iPhone lock screen. You can ‘manage’ to ‘deliver quietly’ or ‘turn off’ specific notifications, for example.

Related posts:

• How to Stop, Restart or Pause Windows 10 Automatic Updates
• How to Disconnect or Disable Airplay
• I found how to print a PDF from my iPhone directly to my printer
• Remove NFC tag reader from iPhone Control Center
• 6 Things to Keep in Mind if You’re Looking to Elevate Your Website

About The Author

Jeff (Surname withheld for family privacy) is an engineer with over 26 years experience. He first learned to program in Fortran 77 ! See the 'About Us' for more.

GAMING ?!: Have you thought of…

Recent posts.

• Network Cable tools, tips and links
• Creative Business Marketing Strategies That Can Benefit You
• How Technology Reshapes Secretary Services: A Digital Evolution
• Harnessing Innovation: Technology’s Power in Enhancing Freight Brokering
• Keep Your Digital World Running Smoothly With These Inside Tips

Computer Tech Popular Posts

• Accessories
• Apple/Mac/OSX
• Certifications
• Customization
• Data Recovery
• Flash Drive
• IT Business startup
• Surface Pro
• Uncategorized
• Web Hosting

Can’t find it in Categories? – Use Search:

Latest Comments

• test on Top 10 Mac Repair Tools
• Alan on How to Remote Control Computers Using PCHelpWare
• Anna on Clean iPhone cable or port to fix intermittent charging
• Jeff on The Best Computer Network Installation Tool Kits
• Kevin on The Best Computer Network Installation Tool Kits

Copyright © 2006 - 2024 · TheTechMentor.com · All Rights Reserved

• Terms Of Service
• Privacy Policy
• FTC Disclosure

The Chromium Projects

W3C Web NFC API implementation in Chromium

Rijubrata Bhaumik < [email protected] >

Leon Han < [email protected] >

Donna Wu < [email protected] >

Former: Alexander Shalamov < [email protected] >

Last updated: 22 Dec 2020

This document explains how W3C Web NFC API is implemented in Chromium on both renderer and browser process sides. Future work and implementation challenges are described in “Future work” section of this document.

Ed spec (8 dec 2020):, w3c web nfc api https://w3c.github.io/web-nfc/, the web nfc api enables wireless communication in close proximity between active and passive nfc devices. the means of communication are based on ndef message exchange specification. the api provides simple, yet powerful interfaces to create, read (receive) or write (send) ndef compliant messages. the ndef format was chosen to hide low level complexity and laborious handling of various nfc technology types. the nfc apis are available on android, windows (uwp), ios , chrome os and linux platforms., high level overview, the implementation of web nfc in chromium consists of two main parts:, the nfc module in blink located at third_party/blink/renderer/modules/nfc/ which contains blink js bindings for web nfc, and the browser side platform level adaptation that is located at services/device/nfc . the blink nfc module communicates with the browser adaptation through nfc mojo interface defined in nfc.mojom file and implemented by the services/device/nfc module. the browser communicates with the android nfc implementation also through nfc_provider.mojom , in order to get the nfc object associated with which either resumes or suspends nfc operation in case of webpage visibility status change. at the time of writing, only android platform is supported., other platforms provide nfc interfaces and can be supported in the future ., ndefreader is the primary interface of the web nfc. the ndefreader interface has both, write and scan methods:, - the write method is for writing data to an nfc tag. this method returns a promise, which will be resolved when the message is successfully written to an nfc tag, or rejected either when errors happened or process is aborted by setting the abortsignal in the ndefwriteoptions., - the scan method tries to read data from any nfc tag that comes within proximity. once there is some data found, an ndefreadingevent carrying the data is dispatched to the ndefreader., detailed design, blink module, android adaptation, the most important classes for android adaptation are nfcimpl , nfctaghandler and ndefmessageutils ., nfcimpl class implements mojo nfc interface and uses android platform nfc apis to access nfc functionality. nfctaghandler wraps android.nfc.tag object and provides a unified interface for reading / writing ndef messages. ndefmessageutils has few static methods for conversion between android.nfc.ndefmessage and mojom.ndefmessage objects., at runtime, the latest nfc.push operation is stored in pendingpushoperation object and as soon as the nfc tag appears within close proximity, write operation is performed. same pattern is applicable for nfc.watch operations., runtime view, ndefreader#write(), ndefreader::write() will resolve the promise if there is no error occurred and the message is written to a matched target successfully. in other cases, any errors, or the abortsignal is set during the process, it will reject the promise., ndefreader#scan(), ndefreader#scan() may trigger ndefreader#{onreading,onreadingerror}() events during the whole process. ndefreader::scan() can be called multiple times on the same reader object but there is maximum only one active at any time point., future work, security and privacy, please see the ux design for detailed information about the permission model., web nfc api can be only accessed by top-level secure browsing contexts and user permission is required to access nfc functionality. web nfc api specification addresses security and privacy topics in chapter security and privacy., [web nfc] w3c web nfc api https://w3c.github.io/web-nfc/, [active] active nfc device (phones, nfc readers, powered devices), [passive] passive nfc device (tags, smart cards, etc), [ndef] nfc data exchange format ndef definition.

This feature is not (yet) supported on your device.

The Web NFC API enables web apps to read and write to NFC tags when they are in close proximity to the device, usually 5-10 cm or 2-4 inches.

Fill in the form with your data below and write it to the NFC tag by tapping the "Write" button and holding the tag close to your device.

After that you can read the data back by tapping the "Scan" button and holding the tag close to your device.

Web NFC Sample

Available in Chrome 89+ | View on GitHub | Browse Samples

Web NFC aims to provide sites the ability to read and write to NFC tags when they are brought in close proximity to the user’s device (usually 5-10 cm, 2-4 inches). The current scope is limited to NDEF, a lightweight binary message format. Low-level I/O operations (e.g. ISO-DEP, NFC-A/B, NFC-F) and Host-based Card Emulation (HCE) are not supported within the current scope.

Live Output

Javascript snippet.