NFC Forum certification: CR15, device classes, fees
NFC Forum certification is a voluntary conformance programme. It tells buyers that a phone, reader, card emulator or tag passed the Forum test cases for its device class at an Authorized Test Lab. It does not put a product on any market: the 13.56 MHz transmitter still needs RED compliance in the European Union and 47 CFR 15.225 in the United States, and payment use needs EMVCo approvals. This page is built from the NFC Forum Certification Policy (v3.3.00), Devices Requirements (v3.4.01), fee schedule and notices as of 7 October 2026, with the dates of Certification Releases 13, 14 and 15, the device classes and what each one costs to certify, and the claims about this programme that those documents contradict.
What the programme is, and what it is not
Section titled “What the programme is, and what it is not”The NFC Forum was established on 18 March 2004 by Nokia, Philips and Sony. It is a member organisation that writes the NFC technical specifications (Analog, Digital Protocol, Activity, the Type 2 to Type 5 Tag specifications, NDEF and the Record Type Definitions, LLCP, SNEP, NCI, Wireless Charging) and runs a certification programme on top of them.
Three points from the Forum documents frame everything else:
- Open to non-members. The certification page and the fee schedule both state that membership is not required for certification.
- Certification is per device class. The Devices Requirements define device classes, each a set of mandatory, optional and conditional interoperability modules. A product must implement at least one class and all mandatory modules of that class, and (section 3) shall not support modules outside the classes it claims.
- It is a supplier warranty, not a type approval. Under the Certification Policy (section 5.1), the supplier warrants that manufactured units keep meeting the requirements and would pass the tests as defined at certification. The Forum can audit, and a product that stops conforming loses its certified status.
Where each obligation comes from
Section titled “Where each obligation comes from”| Layer | Reference | Programme | Mandatory? |
|---|---|---|---|
| 13.56 MHz radio, EU | 2014/53/EU Article 3(2), EN 300 330 V2.1.1 | RED conformity assessment | Yes, to place on the EU market |
| 13.56 MHz radio, US | FCC Part 15.225 | FCC equipment authorisation | Yes, to market in the US |
| Analog, Digital Protocol, Activity, Tag Operation, NDEF | NFC Forum specifications, profiled from ISO/IEC 14443, ISO/IEC 18092, ISO/IEC 15693 and JIS X 6319-4 | NFC Forum certification | No, voluntary |
| Contactless payment acceptance and devices | EMV Contactless Books A, B and C-x, EMV Level 1 and Level 2 | EMVCo approval | Required by the payment systems, not by law |
| Secure element security | Common Criteria or payment-system programmes | Separate evaluation | Depends on the use case |
Certification Releases: the dated timeline
Section titled “Certification Releases: the dated timeline”A Certification Release (CR) fixes which Devices Requirements, test cases and approved test tools apply. The certificate names the CR and Test Release (TR) a product was certified against.
| Date | Event | Source |
|---|---|---|
| 18 March 2004 | Nokia, Philips and Sony establish the NFC Forum | Founding press release |
| September 2021 | Devices Requirements v3.0: Type 1 Tag Operation removed, specific market ecosystem classes and CCC Digital Key classes added, operating volume section added | Devices Requirements revision history |
| April 2024 | CR13 authorised for use (Devices Requirements v3.2), valid through March 2025 | CR13 page |
| January 2025 | CR14 authorised for use (Devices Requirements v3.3, which adds the WPC Ki classes) | Certification Resources |
| 17 June 2025 | NFC Release 15 announced: operating range from 0.5 cm up to 2 cm | Release 15 announcement |
| 17 October 2025 | CR15/TR15.0 launched | Certification notice |
| 1 November 2025 | Test Case License Fees per device class take effect | Certification Resources |
| 5 May 2026 | CR14 grace period set at 36 months from the CR15 launch | Certification notice |
| 7 May 2026 | Certification Policy v3.3.00 and Devices Requirements v3.4.01 (adds Parent/Child coverage for specific market classes) | Policy and Devices Requirements |
| May 2026 | CR15 page lists "authorized for use in certification: May 2026" with Devices Requirements v3.4 | CR15 page |
| 16 June 2026 | Test Case Category List v4.08 becomes the active version | Certification Resources |
| 19 August 2026 | Summary Test Report template 2.6.02 published | Certification Resources |
| 17 October 2028 | CR14 no longer accepted for new submissions | Certification notice |
| 17 October 2031 | CR14 no longer accepted for new automotive device class submissions (72 months) | Certification notice |
Two dates need care. The CR15 launch notice is dated 17 October 2025, while the CR15 release page says "May 2026", the month of Devices Requirements v3.4.01; the CR14 grace period is counted from 17 October 2025. And the Certification Policy (section 4.1.2) says a previous release gets a grace period "of up to 18 calendar months", while the 5 May 2026 notice sets 36 months for CR14. For planning, the notice is the specific decision for CR14.
What changed in Release 15: OV20
Section titled “What changed in Release 15: OV20”The headline change is the operating volume. The Forum write-up of its Release 15 webinar (5 September 2025) explains that the extended read range of 20 mm (OV20) builds on the existing 5 mm definition (OV5), obtained by allowing the magnetic field strength to rise from 14.5 to 18 A/m measured with a Class 6 antenna, plus an adjustment of load modulation amplitude reception for pollers. The Compliance Committee mandated OV20 for all new products in the Universal, Mobile, Reader and Card Emulation device classes; Tag devices may choose OV5 or OV20.
The Devices Requirements add one interoperability warning (section 3.3): a listening device with an ISO/IEC 14443-1 Class 6 antenna that supports only Comms OV5 might not interoperate with a polling device supporting Comms OV20.
Device classes, test equipment and fees
Section titled “Device classes, test equipment and fees”Devices Requirements v3.4.01 define open ecosystem classes (interoperable with each other) and specific market ecosystem classes (interoperable only within their segment). The table combines Table 2, Table 3 and Table 24 of the Devices Requirements with the Test Case License Fees in force since 1 November 2025.
| Device class | Mandatory core modules (summary) | Operating volume | Reference equipment | Test Case License Fee |
|---|---|---|---|---|
| NFC Universal Device | RF Collision Avoidance, Reader/Writer for Type 2, 3, 4A, 4B and 5 Tags, Peer Initiator and Target (PCM) | Comms OV20 | Pollers 0, 3, 6 and Listeners 1, 3, 6 | USD 5,000 |
| NFC Mobile Device | RF Collision Avoidance, Reader/Writer for Type 2 to 5 Tags, Card Emulation on Type 3, 4A and 4B Tag Platforms | Comms OV20 | Pollers 0, 3, 6 and Listeners 1, 3, 6 | USD 5,000 |
| NFC Reader Device | Reader/Writer for Type 2 to 5 Tags | Comms OV20 | Listeners 1, 3, 6 | USD 4,000 |
| NFC Card Emulation Device | At least one of Type 3, 4A, 4B Tag Platforms | Comms OV20 | Pollers 0, 3, 6 | USD 2,500 |
| NFC Tag Device (Type 2, 3, 4A, 4B or 5 Tag) | The one Tag module | Comms OV5 or OV20, plus the tag performance OV | Pollers 0, 3, 6 depending on OV | USD 1,500 |
| WLC Reader and WLC Tag Devices | Wireless Charging Poller or Listener on the stated tag types | WLC OV6 or OV7 | WLC reference coils | Not listed separately |
| CCC and ICCE Digital Key Reader and CE Devices | Subsets for car digital keys | Comms OV5 or OV20 (Reader), OV20 (CE) | As per Table 24 | Not listed separately |
| USI WLC Reader, WPC Ki Reader and Tag Devices | USI stylus charging and WPC Ki subsets | WLC OV7 (USI), not yet defined (WPC Ki) | As per Table 24 | Not listed separately |
Two consequences matter for product teams. A Reader Device is tested only against the reference listeners, while a Mobile Device carries both pollers and listeners. And the Device Test Application (DTA) must be implemented for certification testing in each mode tested (Devices Requirements section 5.12), so firmware builds for the lab need it even if production builds hide it.
Tag types that remain in the programme
Section titled “Tag types that remain in the programme”| Tag type | Technology in Devices Requirements | Can a CE device emulate it? | Test cases in CR15 |
|---|---|---|---|
| Type 1 Tag | Removed: "T1T OP interoperability module is removed" since v3.0 | No | None |
| Type 2 Tag | NFC-A (ISO/IEC 14443A equivalent) | No, Tag mode only | Type 2 Tag and Tag Operation v1.3 |
| Type 3 Tag | NFC-F (JIS X 6319-4, known as FeliCa) | Yes | Type 3 Tag and Tag Operation v1.2 |
| Type 4A and 4B Tags | NFC-A or NFC-B (ISO/IEC 14443A or B) | Yes | Type 4 Tag and Tag Operation v1.3 |
| Type 5 Tag | NFC-V (ISO/IEC 15693) | No, Tag mode only | Type 5 Tag and Tag Operation v1.2 |
Section 2 of the Devices Requirements uses NFC-A, NFC-B, NFC-F and NFC-V for NFC Forum devices and keeps the ISO/IEC and JIS names for "equivalent technologies that are not defined by the NFC Forum". Reader/Writer communication with cards whose data is not formatted according to NDEF, such as payment or transit cards, is allowed but "out of scope of the NFC Forum" (Appendix C.4.1). The CR15 test case set also still contains LLCP v1.2 and SNEP v1.0 test cases, because the Universal Device class keeps the peer modules.
Who can join, and what it costs
Section titled “Who can join, and what it costs”Membership is optional for certification. The Forum lists four levels and a non-profit variant.
| Level | Annual dues | Relevant rights |
|---|---|---|
| Adopter | None | Take part in the Certification Program, license the N-Mark and Wayfinding Marks, join interoperability test events |
| Associate | USD 2,750 (revenue under 10 million), 7,000 (10 to 100 million), 12,000 (100 million to 1 billion), 15,000 (over 1 billion) | Free access to all published specifications, non-voting Working Group participation |
| Non-profit | USD 1,750 | Associate benefits, one discounted participant at meetings |
| Principal | USD 30,000 | Voting on Technical, SIG and Compliance Committees, in-house test labs |
| Sponsor | USD 70,000, applications reviewed by the Board | Board of Directors seat |
Release 15 specifications were available at once to Associate, Principal and Sponsor members; non-members can buy individual specifications from the Forum store.
Certification fees
Section titled “Certification fees”| Item | Amount | Who pays |
|---|---|---|
| Certificate with a Summary Test Report signed by an Authorized Test Lab (Full or Inheritance path) | Free | Not applicable |
| Rename or rebrand of an already certified product | USD 250 | Applicant |
| Product certified in a first-party lab (Sponsor or Principal members only) | USD 2,500 per product, one time | Applicant |
| Test Case License Fee, Universal and Mobile Devices | USD 5,000 | Authorized Test Lab, to the Forum |
| Test Case License Fee, Reader Devices | USD 4,000 | Authorized Test Lab, to the Forum |
| Test Case License Fee, Card Emulation Devices | USD 2,500 | Authorized Test Lab, to the Forum |
| Test Case License Fee, Tag Devices | USD 1,500 | Authorized Test Lab, to the Forum |
The fee schedule is net of taxes, payable in US dollars and "subject to change without notice". Lab testing fees are set by each lab and are not published by the Forum.
The certification process
Section titled “The certification process”The Forum offers three paths: Full Certification (complete digital and analog testing), Inheritance (a product built on a certified subsystem, "generally focused on analog testing", or an OS update with no hardware change, "generally focused on digital testing") and Rename. The Full path runs as follows.
- Choose the Certification Release and device class. Select an active CR and the device class from the matching Devices Requirements.
- Fill in the ICS/IXIT. Generate the Implementation Conformance Statement and Implementation eXtra Information for Test with the Test Plan Generator (TPG). TPG access is reserved to members and to labs; for a non-member, the lab provides and validates the ICS/IXIT and generates the test plan.
- Test at an Authorized Test Lab. The lab validates the ICS/IXIT and Product Registration form, receives the device, runs the test plan with Approved Test Tools and issues a signed Summary Test Report.
- Apply online. Register the organisation once with the Certification Administrator, then submit the Product Registration form, the ICS/IXIT and the Summary Test Report through the Forum application form.
- Audit and certificate. The Certification Administrator audits the submission within 10 calendar days of a complete file and emails the certificate.
- Listing. The product appears on the public list with device class, manufacturer, product name, listing date, CR, TR and a unique ID, unless the supplier asked for confidentiality.
Authorized Test Labs
Section titled “Authorized Test Labs”On 7 October 2026 the Forum lists six Authorized Test Labs: China Academy of Information Communications Technology (Beijing), DEKRA Testing and Certification (Málaga), FIME Japan (Tokyo), IBL-Lab (St. Ingbert, Germany), SGS (Gunpo, Korea) and Telecommunications Technology Association (Korea). Each one is authorised for a stated list of device classes, so check the class before choosing. Under the Certification Policy (section 10), labs are ISO/IEC 17025 accredited first- or third-party labs, or non-accredited first-party labs that follow its principles; a listing carries the note "Tested in ISO 17025 Accredited Test Laboratory" only when all testing was done in accredited labs.
Inheritance, OS updates and renames
Section titled “Inheritance, OS updates and renames”The Certification Policy (section 9.4) allows a new product to inherit test groups from a certified implementation it integrates, as defined in the Test Case Category List. Its rules are strict: "No Analog and/or Performance testing results can be inherited", and a device with more capabilities inherits only the shared parts (a Mobile Device can inherit the reader/writer module from a Reader Device but tests its card emulation modules). An OS update without hardware change (section 9.5) needs a written self-assessment of the software changes, a signed attestation that the analog part is unchanged, and an ATL-signed report of the impacted test cases. A rename needs a Re-brand Acknowledgement Form signed by the original supplier.
Marks: N-Mark, Wayfinding and Certified Product Mark
Section titled “Marks: N-Mark, Wayfinding and Certified Product Mark”| Mark | Purpose | Licence | Tied to certification? |
|---|---|---|---|
| Wayfinding Marks (Directional, Simplified, Instructional, Charging) | Show where to tap | Free, members and non-members | No |
| N-Mark (Generation One) | Original NFC identifier, kept for backward compatibility | N-Mark License Agreement | Not stated as a condition |
| Certified Product Mark | Indicates "NFC Forum Certified Compliant" | Certified Product License Agreement | Yes, only for certified products |
The radio side: RED and FCC
Section titled “The radio side: RED and FCC”European Union. An NFC product is radio equipment under 2014/53/EU. The Commission summary list of harmonised standards (generated 7 September 2026) cites, as the harmonised standard for this radio type, ETSI EN 300 330 V2.1.1 for Article 3(2), published in OJ C 76 of 10 March 2017, with no withdrawal date. V2.1.1 is also the latest version on the ETSI delivery server. For EMC under Article 3(1)(b), the same list cites EN 301 489-3 V2.3.2 (published 15 May 2025, OJ L 2025/893), with the notice that it gives no presumption of conformity if its clause 6 is applied. If the product is internet-connected, the Article 3(3)(d)(e)(f) delegated act has applied since 1 August 2025, with EN 18031-1, -2 and -3 cited with restrictions (Decision (EU) 2025/138). See RED standards.
United States. 47 CFR 15.225 sets field strength limits by sub-band, measured at 30 m.
| Band (MHz) | Limit at 30 m | Paragraph |
|---|---|---|
| 13.553 to 13.567 | 15,848 µV/m | 15.225(a) |
| 13.410 to 13.553 and 13.567 to 13.710 | 334 µV/m | 15.225(b) |
| 13.110 to 13.410 and 13.710 to 14.010 | 106 µV/m | 15.225(c) |
| Outside 13.110 to 14.010 | General limits of 15.209 | 15.225(d) |
Carrier frequency tolerance is ±0.01 % over -20 to +50 °C and over 85 to 115 % of rated supply voltage (15.225(e)). Under 15.225(f), RF-powered tags designed to work with an authorised device may be approved with that device or authorised separately. See FCC scope.
Relationship with EMVCo
Section titled “Relationship with EMVCo”The EMV specification body, EMVCo, is collectively owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa, and lists the NFC Forum among the bodies it collaborates with. EMV Contactless refers to Books A, B and the C-x kernel books; each payment system has its own kernel specification, and EMVCo published Book C-8, a common EMV Contactless Kernel, on 5 October 2022, with its approval testing available since 16 October 2024. EMV Level 1 testing covers the communication protocol between acceptance device and payment instrument, Level 2 the kernel; EMVCo also runs a dedicated Level 1 process for NFC-enabled phones and wearables.
| Criterion | NFC Forum | EMVCo |
|---|---|---|
| Owner | Member organisation, Board of Directors with Sponsor members | American Express, Discover, JCB, Mastercard, UnionPay, Visa |
| Scope | NFC interface conformance per device class | Contact and contactless payment acceptance devices, cards, mobile form factors |
| Testing | Authorized Test Labs, Approved Test Tools | EMVCo accredited laboratories, qualified tools |
| Outcome | Certificate and public listing | Letter of Approval and listing |
| Documented link | CCC Digital Key CE certificate obtainable from an EMVCo Level 1 mobile Letter of Approval | Not applicable |
The documents of neither programme make NFC Forum certification a prerequisite for EMVCo approval. For the payment terminal route, see EMVCo and PCI PTS.
Security is out of scope
Section titled “Security is out of scope”The Devices Requirements define interoperability modules; none of them covers key storage. Card Emulation is defined per Tag Platform (Type 3, 4A, 4B), and the device class tables make no distinction between secure element and host-based emulation. Security of a secure element or of a host card emulation wallet is assessed elsewhere, for example under Common Criteria for the chip and under the payment systems' own programmes for payment credentials.
Claims the texts contradict
Section titled “Claims the texts contradict”| Common claim (including earlier versions of this page) | What the Forum and regulatory texts say |
|---|---|
| "You must join at least the Implementer tier before certifying" | There is no Implementer tier; the levels are Adopter, Associate, Principal and Sponsor, and certification "is open to non-members" |
| "NFC Forum certification licenses the N-Mark" | The N-Mark has its own licence agreement and is available to Adopter members; the Certified Product Mark is the one reserved for certified products |
| "Certification covers tag types T1 to T5" | Type 1 Tag Operation was removed in Devices Requirements v3.0 (September 2021); CR14 and CR15 test cases cover Type 2, 3, 4 and 5, with Type 4 split into 4A and 4B |
| "Card Emulation HCE and Card Emulation SE are separate declared modes" | Card Emulation is defined per Tag Platform (Type 3, 4A, 4B); the device class tables do not distinguish secure element from host emulation |
| "Peer-to-peer is deprecated by the NFC Forum" | Peer Initiator and Target in PCM are mandatory for the NFC Universal Device class in v3.4.01, and LLCP and SNEP test cases are part of CR15; only the Mobile Device class has no peer modules |
| "An integrator inherits the controller certificate if it keeps the reference antenna" | No analog or performance results can be inherited (Policy section 9.4); the Inheritance path is "generally focused on analog testing" of the end product |
| "Certification fees are paid to the Forum with the submission" | The certificate is free with an ATL-signed report; the per-class Test Case License Fee is paid by the lab; only renames (USD 250) and first-party lab certifications (USD 2,500) are billed to the applicant |
| "Declare the strict minimum of modes and tag types" | The applicant declares a device class and must implement all of its mandatory modules; a device "SHALL not support modules" outside the claimed classes |
| "NFC Forum and EMVCo cooperate through recognition agreements; a payment terminal needs both" | The only documented recognition is EMV Level 1 mobile approval leading to the CCC Digital Key CE certificate; no text makes NFC Forum certification a condition of EMVCo approval |
| "EMVCo is a joint venture of the issuers, with kernels C-1 to C-7" | EMVCo is owned by six payment systems; Book C-8 was published in 2022 and is testable since 16 October 2024 |
| "ISO/IEC 18092 is the 2013 edition" | The ISO catalogue lists ISO/IEC 18092:2023 |
Common pitfalls
Section titled “Common pitfalls”| Pitfall | How to avoid it |
|---|---|
| Planning a new reader or phone on OV5 | OV20 is mandatory for Universal, Mobile, Reader and Card Emulation classes under CR15; check the antenna and field strength early |
| Starting a CR14 project late | New CR14 submissions end on 17 October 2028 (2031 for automotive classes) |
| Changing the antenna after a module was certified | Analog results cannot be inherited, so the end product is retested on the analog side in any case; freeze the antenna before lab booking |
| Shipping lab firmware without the DTA | The Device Test Application is required for certification testing in each tested mode |
| Picking a lab that does not cover the class | Each ATL lists its authorised device classes, for example not every lab covers NFC Tag or WLC classes |
| Using the Certified Product Mark before the email | Certification is effective once the Certification Administrator gives written notice |
| Ignoring a non-conformance notice | The supplier has 180 calendar days to fix, prove conformity or stop claiming certification, or 90 days to appeal |
| Treating the certificate as market access | RED (EN 300 330 for Article 3(2)) and 47 CFR 15.225 apply independently; see RED pillar and FCC pillar |
Engineering support for NFC projects
Section titled “Engineering support for NFC projects”See also
Section titled “See also”- EMVCo and PCI PTS: payment device certification
- Qi and Qi2 certification: WPC, FCC and RED rules
- Digital Product Passport (DPP) under the ESPR
- DLNA and OCF: media + IoT interoperability
- HDMI Forum and HDMI LA: device and cable certification
- Zigbee + CSA: certification of the 802.15.4 mesh protocol
- Wi-SUN Alliance: IPv6 mesh sub-GHz certification
See also the glossary for NFC, NDEF and secure element definitions, and the guides RED standards, FCC scope and Bluetooth SIG qualification for another consortium programme.
Sources & references
- NFC Forum, Product Certification (paths, Rename fee, application steps), NFC Forum nfc-forum.org/build/certification
- NFC Forum, Certification Resources (Certification Releases, Devices Requirements, fees, STR, TCCL), NFC Forum nfc-forum.org/build/certification/resources
- NFC Forum Certification Policy, version 3.3.00 (7 May 2026), NFC Forum nfc-forum.org/uploads/Certification-Files/certification-policy-v3-3-00.pdf
- NFC Forum Devices Requirements, version 3.4.01 (7 May 2026), NFC Forum nfc-forum.org/uploads/Certification-Files/nfcforum-devicesrequirements-3-4-01.pdf
- NFC Forum, CR15/TR15.0 is now launched (17 October 2025), NFC Forum nfc-forum.org/certification_notices/cr15-tr15-0-is-now-launched/
- NFC Forum, Grace Period for CR14/TR14.0 (5 May 2026), NFC Forum nfc-forum.org/certification_notices/grace-period-for-cr14-tr14-0/
- NFC Forum, Certification Release 15, NFC Forum nfc-forum.org/certification_releases/certification-release-15/
- NFC Forum, Certification Release 13, NFC Forum nfc-forum.org/certification_releases/certification-release-13/
- NFC Forum, Labs and Testing Tools (Authorized Test Labs, Approved Test Tools), NFC Forum nfc-forum.org/build/certification/authorized-tools-labs
- NFC Forum, Branding and Marks (Wayfinding Marks, N-Mark, Certified Product Mark), NFC Forum nfc-forum.org/build/branding
- NFC Forum, Join the Forum (membership levels and annual dues), NFC Forum nfc-forum.org/engage/join
- NFC Forum Announces NFC Release 15 (17 June 2025), NFC Forum nfc-forum.org/news/2025-06-nfc-forum-announces-nfc-release-15/
- NFC Release 15 and Extended Range: Key Webinar Takeaways (5 September 2025), NFC Forum nfc-forum.org/news/2025-09-nfc-release-15-and-extended-range-key-webinar-takeaways/
- Nokia, Philips and Sony establish the Near Field Communication (NFC) Forum (press release, 18 March 2004), GlobeNewswire www.globenewswire.com/news-release/2004/03/18/1846833/0/en/Nokia-Philips-and-Sony-establish-the-Near-Field-Communication-NFC-Forum.html
- ISO/IEC 14443-3:2018, contactless proximity objects, Part 3: initialization and anticollision, ISO www.iso.org/standard/73598.html
- ISO/IEC 18092:2023, Near Field Communication Interface and Protocol 1 (NFCIP-1), ISO www.iso.org/standard/82095.html
- ETSI EN 300 330, short range devices 9 kHz to 25 MHz and inductive loop systems 9 kHz to 30 MHz, ETSI www.etsi.org/deliver/etsi_en/300300_300399/300330/
- European Commission, summary list of harmonised standards under Directive 2014/53/EU (generated 7 September 2026), European Commission webgate.ec.europa.eu/circabc-ewpp/d/d/workspace/SpacesStore/8e7cd43d-baab-4450-8f0c-7c9785e75f2c/download
- 47 CFR 15.225, operation within the band 13.110-14.010 MHz, eCFR www.ecfr.gov/current/title-47/section-15.225
- EMVCo, About us (ownership and governance), EMVCo www.emvco.com/about-us/
- EMVCo, EMV Contactless Chip, EMVCo www.emvco.com/emv-technologies/emv-contactless-chip/
- EMVCo, What are EMV Level 1 and Level 2 testing?, EMVCo www.emvco.com/knowledge-hub/what-are-emv-level-1-and-level-2-testing/
- EMVCo Launches the EMV Contactless Kernel Testing Process (16 October 2024), EMVCo www.emvco.com/news/emvco-launches-the-emv-contactless-kernel-testing-process/
Frequently asked questions
- Does NFC Forum certification replace RED or FCC radio compliance?
- No. NFC Forum certification is a voluntary programme of a private standards body and grants no market access. In the European Union a 13.56 MHz product is radio equipment under Directive 2014/53/EU, with ETSI EN 300 330 V2.1.1 as the harmonised standard cited for Article 3(2). In the United States the transmitter falls under 47 CFR 15.225. Both apply whether or not the product is NFC Forum certified.
- Do I need to be an NFC Forum member to certify a product?
- No. The Forum states that certification is open to members and non-members. Membership has four levels (Adopter, which has no annual dues, Associate, Principal and Sponsor). Membership matters for specification access, voting and, for Sponsor or Principal members, running a first-party test lab.
- How much does NFC Forum certification cost?
- The certificate itself is free when the application includes a Summary Test Report signed by an Authorized Test Lab. Since 1 November 2025 the Forum charges a Test Case License Fee per device class, paid by the lab (USD 5,000 for Universal and Mobile devices, 4,000 for Readers, 2,500 for Card Emulation devices, 1,500 for Tags). A rename costs USD 250 and a product certified in a first-party lab USD 2,500. Lab fees are extra.
- Which Certification Release should a new product use?
- CR15, launched on 17 October 2025 with Devices Requirements v3.4. It adds the 20 mm operating volume (OV20), which is mandatory for the Universal, Mobile, Reader and Card Emulation device classes. CR14 remains accepted for new submissions until 17 October 2028 (17 October 2031 for automotive device classes).
- Can a product inherit the certification of an NFC controller or module?
- Only in part. The Certification Policy lets a new product inherit digital test groups listed in the Test Case Category List, but states that no analog or performance results can be inherited. The finished product is therefore retested on the analog side by an Authorized Test Lab, which is what the Forum Inheritance path is built around.
- Does NFC Forum certification let me use the N-Mark?
- The two are separate licences. The N-Mark (now the Generation One mark, alongside the newer Wayfinding Marks) is licensed under its own N-Mark License Agreement. The mark reserved for certified products is the Certified Product Mark, licensed under a separate agreement and only for NFC Forum Certified products.
- Does NFC Forum certification cover contactless payment?
- No. Payment acceptance and payment devices are approved by EMVCo (EMV Level 1 and Level 2 testing), which is owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa. The one documented bridge runs the other way: an EMVCo Letter of Approval for an EMV Contactless Level 1 mobile product can be used to obtain the NFC Forum CCC Digital Key CE device class certificate.