> [!NOTE]
> **Note:** Google recommends using the [Validator App](https://play.google.com/apps/testing/com.google.location.nearby.apps.fastpair.validator "Link to the Validator App on the Google Play Store.") for self-testing to verify your implementation. The Validator App is a self-verification tool and does not replace official 3rd Party Lab certification.

## General Process Notes

1. This process covers certification for Fast Pair (FP) and Audio switch devices.
   1. Fast Pair self-tests can be found in the [BlueTooth Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip "Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.") or [BlueTooth LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2025_Q4.zip "Link to the Fast Pair LE Audio Self-Test Report sheet.") Self-Test Report forms.
   2. Audio switch self-tests can be found in the [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_SASS_Certification_Test_Report_04302026.zip "Link to the Bluetooth Classic Audio switch Self-Test Report sheet.") or [BT LEA Audio switch](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_LEA_SASS_Certification_Test_Report_04302026.zip "Link to the LE Audio Audio switch Self-Test Report sheet.") Self-Test Report forms.
2. Devices implementing LE Audio must be certified for Fast Pair version 3.1.
3. Devices implementing Audio switch must be also be certified for Fast Pair version 3.2.
   1. This includes devices implementing Audio switch over LE Audio.
4. Devices that implemented Fast Pair 2.0 or 3.1 don't need to support or certify Audio switch.
5. OEMs are expected to interface with their preferred System Integrator (SI) or SoC Partner for the majority of the process.
   1. See [SI Roles and Responsibilities](https://developers.google.com/nearby/fast-pair/system-integrator-roles-and-responsibilities "Link to the Roles and Responsibilities page.") for more details.
6. OEMs should start Fast Pair and Audio switch certification around Product Verification Testing (PVT).
7. Contact your SI or SoC partner, with technical, scheduling, or process questions.

## The Certification Process

> [!NOTE]
> **Note:** Ensure you have created a [business proposal](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform "Link to the Business Proposal submission form.") and [model ID](https://developers.google.com/nearby/fast-pair/specifications/service/modelregistration#CreateModelId "How to register a Fast Pair Model ID.") for your project prior to certification.

### Preparing for Certification via Self Testing:

1. OEM: follow the testing preparation provisions defined in the respective specification pages.
   1. Details for the Fast Pair specification are found on the [Fast Pair specification page](https://developers.google.com/nearby/fast-pair/specifications/introduction "Link to the FP Specification.").
   2. Details for the Audio switch specification are found on the [Audio switch specification page](https://developers.google.com/nearby/fast-pair/specifications/extensions/sass "Link to the Audio switch specification.").
   3. Details for the LE Audio specification are found on the [LE Audio specification page](https://developers.google.com/nearby/fast-pair/specifications/bledevice "Link to the LE Audio specification for FP.").
   4. Your SI or SoC Partner may need to enable these features.
2. OEM: run the [Fast Pair Validator](https://play.google.com/apps/testing/com.google.location.nearby.apps.fastpair.validator "Link to the Validator App on the Google Play Store.") to ensure the implementation is
   correct and meets the certification criteria.

   1. Additional documentation on how to use the validator can be found in the [Validator App Help Guide](https://developers.google.com/nearby/fast-pair/audio-switch-validator-app-user-manual "Link to the Validator App User Manual.").
   2. The tests required to complete the Self-Test Report depend on the Fast Pair versionbeing implemented, as shown in this table:

   ### Classic with A2DP+HPF

   | Test Name | FP V2.0 | FP V3.1 | FP V3.2 | FP V3.3 | Optional |
   |---|---|---|---|---|---|
   | Calibration | Yes | Yes | Yes | Yes |   |
   | End-to-End Integration | Yes | Yes | Yes | Yes |   |
   | Auto Pairing Test |   |   | Yes | Yes |   |
   | Auto Subsequent Pairing Test |   |   | Yes | Yes |   |
   | Distance 0.3 Meter |   |   |   |   | Yes |
   | Distance 1.2 Meter |   |   |   |   | Yes |
   | Distance 2.0 Meter |   |   |   |   | Yes |
   | Battery Notification Verification |   |   |   |   | Yes |
   | All other tests |   |   |   |   | Yes |

   ### BLE with Data Only

   | Test Name | FP V3.1 | FP V3.2 | FP V3.3 | Optional |
   |---|---|---|---|---|
   | Calibration | Yes | Yes | Yes |   |
   | End-to-End Integration | Yes | Yes |   |   |
   | Auto Pairing Test |   | Yes |   |   |
   | Auto Subsequent Pairing Test |   | Yes |   |   |
   | Integration with Seeker Support BLE spec Audio Connection |   |   | Yes |   |
   | Auto Pairing Test with Seeker Support BLE and LE Audio Connection |   |   | Yes |   |
   | Auto Subsequent Pairing Test with Seeker Support BLE and LE Audio Connection |   |   | Yes |   |
   | All other tests |   |   |   | Yes |

   ### BLE with LE Audio

   | Test Name | FP V3.1 | FP V3.2 | FP V3.3 | Optional |
   |---|---|---|---|---|
   | Calibration | Yes | Yes | Yes |   |
   | End-to-End Integration | Yes | Yes |   |   |
   | Auto Pairing Test |   | Yes |   |   |
   | Auto Subsequent Pairing Test |   | Yes |   |   |
   | Integration with Seeker not Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Integration with Seeker Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Auto Pairing Test with not Seeker Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Auto Pairing Test with Seeker Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Auto Subsequent Pairing Test with Seeker not Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Auto Subsequent Pairing Test with Seeker Support BLE Spec and Classic Profile Connection |   |   | Yes |   |
   | Common Audio Service UUID Verification |   |   | Yes |   |
   | Advertise Address Verification |   |   | Yes |   |
   | All other tests |   |   |   | Yes |

3. OEM: test according to the
   [Fast Pair certification guidelines](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline "Link to the Fast Pair Certification Guidelines page.") and
   [Audio switch certification guidelines](https://developers.google.com/nearby/fast-pair/audio-switch-certification-guideline "Link to the Audo switch Certification Process page.") templates.

   1. Fast Pair self-tests can be found in either the [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip "Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.") or [BT LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2025_Q4.zip "Link to the Fast Pair LE Audio Self-Test Report sheet.") Self-Test Report forms.
   2. Audio switch self-tests can be found in either the [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_SASS_Certification_Test_Report_04302026.zip "Link to the Bluetooth Classic Audio switch Self-Test Report sheet.") or [BT LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_LEA_SASS_Certification_Test_Report_04302026.zip "Link to the LE Audio Audio switch Self-Test Report sheet.") Self-Test Report forms.

### Submitting for Official Lab Certification:

1. OEM: request assistance for creating the Technical Proposal (TP) from your SoC or SI Partner.
2. SI Partner (only): create a TP tracking bug in the appropriate Buganizer.
   1. OEM: Contact [the Fast Pair support group](mailto:fast-pair-integrations@google.com "MailTo link for the Support group.") if you don't work with an SI Partner and need a Technical Account Manager (TAM).
3. OEM: submit Self-Test Reports for the specifications you are certifying ( [Fast Pair BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip "Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.") or [FP BT LEA](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2025_Q4.zip "Link to the Fast Pair LE Audio Self-Test Report sheet."), [Audio switch BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_SASS_Certification_Test_Report_04302026.zip "Link to the Bluetooth Classic Audio switch Self-Test Report sheet.") or [Audio switch LEA](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_LEA_SASS_Certification_Test_Report_04302026.zip "Link to the LE Audio Audio switch Self-Test Report sheet.")) to your SI or SoC partner.
4. Google: review and verify TP tracking bug.
   1. See [SI Roles and Responsibilities](https://developers.google.com/nearby/fast-pair/system-integrator-roles-and-responsibilities "Link to the Roles and Responsibilities page.") for more details.
5. Google: validate the Self-Test Reports provided by the OEM.
   1. OEM: resolve any issues found in the Self-Test Reports.
6. OEM: complete the [certification application form](https://docs.google.com/forms/d/e/1FAIpQLScYDjb7qghl-jJWghyA9gll1pl79R9eEz9sHWF7w0uE8zRiZA/viewform "Link to the Certification Application form.").
7. OEM: prepare 3 samples for QA testing.
   1. See [shipping guidelines](https://developers.google.com/nearby/fast-pair/shipping-devices-to-3pl "Link to the page for shipping devices to 3rd Party Labs.") for detailed instructions.
8. Google: create a corresponding Certification Request ticket in Buganizer.
9. Google: provide a lab certification ticket ID for official testing to the OEM or SI Partner.
10. Google: coordinate formal testing with the appropriate 3rd party lab (3PL).
11. Google: inform the SI or SoC partner when testing is scheduled to start.
12. SI or SoC Partner: provide the testing date to the OEM.
13. OEM: deliver your QA samples to Google or the appropriate 3PL at least one week before official certification.
    1. You must send 3 sample units for QA testing and certification.
14. 3PL: perform official certification.
15. 3PL: provide certification results to Google.
16. Google: provide certification results to the SI or SoC partner.
    1. Certification results are shared in 2-4 weeks.
       1. If passed, your device's Fast Pair and Audio switch features are turned on immediately.
          1. Device status and model ID are visible on your [Nearby console](https://developers.google.com/nearby/devices "Link to the Nearby console.").
          2. Google provides a Technical Approval Letter to the SI or SoC partner and OEM.
             1. Congratulations on passing certification!
       2. Otherwise, the Google team or your SI partners will contact you with a list of issues.
          1. Restart from the [Self-Test](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") section once the issues have been resolved.

### Post Certification:

1. When updating firmware or BlueTooth (BT) stacks, OEMs must submit Self-Test Reports matching the implemented features (Fast Pair, Audio switch, LE Audio) to their SI or SoC Partner or TAM.
   1. See the [Self-Test](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") section for details.

## Fast Pair Project Certification and Activation Process

This section outlines the current guidelines for Fast Pair project certification
and activation, ensuring a smooth product launch.

### Certification Pre-Check (Before Certification Request Submission)

**OEM Project Owner or Team Responsibility:**

You are responsible for ensuring that all configurations on the device console
are accurate. This includes:

- Project name
- Icon Image
- Feature configurations
- Firmware version
- "Public Date" (official launch date)

### Certification and Activation

**OEM Project Owner or Team Responsibility:**

- Provide sufficient information and firmware test results to facilitate a smooth certification process.
- Submit self-test reports for review to ensure no critical issues will be observed during LAB certification.
- Ensure correct project information and feature configuration to streamline LAB certification.

**Fast Pair Certification Team Responsibility:**

- Once your project successfully passes the LAB certification criteria, the Fast Pair Certification team will change the Project series status to "Active" and send an approval email.

#### IMPORTANT NOTE: Changes to 'Active' Projects

> Be aware that making any changes to an 'Active' project in the
> device console will automatically revert its status to 'Pending'.
>
> - **Production users are NOT affected** during this 'Pending' state; they will continue to use the previously active configuration.
> - The new settings are for testing only and won't be served to production users until the project is formally re-activated.
> - You **MUST** contact the Fast Pair certification team (fast-pair-integrations@google.com) to explain the changes and request project re-activation.

### Understand "Public Date" and Project Status Configuration

The "Public Date" is the official launch date set by the project owner on the
device console. The project status and visibility to public users will vary
based on this date:

- **Public Date SET AFTER Today:**

  - "Include debug results" **OFF** on the phone: The Fast Pair half-sheet **WILL NOT** appear for the project.
  - "Include debug results" **ON** on the phone: The Fast Pair half-sheet **WILL** appear with an **obfuscated** image or project name.
- **Public Date SET BEFORE Today \& Project Status "Non-Active":**

  - "Include debug results" **OFF** on the phone: The Fast Pair half-sheet **WILL NOT** appear for the project.
  - "Include debug results" **ON** on the phone: The Fast Pair half-sheet **WILL** appear with the **non-obfuscated** image or project name.
- **Public Date SET BEFORE Today \& Project Status "Active":**

  - The Project has officially been launched for public users. The Fast Pair half-sheet will appear for all users.

![Fast Pair Project Activation Process Flowchart](https://developers.google.com/static/nearby/images/fast_pair_project_activation_flowchart.png)

### Contact

For questions or re-activation requests, email:
fast-pair-integrations@google.com