{"id":836,"date":"2026-09-17T06:10:33","date_gmt":"2026-09-17T06:10:33","guid":{"rendered":"https:\/\/microtalk.co.uk\/blog\/?p=836"},"modified":"2026-09-17T06:12:36","modified_gmt":"2026-09-17T06:12:36","slug":"carriers-know-your-customer-kyc-obligations-fcc-proposals-and-compliance-requirements","status":"publish","type":"post","link":"https:\/\/microtalk.co.uk\/blog\/carriers-know-your-customer-kyc-obligations-fcc-proposals-and-compliance-requirements\/","title":{"rendered":"Carriers’ “Know Your Customer” (KYC) Obligations \u2014 FCC Proposals and Compliance Requirements"},"content":{"rendered":"

KYC and KYUP: What Every Voice Service Provider Must Know About Customer Vetting<\/span><\/h1>\n
\n

The $4.5 Million Wake-Up Call<\/h2>\n

In February 2025, the FCC<\/span> proposed a penalty of nearly $4.5 million against a prominent voice service provider for alleged violations of the FCC<\/span>‘s Know Your Customer (KYC) rules.<\/p>\n

What did the voice provider do wrong? They failed to properly vet a customer who made roughly 1,800 prerecorded scam calls<\/a> on their first day of service before Telnyx caught the issue and shut them down.<\/p>\n

The FCC<\/span>‘s message was unmistakable: If you carry traffic for scammers, you are responsible\u2014even if you didn’t know.<\/p>\n

What Are the FCC<\/span>‘s KYC Rules?<\/h3>\n

The FCC<\/span>‘s KYC rules require voice service providers to take “affirmative, effective measures to prevent new and renewing customers” from using their networks for illegal robocalls.<\/p>\n

In plain English: Before you enable service for a business customer, you must verify who they are, what they intend to do with your network, and whether they pose a risk of generating illegal traffic.<\/p>\n

What does this mean in practice?<\/h4>\n

Carriers must implement a formal KYC program that includes:<\/p>\n

Customer Identity Verification: You must collect and verify identifying information about your customers\u2014including name, physical address, and contact information. The FCC<\/span> is also proposing to require government-issued ID numbers and alternate phone numbers.<\/p>\n

Risk Assessment: You must evaluate whether a new customer presents a risk of generating illegal robocalls. High-risk customers may require additional scrutiny.<\/p>\n

Ongoing Monitoring: KYC is not a one-time check. You must monitor customer behavior and update your risk assessments over time.<\/p>\n

Record Keeping: You must maintain records of your KYC efforts and be able to demonstrate them to the FCC<\/span> upon request.<\/p>\n

The Proposed KYC Expansion<\/h5>\n

The FCC<\/span><\/a> is not stopping with the current rules. In October 2025, the Commission proposed significant expansions to the KYC framework.<\/p>\n

Know Your Customer’s Customer (KYCC): The FCC<\/span> is formalizing a stringent new framework that requires carriers to verify not just their direct customers but also their customers’ customers. This means you must look further down the call chain to ensure that illegal traffic isn’t flowing through your network.<\/p>\n

Know Your Upstream Provider (KYUP): Similar to KYCC, this requires carriers to vet the providers they receive traffic from\u2014not just the providers they send traffic to.<\/p>\n

The Goal: The FCC<\/span> is moving toward an ecosystem built on verified, secure caller identity and strict KYC frameworks to label or quarantine foreign-originated traffic.<\/p>\n

The Enforcement Reality<\/pre>\n
The Telnyx case was a first-of-its-kind enforcement action. But it will not be the last. The FCC<\/span> has made it clear that KYC enforcement is a priority.<\/p>\n
What the FCC<\/span> is looking for:<\/p>\n
– Did the carrier have a KYC program in place?<\/p>\n
– Did the carrier actually implement that program?<\/p>\n
– Did the carrier take reasonable steps to prevent illegal traffic?<\/p>\n
– Did the carrier respond appropriately when illegal traffic was detected?<\/p>\n
What happens if you fail?<\/pre>\n
– Fines: Up to $4.5 million (and counting)<\/p>\n
– Reputation damage: Public enforcement actions are a permanent stain<\/p>\n
– Operational disruption: Investigations consume time and resources<\/p>\n
– Potential RMD removal: Severe KYC failures could lead to de-listing<\/p>\n
How to Build a Compliant KYC Program<\/pre>\n
Building a robust KYC program requires a systematic approach:<\/p>\n
Develop Written Policies: Document your KYC procedures, including customer onboarding, risk assessment, and ongoing monitoring.<\/p>\n
Train Your Team: Ensure that everyone involved in customer onboarding understands KYC requirements and how to implement them.<\/p>\n
Use Technology: Automated KYC tools can help verify customer identities, assess risks, and flag suspicious activity.<\/p>\n
Maintain Records: Keep detailed records of every KYC check you perform. The FCC<\/span> may ask to see them.<\/p>\n
Respond Quickly to Red Flags: If you detect illegal traffic on your network, act immediately. The FCC<\/span> expects prompt action.<\/p>\n
The Bottom Line<\/pre>\n
KYC is no longer a “nice-to-have” for carriers. It is a core compliance<\/span> obligation with serious consequences for failure.<\/p>\n
The Telnyx case sent a clear message: the FCC<\/span> will hold carriers accountable for the traffic they carry, regardless of whether they knowingly facilitated illegal calls.<\/p>\n
At Microtalk<\/a>, we help carriers implement robust KYC programs that meet FCC<\/span> expectations and protect against enforcement actions. Because in today’s regulatory environment, knowing your customer isn’t just good practice\u2014it’s survival.<\/p>\n
Do you know who is using your network to make calls?<\/p>\n<\/div>\n"},"excerpt":{"rendered":"
KYC and KYUP: What Every Voice Service Provider Must Know About Customer Vetting The $4.5 Million Wake-Up Call In February 2025, the FCC proposed a penalty of nearly $4.5 million against a prominent voice service provider for alleged violations of the FCC‘s Know Your Customer (KYC) rules. What did the voice provider do wrong? They […]<\/p>\n","protected":false},"author":6,"featured_media":837,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[319],"tags":[174,161,162,322,4,301],"class_list":["post-836","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fcc-compliance-for-usa-traffic","tag-business-voip","tag-call-centre","tag-contact-centre","tag-fcc-compliance","tag-microtalk","tag-wholesale-voice"],"_links":{"self":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=836"}],"version-history":[{"count":3,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/836\/revisions"}],"predecessor-version":[{"id":840,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/posts\/836\/revisions\/840"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/media\/837"}],"wp:attachment":[{"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microtalk.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}