0
Skip to content

FCC Rule on Use of Third Parties in Call Authentication Takes Effect in September

FCC logoThe rule permits voice service providers to use third parties, as long as they implement safeguards to protect the call authentication process.

08/21/2025 11:00 A.M.

2 minute read

Late last year, the Federal Communications Commission adopted a final rule clarifying that voice service providers may use third parties in the call authentication process.

The rule, part of the FCC’s ongoing efforts to mitigate illegal robocalls, takes effect on Sept. 18, 2025.

The rule strengthens the FCC’s caller ID authentication requirements by establishing clear practices for providers that rely on third parties to fulfill their STIR/SHAKEN implementation obligations.

STIR/SHAKEN is a framework of interconnected standards, according to the FCC, that enables phone companies to verify that calls originate from the number displayed on caller ID and is designed to prevent illegal number spoofing.  

The FCC originally adopted rules requiring voice service providers to implement the call authentication framework known as STIR/SHAKEN in 2020.

Since the adoption of the rules, the FCC has continued to expand voice service providers’ obligations with the goal of having widespread adoption of the STIR/SHAKEN framework.

The rule authorizes providers with a STIR/SHAKEN implementation obligation — generally the company providing service to the company making a call — to engage third parties to perform the technological act of digitally “signing” calls consistent with the requirements of the STIR/SHAKEN technical standards, subject to two conditions:

  • Providers with implementation obligations must make the “attestation-level” decisions for authenticating caller ID information.
  • Providers must sign all calls using their own certificate — not the certificate of a third party.

The rules also “explicitly require all providers with a STIR/SHAKEN implementation obligation to obtain a Service Provider Code token from the STIR/SHAKEN Policy Administrator and present that token to a STIR/SHAKEN Certificate Authority to obtain a digital certificate.”

Additionally, the rules outline recordkeeping requirements for third-party authentication arrangements to enable the FCC to monitor compliance with the rule and allow enforcement.

For example, providers that don’t obtain and use a Service Provider Code token and certificate must update their Robocall Mitigation Database certifications to note that they have not fully or partially implemented call authentication requirements to avoid referral to the enforcement bureau for a rule violation.

ACA International members working with voice service providers on call authentication systems should review the rule to ensure their providers know the possible requirements for third-party authentication.

ACA’s resources, including a memorandum (PDF) on robocall mitigation obligations, may be helpful in reviewing the rule with voice service providers.

Remember, subscribe to ACA Daily and Member Alerts under your My ACA Assistant profile when logged in to acainternational.org.

If you have executive leadership updates or other member news to share with ACA, contact our communications department at comm@acainternational.org. View our publications page for more information and our news submission guidelines here.

One moment please...

Share Profile

This site utilizes cookies as included in our Privacy Policy and User Agreement.