The NFC Forum Specifications form a technology standard that harmonizes and extends existing contactless standards unlocking the full capabilities of NFC technology across the different contactless operating modes, peer-to-peer mode, reader/writer mode, card emulation mode.

To discover the different types of NFC Forum Specifications that enable these operating modes, click on the appropriate link below:

Logical Link Control Protocol Technical Specification

Defines an OSI layer-2 protocol to support peer-to-peer communication between two NFC-enabled devices, which is essential for any NFC applications that involve bi-directional communications. The specification defines two service types, connectionless and connection-oriented, organized into three link service classes: connectionless service only; connection-oriented service only; and both connectionless and connection-oriented service. The connectionless service offers minimal setup with no reliability or flow-control guarantees (deferring these issues to applications and to the reliability guarantees offered by ISO/IEC 18092 and ISO/IEC 14443 MAC layers). The connection-oriented service adds in-order, reliable delivery, flow-control, and session-based service layer multiplexing.

LLCP is a compact protocol, based on the industry standard IEEE 802.2, designed to support either small applications with limited data transport requirements, such as minor file transfers, or network protocols, such as OBEX and TCP/IP, which in turn provide a more robust service environment for applications. The NFC LLCP thus delivers a solid foundation for peer-to-peer applications, enhancing the basic functionality offered by ISO/IEC 18092, but without affecting the interoperability of legacy NFC applications or chipsets. Version 1.3 of the LLCP specification adds an unauthenticated secure data transport option to ensure privacy and confidentiality of messages exchanged between peer devices.

Purchase Specification

Simple NDEF Exchange Protocol Technical Specification

The Simple NDEF Exchange Protocol (SNEP) allows an application on an NFC-enabled device to exchange NFC Data Exchange Format (NDEF) messages with another NFC Forum device when operating in NFC Forum peer-to-peer mode. The protocol makes use of the Logical Link Control Protocol (LLCP) connection-oriented transport mode to provide a reliable data exchange.

Purchase Specification

The NFC Data Exchange Format Technical Specification provides a standard format for NFC application data and RTD specifications specify the format and rules for building standard record types used by NFC Forum application definitions and third parties that are based on the NDEF data format. Application level specifications are important for use cases that require an exchange of control information, such as smart posters and remote control, because message format is defined and issues that must be considered for implementation are addressed. The RTD specifications provide a way to efficiently define record formats for new applications and gives users the opportunity to create their own applications based on NFC Forum specifications.

A device level specification, the NFC Controller Interface (NCI) Technical Specification defines the interface between an NFC Controller (NFCC) and a Device Host (DH) and addresses issues that must be considered for implementation.

The specifications for the NFC Forum Type 1/2/3/4/5 Tags provide the technical information needed to implement the reader/writer and associated control functionality of the NFC device to interact with the tags. The new TNEP 1.0 Technical Specification supports the bi-directional exchange of NDEF messages based on the communication protocol used by the NFC Forum Tag devices of Type 2, 3, 4 and 5. The aim of these specifications is to define how NDEF messages are read from and written to NFC tags.

Type 1 Tag Specification

Defines how an NFC-enabled device in Reader/Writer Mode detects, reads and writes a NDEF Message on a NFC Forum Type 1 Tag. The communication with this NFC Forum Tag type is based on NFC-A Technology.

Purchase Specification

Type 2 Tag Specification

Defines how an NFC-enabled device in Reader/Writer Mode detects, reads and writes a NDEF Message on a NFC Forum Type 2 Tag. The communication with this Forum Tag type is based on NFC-A Technology.

Purchase Specification

Type 3 Tag Specification

Defines how an NFC-enabled device in Reader/Writer Mode detects, reads and writes a NDEF Message on a NFC Forum Type 3 Tag. The communication with this Forum Tag type is based on NFC-F Technology, which is compatible to the Japanese Industrial Standard (JIS) X 6319-4.

Purchase Specification

Type 4 Tag Specification

Defines how an NFC-enabled device in Reader/Writer Mode detects, reads and writes a NDEF Message on a NFC Forum Type 4 Tag. The communication with this Forum Tag type is based on the ISO Data Exchange Protocol (ISO-DEP) which is fully compatible with the ISO/IEC 14443 standard series. This protocol is either based on NFC-A or NFC-B Technology

Purchase Specification

Type 5 Tag Technical Specification

Defines how an NFC-enabled device in Reader/Writer Mode detects, reads and writes a NDEF Message on a NFC Forum Type 5 Tag. The communication with this NFC Forum Tag type is based on NFC-V Technology.

Purchase Specification

Tag NDEF Exchange Protocol (TNEP) Technical Specification

The TNEP 1.0 Technical Specification supports the bi-directional exchange of NDEF messages based on the communication protocol used by the NFC Forum Tag devices of Type 2, 3, 4 and 5. The new TNEP protocol offers a simple protocol for NFC IoT devices to exchange data between an NFC enabled phone and the IoT Device. For example, this protocol can be used to configure and read smart meter devices, to control the thermostatic radiator valve or to configure the lightning device in your smart home.

Technical specifications for Record Type Definitions (RTDs) and four specific RTDs: Text, URI, Smart Poster, and Generic Control.

NFC Record Type Definition (RTD) Technical Specification

Specifies the format and rules for building standard record types used by NFC Forum application definitions and third parties that are based on the NDEF data format. The RTD specification provides a way to efficiently define record formats for new applications and gives users the opportunity to create their own applications based on NFC Forum specifications.

NFC Text RTD Technical Specification

Provides an efficient way to store text strings in multiple languages by using the RTD mechanism and NDEF format. An example of using this specification is included in the Smart Poster RTD.

NFC URI RTD Technical Specification

Provides an efficient way to store Uniform Resource Identifiers (URI) by using the RTD mechanism and NDEF format. An example of using this specification is included in the Smart Poster RTD.

NFC Smart Poster RTD Technical Specification

Defines an NFC Forum Well Known Type to put URLs, SMSs or phone numbers on an NFC tag, or to transport them between devices. The Smart Poster RTD builds on the RTD mechanism and NDEF format and uses the URI RTD and Text RTD as building blocks.

NFC Generic Control RTD Technical Specification

NFC Forum-TS-Generic Control RTD_1.0 has been withdrawn with no replacement.

NFC Signature RTD Technical Specification

Specifies the format used when signing single or multiple NDEF records. Defines the required and optional signature RTD fields, and also provides a list of suitable signature algorithms and certificate types that can be used to create the signature. Does not define or mandate a specific PKI or certification system, or define a new algorithm for use with the Signature RTD. Specification of the certificate verification and revocation process is out of scope.

NFC Device Information RTD Technical Specification

Defines the Device Information record type which conveys fundamental model and identity identification information.

Wireless Charging allows for wireless charging of small battery-powered devices like those found in many IoT devices, This approach can help avoid the need for a separate wireless charging unit for small devices if the device includes an NFC communication interface. For example, a Bluetooth headset which includes NFC technology for pairing could also use the NFC interface for wireless charging. In this case, the NFC antenna is used to exchange the pairing information and to transfer power.

This NFC specification uses the 13.56 MHz base frequency and leverages the NFC communication link to control the power transfer. NFC technology is unique in that it allows the transfer of power to an NFC tag to enable communication by providing a constant carrier signal. The WLC specification extends this communication functionality of NFC technology to enable wireless charging. The WLC specification ensures a safe charging process between two NFC-enabled devices in either static or negotiated modes. Static mode uses standard radio frequency (RF) field strength and provides a consistent power level. Negotiated mode uses a higher RF field supporting four power transfer classes of 250, 500, 750 and 1000 milliwatts.

NFC Forum Application Documents are informative technical documents designed to promote NFC solutions in vertical markets and to foster best practices, by describing proposed solutions based on NFC Forum specifications.

Bluetooth Secure Simple Pairing Using NFC

This Application Document describes the interaction of Bluetooth technology and NFC during SSP in detail. It provides examples of both negotiated and static handover in the most feasible use cases involving the presence of both technologies. Developers will find the examples useful guides for their own work. The document has now been expanded (in June 2014) to include descriptions of how to use NFC for fast and easy Bluetooth low energy out-of-band (OOB) pairing, a key capability of Bluetooth Smart, a version of Bluetooth wireless technology that offers considerably reduced power consumption.

The updated Application Document published in June 2019 supports also Bluetooth devices implemented according the Bluetooth Core Specification 5.1 and is extended for Bluetooth Low Energy.

Download Application Document

Wi-Fi Protected Setup using NFC technology

The Wi-Fi Protected Setup using NFC technology can be found in the Wi-Fi Simple Configuration Technical Specification on the Wi-Fi Alliance website. Similar to the mechanism described in the Bluetooth Secure Simple Pairing Application Document, the mechanism of the Wi-Fi Protected Setup is based on the Connection Handover Technical Specification from the NFC Forum.

Candidate Technical Specifications

NFC Forum Candidate Technical Specifications are very mature technical specifications whose final adoption is delayed so as to allow verification of its quality, to progress on related test specifications, or the like. Candidate Technical Specifications have different licensing restrictions than adopted Technical Specifications. Companies that are not members of the NFC Forum can purchase candidate specs and offer feedback, and will be provided the final adopted spec at no charge.

Connection Handover (CH) Candidate Specification 1.5

The new CH 1.5 Candidate Specification is the first NFC Forum specification which takes advantage of the new TNEP protocol (see below). This specification version offers now the possibility to use the Negotiated Handover mechanism for a secure Bluetooth or Wi-Fi pairing, without the need to implement the LLCP protocol. That allows to implement this flexible and secure handover mechanism also for devices not offering the LLCP protocol. For example, the Negotiated Handover mechanism using the TNEP protocol can now easily be implemented for pairing of digital cameras, Bluetooth loudspeakers or internet router devices.

Non-Members: Purchase Specifications

NFC Money Transfer (NMT) Candidate Technical Specification

The NFC Money Transfer (NMT) Specification defines the functions that enable two NFC Forum Devices to transfer money – such as passing money to an individual or paying a bill in a convenience store. This specification defines Money Transfer (MT) protocols, the corresponding message structures for those protocols, and the NFC Forum Well Known Types used in those messages.

The NMT Specification gives payment service providers and consumers the opportunity to take advantage of the simple and secure NFC-based payment solutions already in use worldwide as an alternative to QR code-based solutions. The NMT solution improves the speed and efficiency of the payment process by eliminating the need for a camera or scanner used in QR code-based solutions. It provides an open framework which can be easily used by payment service providers to map their already defined data exchange for QR code-based payment solutions with NFC communication. The specification works between all NFC-enabled devices such as smartphones, readers and tags.

Non-Members: Purchase Specifications

Wireless Charging (WLC) Candidate Technical Specification

The Wireless Charging Candidate Technical Specification (WLC) makes it possible to wirelessly charge NFC-enabled devices at a power transfer rate of up to one watt. The WLC enables a single antenna in the NFC-enabled device to manage both communications and charging. This solution makes it easier and more convenient to charge low-power IoT devices such as smart watches, fitness trackers, headsets and other consumer devices.

This NFC specification uses the 13.56 MHz base frequency and leverages the NFC communication link to control the power transfer. NFC technology is unique in that it allows the transfer of power to an NFC tag to enable communication by providing a constant carrier signal. The WLC specification extends this communication functionality of NFC technology to enable wireless charging.

The WLC specification ensures a safe charging process between two NFC-enabled devices in either static or negotiated modes. Static mode uses standard radio frequency (RF) field strength and provides a consistent power level. Negotiated mode uses a higher RF field supporting four power transfer classes of 250, 500, 750 and 1000 milliwatts.