SPC Tokens Explained: The One Document You Can't Skip
- An SPC token ties your OCN to your specific legal entity — it’s how a certificate authority confirms you’re actually authorized to operate that OCN.
- Tokens come from iConectiv’s STI-PA token portal, not from your certificate authority.
- A token is tied to your legal entity name exactly as registered — a mismatch, even a minor one, will block certificate issuance.
- A merger, rebrand, or legal name change means you need a new token, not just an updated certificate.
- Confirm your token’s legal entity name matches your registration exactly, request a new one proactively after any name change, and keep it accessible to whoever manages renewals.
Every STIR/SHAKEN certificate request starts with the same question from your certificate authority: what's your SPC token? If you don't have a clean answer, nothing else moves forward.
What SPC Stands For
SPC stands for Service Provider Code — a code that ties a specific OCN to a specific legal entity. The SPC token is a signed, verifiable document (or more precisely, data object) asserting that your company is the authorized operator of that OCN. A certificate authority checks this token before issuing a certificate, so that certificates can't be issued for an OCN to a company that doesn't actually operate it.
Where It Comes From
SPC tokens are issued through iConectiv's STI-PA token portal, not through your certificate authority. The two are separate steps: first you register with iConectiv and obtain your token, then you present that token to your STI-CA when requesting a certificate.
The Most Common Mistake: Legal Entity Name Mismatches
The single most common reason an SPC token request gets flagged is a mismatch between the legal entity name on the token and the name your certificate authority has on file — different punctuation, a missing "LLC" or "Inc.", or an outdated name from before a rebrand. These aren't bureaucratic nitpicks; the whole point of the token is confirming identity, so even a small mismatch is treated seriously.
When You Need a New Token
If your company changes its legal name, merges with another entity, or restructures, your existing SPC token no longer accurately describes who operates the OCN. Requesting a new token — not just updating your certificate — is the right move in these situations.
Conclusion
The SPC token isn't paperwork for paperwork's sake — it's the mechanism that keeps certificates tied to the right legal entity. Get the name exactly right, keep the token where your team can find it, and request a fresh one any time your company's legal identity changes.
This article is provided for general informational purposes only and does not constitute legal or compliance advice. Consult a qualified attorney or compliance professional about your organization’s specific obligations under FCC rules and the STIR/SHAKEN framework.
Need a STIR/SHAKEN certificate?
Telonium is an approved STI-CA — request your first certificate today.