Does Matter replace radio certification (RED, FCC)?

No. Matter is an application-layer protocol that runs on IPv6 over Thread or Wi-Fi, with commissioning typically assisted by BLE. The underlying radio link still has to clear the usual regulatory regimes (RED article 3.2 in Europe, FCC Part 15 in the US) and the radio ecosystem certifications (Wi-Fi Alliance, Thread Group). CSA Matter certification sits on top, it does not substitute for any of them.

Which ecosystems actually consume Matter certification?

The major consumer smart-home ecosystems, Apple Home, Google Home, Amazon Alexa and Samsung SmartThings, refuse to commission a device whose DAC chain does not trace back to a PAA recognised by the CSA. A non-certified device cannot be added by an end user to any of these ecosystems, even if its Matter firmware is technically functional.

What is the DAC and why is it critical?

The Device Attestation Certificate is a unique X.509 certificate per device, provisioned at the factory, that cryptographically proves the device was produced by a CSA member and corresponds to a certified VID/PID pair. The DAC -> PAI -> PAA chain is verified during commissioning by the ecosystem commissioner. No valid DAC, no pairing.

What is the difference between Adopter, Participant and Promoter?

These are the three CSA membership tiers. Adopter is the lowest, enough to certify a Matter product and obtain a VID. Participant adds access to the technical working groups. Promoter grants a board seat and influences the roadmap. Annual fees scale accordingly, refer to the CSA pricing page for current amounts.

Does every Matter version bump force a recertification?

It depends on the scope of the change. Minor versions (1.1, 1.2, 1.3, etc.) typically do not trigger an automatic recertification as long as the implemented device-type remains compliant with its declared spec. A major version or a significant functional addition (new cluster, new device-type class) triggers a recertification or a partial recertification, to be assessed against the CSA test plan in force.

Is the DCL public and mandatory?

The Distributed Compliance Ledger is a public, distributed registry consulted by every commissioner. The DCL entry is the last step of the certification process, without it the product is not recognised by Matter ecosystems. It is therefore de facto mandatory for any product sold under the Matter logo.

Can any lab run the Matter test plan?

No. Tests must be executed or supervised by an Authorized Test Lab recognised by the CSA. The ATL list is published by the CSA and evolves. Running tests outside an ATL does not produce a receivable report, this is a frequent mistake on first submissions.

Can an OTA update invalidate the certification?

Yes, if it changes supported clusters, adds device-types or alters Matter behaviour substantially. The principle is the same as in other regimes, any functional change affecting conformity triggers a reassessment. Strictly defensive security patches typically do not trigger recertification but must be tracked in product documentation.

Matter certification (CSA): process, DAC and DCL

Author Hugues Orgitello Last updated 26 May 2026

Guide · Matter / CSA

Matter sits in a distinct position within the IoT certification landscape, at once an interoperability protocol, an attestation-based security scheme, and a private program operated by the Connectivity Standards Alliance (CSA, formerly the Zigbee Alliance). The most common misunderstanding treats it as a substitute for the usual radio regimes. It is not. Matter is an application layer that runs over Thread or Wi-Fi, with commissioning typically assisted by BLE, and its logo can only be applied after a CSA certification that is independent of CE marking, FCC declarations, and Wi-Fi Alliance or Thread Group certifications. This page describes the exact scope of Matter certification, the VID/PID -> DAC -> ATL -> DCL workflow, the cryptographic artefacts that must be provisioned at the factory, and the recurring pitfalls observed across the first waves of Matter 1.x products.

What Matter is, and what it is not

Matter is an application-layer protocol specified by the CSA, built on IPv6 and designed to unify consumer smart home under a common interoperability scheme. Its functional scope is deliberately narrow, controlling home equipment (lighting, plugs, thermostats, locks, sensors, blinds, etc.) from any certified ecosystem, without relying on a proprietary cloud for local interaction.

Layer	Matter	Wi-Fi	Thread	BLE
Application	Matter clusters (OnOff, LevelControl, DoorLock, etc.)	n/a	n/a	n/a
Transport	UDP/TCP over IPv6	n/a	n/a	n/a
Network	IPv6 (mDNS-SD for discovery)	IPv6	6LoWPAN/IPv6	n/a (commissioning only)
Link/PHY	n/a (underlying)	IEEE 802.11	IEEE 802.15.4	Bluetooth LE

Concretely, Matter does not define a new radio. A Matter product transmits on Wi-Fi or Thread (802.15.4), and the commissioning phase almost always uses BLE to convey the initial network credentials. The regulatory regimes applicable to those radios (RED 3.2 in the EU, FCC Part 15 in the US, radio ecosystem alliance certifications) remain fully required.

The CSA itself describes Matter as a smart-home interoperability standard, not as a replacement for existing radio regimes.

Place in the certification stack

For a Matter Wi-Fi product launched in both the EU and the US, the minimum certification stack looks like this:

Regime	Scope	Required when...
CE marking + RED	EMC, safety, spectrum, cybersecurity (3.3)	Placed on the EU market
FCC Part 15	Intentional radiators	Placed on the US market
Wi-Fi Alliance	Wi-Fi interoperability	Wi-Fi CERTIFIED logo used
Thread Group	Thread interoperability	Thread logo used and Thread feature shipped
CSA Matter	Protocol conformance + DAC	Matter logo used, commissioning by ecosystems
Ecosystem cert (Works with Apple/Google/Amazon)	Optional, strategy dependent	Specific partner programs

None of these regimes substitutes for another. Matter is an addition on top of Wi-Fi and Thread, not a replacement. See RED procedure and FCC scope for the underlying radio regimes, and Bluetooth SIG qualification for the BLE commissioning side.

CSA membership, the three tiers

The CSA is a paid-membership organisation. Three tiers structure access to the Matter program:

Adopter: minimum tier to obtain a VID, download the full specification and certify a product. Suitable for the majority of manufacturers who simply want to ship.
Participant: adds access to the technical working groups (Matter Working Group, device-type subgroups), to draft future versions and to enhanced support channels.
Promoter: holds a seat on the CSA board, influences the roadmap and strategic positioning. Reserved for major actors (Apple, Google, Amazon, Samsung, etc.).

Annual fees scale at each tier. Exact amounts evolve and must be confirmed with the CSA, the public pricing page remains the only up-to-date reference. A project budgeting Matter must include the annual membership fee on top of per-product certification fees.

The VID / PID / DAC triplet

At the core of Matter sits a cryptographic attestation scheme that proves a device was actually produced by a certified manufacturer and corresponds to a certified product. Three identifiers combine:

VID (Vendor ID): unique identifier assigned by the CSA to the manufacturer at membership. A VID covers all Matter products from that vendor.
PID (Product ID): identifier assigned by the manufacturer to each Matter product in its VID catalogue. The VID/PID pair uniquely identifies a Matter model across the entire ecosystem.
DAC (Device Attestation Certificate): X.509 certificate unique per device, signed by the manufacturer via a PAI, provisioned at the factory into the device's secure storage. The DAC carries the VID/PID and binds a physical device to a certified product.

The full attestation chain is:

DAC (per device)
  signed by PAI (Product Attestation Intermediate, per manufacturer or per product family)
    signed by PAA (Product Attestation Authority, root recognised by the CSA)

At commissioning time, the commissioner (Apple Home, Google Home, etc.) asks the device to present its DAC chain, verifies the signature up to the PAA, checks that the VID/PID matches a product listed in the DCL, and only then accepts to pair. No valid DAC, no pairing.

The DCL, public conformance registry

The Distributed Compliance Ledger is a distributed registry (technically a consortium blockchain) operated by the CSA. It holds every certified Matter product, with its VID/PID, model name, manufacturer, certified Matter version, approved firmware versions and update policies.

The DCL serves two purposes:

Public reference: any user or integrator can verify that a Matter product is actually certified. The list is browsable directly from the CSA website.
Trust source for commissioners: Apple Home, Google Home and others consult the DCL to confirm that a VID/PID presented by a device matches a listed product. It is the final check before accepting the DAC.

A DCL entry is created only after successful certification. As long as that entry does not exist, a device may technically speak Matter but will be rejected by commercial ecosystems.

Certification process, step by step

The standard path of a Matter project, from design to DCL entry:

CSA membership at the Adopter tier as a minimum. Obtain a VID.
Choose the target device-type in the Matter spec in force (light, lock, thermostat, contact sensor, etc.). Each device-type has its own dedicated test plan.
Design and implementation of the Matter stack, in practice on top of a silicon vendor SDK (NXP, Silicon Labs, Espressif, Nordic, etc.) that ships the open-source CHIP (Connected Home over IP).
Internal pre-test using chip-tool, the CSA reference tool, and the CHIP TestHarness. This phase validates the implementation against the specified clusters.
Factory provisioning: generation of PAI and DAC certificates, integration into the assembly line (HSM, secure element or equivalent encrypted storage). This step is often underestimated.
PICS (Protocol Implementation Conformance Statement): formal declaration of supported optional features. The PICS conditions the scope of the test plan executed by the lab.
Select an ATL (Authorized Test Lab) from the CSA list. Submit the product, PICS and accompanying dossier.
Execute the test plan at the ATL: device-type conformance, Matter security, commissioning interoperability, network robustness.
Submit the report to the CSA, by the ATL or the manufacturer depending on the CSA procedure in force. CSA review, possible clarification requests.
Certification decision by the CSA. Certificate issued.
Create the DCL entry with VID/PID, Matter version and approved firmware.
Place on the market with the Matter logo applied to packaging and documentation. Ecosystems can now commission the product.

Total schedule depends on device-type, team maturity and ATL availability. Exact durations vary and must be confirmed with the chosen ATL, but industrial experience puts a first-time certification at several months between the ATL engagement and the DCL entry.

Matter test categories

The Matter test plan executed at an ATL covers four major axes:

Device-type conformance: for each cluster declared in the PICS, verification that attributes, commands and events match the spec exactly. A door-lock test plan (Door Lock cluster) has nothing in common with a thermostat plan.
Matter security: verification of the DAC/PAI/PAA attestation chain, the Certification Authority Session Establishment (CASE) and Password Authenticated Session Establishment (PASE) flows, fabric management (multi-admin), and certificate rotation.
Commissioning and interoperability: testing the BLE commissioning phase (advertisement, QR code/manual pairing code, credential exchange, transfer to the target IPv6 network). Verification that the device can be commissioned by multiple commissioners (multi-fabric).
Network robustness: behaviour under Thread failures (loss of Thread Border Router, fragmentation) or Wi-Fi failures (disconnect, SSID change), rejoin after reboot, Subscription handling.

The test plan evolves with each Matter spec version. The CSA publishes up-to-date test plans for members, and any certified product is certified against a precise version of the test plan.

Matter vs Wi-Fi vs Thread vs RED/FCC, who does what

Question	Applicable regime
Does my Wi-Fi product stay within legal 2.4 GHz/5 GHz limits in Europe?	RED article 3.2 + harmonised standards
Does my Wi-Fi product stay within legal limits in the US?	FCC Part 15 + FCC tests
Is my Wi-Fi product interoperable with other Wi-Fi gear?	Wi-Fi Alliance
Is my Thread product interoperable on Thread (network formation, routing)?	Thread Group
Is my BLE qualified by the SIG for use of the Bluetooth logo?	See Bluetooth SIG qualification
Does my product speak Matter correctly and present a valid DAC?	CSA Matter
Is my product compliant with RED 3.3 cybersecurity?	RED article 3.3 + EN 18031
Can it be added to Apple Home / Google Home / SmartThings?	CSA Matter + commissioning ATL pass

Reading this table line by line is enough to dispel the most frequent confusion, each regime answers a distinct question, and none waives any other.

Recertification, the most mobile topic

The Matter spec evolves through versions (1.0, 1.1, 1.2, 1.3, etc.) at a sustained pace. CSA recertification policy seeks a balance between certified-fleet stability and incentive to evolve. The operational principles:

Minor spec versions: generally no automatic recertification of products already listed in the DCL, as long as the implemented device-type remains compliant. For each minor version the CSA publishes guidance that clarifies whether partial recertifications are required (typically when a security defect was fixed in the spec).
Major versions: policy varies with impact. A major version that modifies the security scheme (cryptographic clusters, fabric mechanics, DAC format) triggers a recertification procedure, possibly lightened for products already in the DCL.
Adding a device-type or cluster to an existing product: equivalent to certifying a new profile, the PICS changes, so the test plan changes, so partial recertification at minimum.
OTA update modifying Matter behaviour: if the OTA adds clusters, changes the supported Matter version or affects the security layer, recertification is required. If the OTA fixes a strictly defensive bug without modifying the PICS, recertification is generally not required but must be tracked in product documentation.

The practical rule: any change that would alter the product PICS triggers a recertification procedure, full or partial depending on scope.

Factory provisioning of the DAC, the industrial pitfall

The DAC is not a generic firmware artefact installable after the fact. It is an X.509 certificate unique per device, generated from an equally unique private key, and provisioned during assembly. Four industrial options coexist:

Online generation on the assembly line with a dedicated HSM, injecting the DAC into the secure element or secure storage of the SoC. Reference model for high-volume manufacturers.
Pre-provisioning by the secure element vendor (Microchip, NXP, Infineon, etc.), delivering parts already personalised with a DAC. Practical for low volumes, adds a unit cost.
Pre-provisioning by the silicon vendor when the SoC ships a proprietary secure element (typical of Espressif ESP32-H2/C6, SiLabs EFR32, Nordic nRF54). The vendor operates the PAI on the manufacturer's behalf.
Provisioning by a specialised third party (services such as Kudelski IoT keySTREAM, equivalent services). Suited to manufacturers who do not want to operate their own PKI.

Frequent mistake: thinking the DAC can be generated by the firmware on first boot. This would be incompatible with the Matter trust model, the DAC private key must exist before the device leaves the factory and must be stored in secure storage that resists extraction.

See the certification glossary for the precise definition of PAA, PAI, DAC, PICS and VID/PID.

Recurring pitfalls

The most frequent non-conformities on first Matter submissions, as reported by ATLs and community feedback:

Confusing Matter with Thread. Many teams assume a Thread Group certification is enough to speak Matter over Thread. False, both regimes are independent and both are required when Thread is used.
Confusing Matter with Wi-Fi. Symmetrically, a Wi-Fi Alliance certification grants no credit toward Matter. Most Matter-on-Wi-Fi products therefore stack Wi-Fi CERTIFIED + Matter + FCC + CE.
Forgetting the commissioning BLE. BLE is not optional on most device-types, it is used for the initial commissioning phase. Its SIG qualification and radio conformance must be treated as for any other BLE link.
DAC not provisioned at the factory. Structural defect, the product needs a full production-side rework. Best detected as early as possible in the project.
Insecure DAC storage. Storing the DAC private key in unencrypted external flash, in a production file, or worse inside the firmware image itself, is a serious defect that will be caught by the ATL.
Incomplete or contradictory PICS. The PICS must reflect actual behaviour exactly. A PICS declaring features that are not implemented, or omitting features that are, both extend the test plan and cause failures.
Lab not listed. Submitting a test report produced by a lab not on the CSA ATL list produces nothing useful, the report will be rejected. Verify the list before any engagement.
Underestimating recertification. A team that plans Matter 1.x as a "one shot" ends up recertifying at the next device-type or cluster addition, without budget. Product versioning policy must anticipate this cycle.
Confusion with ecosystem programs. Apple, Google, Amazon and Samsung each run their own partner program on top of Matter. These programs do not replace CSA certification, they add to it for manufacturers seeking reinforced commercial visibility.

Costs, what can be stated without inventing

CSA fees evolve frequently and cannot be quoted here reliably. Refer directly to the CSA pricing page for current amounts. Typical cost items in a Matter project are:

Annual CSA membership (Adopter at minimum), tiered by manufacturer revenue.
Per-product certification fees (VID/PID), invoiced by the CSA on submission.
ATL fee for executing the test plan, billed by the lab and dependent on device-type.
DAC provisioning cost (HSM, third-party PKI services, or silicon-vendor PAI program licence).
Complementary memberships if the underlying radios need their own alliances (Wi-Fi Alliance, Thread Group, Bluetooth SIG).
Partial recertifications to anticipate over the product life cycle.

For a cross-cutting view of certification budgets, see certification costs.

Operational summary

For a Matter product to actually reach commercial ecosystems, six cumulative conditions must hold:

The manufacturer is a CSA member and holds a VID.
The product has a PID assigned and a PICS rigorously aligned with its implementation.
The test plan for the Matter version and device-type has been passed at a listed ATL.
Every manufactured device carries a unique DAC, provisioned at the factory, bound to a valid PAI and to a PAA recognised by the CSA.
A DCL entry references the VID/PID with Matter version and approved firmware.
The underlying radios (Wi-Fi, Thread, BLE) are independently certified in their own regimes, and the product has cleared its radio regulatory conformance (RED in the EU, FCC in the US) plus the applicable radio ecosystem alliance certifications.

Missing any one of these conditions is enough to block commissioning at Apple, Google, Amazon or Samsung, even if the product "works" on the bench.

Sources & references

CSA Matter, overview , Connectivity Standards Alliance csa-iot.org/all-solutions/matter/
CSA certified products (Distributed Compliance Ledger) , Connectivity Standards Alliance csa-iot.org/csa-iot_products/
CSA certification program , Connectivity Standards Alliance csa-iot.org/certification/
Matter specification download request , Connectivity Standards Alliance csa-iot.org/developer-resource/specifications-download-request/
Thread Group certification , Thread Group www.threadgroup.org/
Wi-Fi Alliance certification , Wi-Fi Alliance www.wi-fi.org/certification