NFC (Near Field Communication) is widely used in smartphones, access control systems, payment terminals, identification products, industrial equipment, consumer electronics and IoT devices.

From a compliance perspective, however, an NFC interface is more than simply a communication feature.

For manufacturers, the compliance chain typically looks like:

NFC implementation → 13.56 MHz RF → EMC → RF exposure → Market-specific requirements → Product documentation

NFC Forum certification can be relevant for interoperability and product certification, but it does not replace regulatory compliance.

This distinction is important when defining the actual test scope for a product.

What Is NFC?

NFC, or Near Field Communication, is a short-range wireless technology operating at 13.56 MHz.

NFC is based on inductive coupling between devices and is designed for communication over relatively short distances. Depending on the implementation, NFC can support different operating modes, including:

• Reader/Writer
• Card Emulation
• Peer-to-Peer

NFC is closely related to HF RFID because both technologies operate around 13.56 MHz and use inductive coupling. However, NFC and HF RFID should not simply be treated as identical technologies. The applicable protocol, operating mode, product architecture and regulatory requirements need to be considered.

For compliance purposes, the important question is therefore not only:

“Does the product contain NFC?”

but:

“How is the NFC functionality implemented and operated in the final product?”

NFC Certification Is Not the Same as Regulatory Compliance

One of the most important distinctions for manufacturers is the difference between NFC Forum certification and regulatory compliance.

NFC Forum certification focuses on interoperability and conformance with applicable NFC specifications.

Regulatory compliance addresses whether the radio equipment can legally be placed on the market and operated in a particular country or region.

These are separate requirements.

A product can therefore have:

• NFC Forum certification
• a certified NFC module
• successful NFC interoperability testing

and still require additional regulatory evaluation for the final product.

The regulatory requirements depend on the target market and the actual implementation.

Regulatory Standards for NFC in Europe, the USA and Canada

NFC operates at 13.56 MHz, so manufacturers need to evaluate the applicable radio and EMC requirements for each target market.

European Union

In the European Union, NFC equipment with a radio transmission function generally falls under the Radio Equipment Directive (RED) 2014/53/EU.

A key harmonised standard for NFC and other inductive short-range devices is:

ETSI EN 300 330

This standard covers Short Range Devices operating in the frequency range from 9 kHz to 25 MHz, which includes 13.56 MHz NFC applications.

For EMC, the applicable standard is typically:

ETSI EN 301 489-3

This addresses EMC requirements for Short Range Devices within its scope.

Depending on the product, additional requirements may also apply, for example for:

• electrical safety
• RF exposure
• other radio interfaces
• EMC of non-radio functions
• product-specific requirements

The exact RED test scope therefore depends on the complete product architecture rather than NFC alone.

United States

In the United States, NFC equipment is generally evaluated under the FCC rules for unlicensed radio devices, particularly 47 CFR Part 15.

For intentional radiators operating at 13.56 MHz, an important provision is:

FCC 47 CFR §15.225

This section contains the specific requirements for intentional radiators operating in the 13.553–13.567 MHz band.

Depending on the product architecture, additional FCC requirements can also apply, including requirements for:

• unintentional emissions
• conducted emissions
• radiated emissions
• RF exposure

The applicable FCC test scope therefore needs to be determined from the actual NFC transmitter, antenna, power level, enclosure and other electronics in the final product.

Canada

In Canada, NFC equipment is generally subject to ISED requirements for licence-exempt radio apparatus.

The main documents to consider include:

ISED RSS-210 — Licence-Exempt Radio Apparatus

and

ISED RSS-Gen — General Requirements for Compliance of Radio Apparatus

The applicable requirements for a 13.56 MHz NFC implementation need to be determined from the current RSS-210 provisions and the characteristics of the equipment.

As with the USA and EU, RF exposure and other requirements may also need to be evaluated depending on the product.

An important practical point is that an FCC test report should not automatically be assumed to demonstrate Canadian compliance. The applicable ISED requirements and measurement conditions need to be checked against the actual product.

NFC Reader vs. NFC Tag

The compliance approach can differ significantly depending on whether the product actively generates the RF field.

NFC Reader / Initiator

An NFC reader actively generates the electromagnetic field used to communicate with another device.

This means the RF output characteristics need to be evaluated, including aspects such as:

• operating frequency
• field strength
• modulation
• antenna configuration
• matching network
• operating modes
• duty cycle
• conducted and radiated emissions

The reader is therefore normally the more significant element from an RF compliance perspective.

NFC Tag

A passive NFC tag does not normally contain its own RF transmitter.

It obtains energy from the electromagnetic field generated by the reader and communicates by modulating the load seen by the reader.

This creates a different compliance situation from an active NFC transmitter.

However, the final product still needs to be evaluated according to its actual function and applicable market requirements.

NFC Antenna Design Is Part of the Compliance Scope

At 13.56 MHz, the antenna is a fundamental part of the NFC implementation.

Unlike many higher-frequency radio systems, NFC commonly uses a coil antenna and relies on inductive coupling.

Important design parameters include:

• coil geometry
• number of turns
• antenna dimensions
• inductance
• matching components
• resonant frequency
• Q factor
• PCB layout
• ground-plane interaction
• enclosure materials
• nearby metal
• ferrite or shielding materials

Changing the antenna can therefore change the RF characteristics of the complete system.

For example:

NFC IC → Matching Network → NFC Antenna

should be treated as an RF system rather than three independent components.

A change to the antenna or matching network can affect the final compliance assessment.

What About Pre-Certified NFC Modules?

A pre-certified NFC module can reduce development and compliance effort, but module certification does not automatically mean that the final product is compliant.

The final assessment can depend on:

• approved antenna
• antenna gain or characteristics
• matching network
• PCB layout
• enclosure
• installation configuration
• operating power
• simultaneous operation with other radios
• separation distances
• host product configuration

For example, integrating an NFC module into a metal housing can significantly change the antenna environment compared with the module’s original test configuration.

The manufacturer’s module documentation and certification conditions therefore need to be reviewed before defining the final test scope.

EMC Testing for NFC Products

NFC products can require EMC testing in addition to the specific RF measurements.

The NFC transmitter operates at 13.56 MHz, but the product may contain many other potential sources of electromagnetic emissions:

• microprocessors
• displays
• switching power supplies
• USB interfaces
• Ethernet
• Wi-Fi
• Bluetooth
• cellular modems
• DC/DC converters
• high-speed digital interfaces

The compliance assessment therefore needs to consider the complete product.

For EU products, EN 301 489-3 is particularly relevant to the radio-related EMC assessment for applicable NFC/SRD equipment.

The final EMC scope can nevertheless extend beyond the NFC interface depending on the product and applicable legislation.

RF Exposure and NFC

NFC operates at very short distances, but RF exposure requirements should not simply be ignored.

The applicable assessment depends on factors such as:

• operating power
• antenna characteristics
• intended use
• separation distance
• operating mode
• duty cycle
• simultaneous transmission with other radios

A product containing NFC together with Wi-Fi, Bluetooth or cellular connectivity may require an assessment of the combined operating conditions.

For example:

NFC + Wi-Fi + Bluetooth

can require a different exposure assessment from an NFC-only product.

The relevant exposure requirements therefore need to be determined from the actual product configuration and target market.

NFC and Other Wireless Technologies

Modern products often contain multiple wireless interfaces.

A typical product might contain:

NFC + Bluetooth + Wi-Fi + Cellular

Each radio can have its own regulatory requirements.

But the compliance assessment also needs to consider whether the radios can operate simultaneously.

This can affect:

• RF exposure
• EMC
• spurious emissions
• transmitter coexistence
• test configurations
• antenna separation
• product operating modes

This is why defining the compliance scope based only on the individual radio modules can result in an incomplete test plan.

NFC Forum Certification

The NFC Forum provides specifications and certification programs intended to support interoperability between NFC-enabled products.

This is particularly relevant for products that need to operate correctly with the wider NFC ecosystem.

However:

NFC Forum certification ≠ regulatory approval

NFC Forum certification addresses NFC technology conformance and interoperability.

Regulatory compliance addresses requirements imposed by authorities in the target market.

Manufacturers may therefore need both.

Changes to an NFC Product Can Change the Compliance Scope

A product that has already been tested can require additional evaluation after hardware or software changes.

Examples include:

• changing the NFC antenna
• changing the matching network
• changing the NFC IC
• increasing RF power
• changing the PCB layout
• changing the enclosure
• adding metal close to the antenna
• changing the operating mode
• adding Wi-Fi or Bluetooth
• changing the power supply
• changing the installation configuration
• changing the intended use or separation distance

Not every change automatically requires a complete retest.

The correct question is:

Which characteristics relevant to the original compliance assessment have changed?

This is where a structured change assessment can prevent unnecessary testing while still identifying cases where additional evaluation is required.

Typical NFC Compliance Workflow

A practical NFC compliance workflow can be structured as follows.

1. Define the product

Identify:

• product type
• intended use
• target markets
• operating environment
• installation configuration

2. Define the NFC implementation

Document:

• NFC mode
• NFC IC/module
• operating frequency
• RF power/field characteristics
• antenna
• matching network
• supported NFC functions

3. Identify the regulatory requirements

For example:

EU → RED → EN 300 330 + applicable EMC requirements

USA → FCC Part 15 → §15.225 + applicable additional requirements

Canada → ISED → RSS-210 + RSS-Gen + applicable additional requirements

4. Evaluate the complete RF architecture

Check:

• antenna
• matching
• enclosure
• PCB
• power supply
• other radios
• simultaneous transmission

5. Define the EMC scope

Identify the applicable radio and product-level EMC requirements.

6. Evaluate RF exposure

Determine whether an RF exposure assessment is required and which evaluation method applies.

7. Determine certification requirements

Separately evaluate whether NFC Forum certification or other industry-specific certification is required.

8. Prepare the technical documentation

The final compliance documentation should reflect the actual tested product configuration.

Common NFC Compliance Mistakes

Assuming NFC Forum certification is regulatory approval

It is not.

Industry certification and legal market-access requirements are separate.

Assuming 13.56 MHz automatically means the same test everywhere

It does not.

The applicable regulatory requirements differ between the EU, USA, Canada and other markets.

Treating the NFC module as the complete compliance solution

The final host product can change the RF characteristics significantly.

Ignoring the antenna

The antenna and matching network are fundamental parts of the NFC RF system.

Forgetting other radios

NFC is frequently integrated alongside Wi-Fi, Bluetooth or cellular connectivity.

Testing only the NFC function

The complete product may have additional EMC, safety and RF exposure requirements.

Retesting everything after every design change

A change assessment should first determine which compliance characteristics have actually changed.

NFC in Industrial and IoT Products

NFC is increasingly used as part of larger connected products.

A typical architecture might look like:

NFC → Microcontroller → Bluetooth/Wi-Fi → Gateway → Cloud

or:

NFC → Industrial Controller → Ethernet → IIoT Platform

In these systems, NFC may be used for:

• device commissioning
• configuration
• identification
• authentication
• service access
• parameter transfer
• maintenance
• pairing

The compliance scope should therefore consider the complete product architecture rather than treating NFC as an isolated feature.

Conclusion

NFC is a short-range wireless technology operating at 13.56 MHz, but NFC compliance is not simply a matter of checking whether the NFC protocol works.

For manufacturers, the relevant compliance chain can include:

NFC implementation → RF characteristics → Antenna → EMC → RF exposure → Regulatory requirements → Industry certification → Technical documentation

The applicable requirements also depend on the target market.

For example:

EU → RED + ETSI EN 300 330 + applicable EMC requirements

USA → FCC Part 15 + §15.225 + applicable additional requirements

Canada → ISED RSS-210 + RSS-Gen + applicable additional requirements

NFC Forum certification can address interoperability and NFC technology conformance, but it does not replace these regulatory requirements.

The key to an efficient compliance process is therefore to define the actual product configuration and regulatory scope before testing begins.

How ScopeRight Helps

ScopeRight helps manufacturers define the compliance scope of products containing radio technologies such as NFC, Bluetooth, Wi-Fi, RFID, LoRa and other wireless interfaces.

The process starts with the product configuration and identifies the relevant:

• regulatory requirements
• standards
• RF tests
• EMC tests
• RF exposure requirements
• test configurations
• documentation requirements
• estimated laboratory effort

For products with multiple wireless technologies, the assessment can also take simultaneous operation and the overall product architecture into account.

The result is a structured test plan that can be used to discuss the required testing with laboratories before the project starts.

Define the scope first. Then test what is actually required.

ScopeRight