Source note · Robocall mitigation and RMD obligations
All providers with a STIR/SHAKEN implementation obligation are explicitly required to obtain an SPC token from the Policy Administrator and to present it to a STIR/SHAKEN Certificate Authority to obtain a digital certificate.
Checked 2026-09-16
all providers with a STIR/SHAKEN implementation obligation under the Commission's rules will now be explicitly required to obtain an SPC token from the Policy Administrator
- Vendor
- Federal Communications Commission
- Product
- STIR SHAKEN
- Subsystem
- SPC token and certificate
- Deployment
- all-us-voice-service-provider-networks
- Region
- united states
- Release range
- compliance from 2025-09-18
- Checked
- 2026-09-16
Sources
- Call Authentication Trust Anchor, Eighth Report and Order (FCC 24-120) — Federal Communications Commission · tier 1 standards and regulators · FCC 24-120 para 28
Cite this note
APA
WarmTransfer. (2026, September 16). Robocall mitigation and RMD obligations: source note robocall-mitigation-eight-spc-token-mandate. WarmTransfer. https://warmtransfer.net/knowledge/claims/robocall-mitigation-eight-spc-token-mandate
BibTeX
@misc{warmtransfer-claim-robocall-mitigation-eight-spc-token-mandate,
title = {Robocall mitigation and RMD obligations: source note robocall-mitigation-eight-spc-token-mandate},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/robocall-mitigation-eight-spc-token-mandate},
note = {Source note robocall-mitigation-eight-spc-token-mandate, checked 2026-09-16}
}