Answers
What Regulatory Requirements Apply to Launching an MVNO in the United States?
A US MVNO does not need a spectrum licence, but it is still a regulated telecommunications provider. At federal level that means registering with the FCC and USAC, contributing to the Universal Service Fund, protecting customer data under the CPNI rules, filing in the Robocall Mitigation Database if you sell voice, supporting 911 and number portability, and certifying hearing aid compatibility for the handsets you offer. Most of these carry an annual filing deadline, and several were tightened or clarified in 2026. State registration, taxes and fees sit on top of the federal layer.
This page covers federal obligations as of September 2026. It is a practical overview, not legal advice. Confirm your specific position with telecom counsel before launch.
Start with one question: who is the carrier of record?
Every obligation below attaches to the entity that provides service to the subscriber. If you launch through an MVNE or enabler that acts as carrier of record, a large part of the filing burden sits with them. If you sell service under your own name and billing relationship, it sits with you.
This is also a portability question. If you later change enabler and the new one does not act as carrier of record, the obligations move to your company. Settle it in the commercial agreement before launch, and get the split in writing for every item in the table below.
Federal obligations that apply to MVNOs
| Obligation | Rule | What it requires | Cadence |
|---|---|---|---|
| FCC and USAC registration | Form 499-A | Register as a telecommunications provider and obtain a Form 499 Filer ID. Most other filings reference it. | Before service starts |
| Universal Service Fund reporting | Form 499-A, Form 499-Q | Report telecommunications revenue so USF contributions can be assessed. | Annual, plus quarterly unless exempt |
| International service authority | Section 214 | Required to provide US-international service, including on a resold wireless basis. Domestic resale does not need a separate application. | Once, before offering international |
| CPNI protection | 47 CFR 64.2001 to 64.2011 | Customer consent tracking, staff training, authentication before disclosing call detail, breach notification to law enforcement. | Ongoing |
| CPNI officer certification | 47 CFR 64.2009(e) | Signed officer certificate with a compliance statement and complaint summary, filed in EB Docket 06-36. | Annually by 1 March |
| Robocall Mitigation Database | 47 CFR 64.6305 | Certification of STIR/SHAKEN status plus a robocall mitigation plan, including know-your-customer processes. | On launch, recertified annually by 1 March |
| Traceback response | 47 CFR 64.1200(n)(1) | Respond to traceback requests from the FCC, law enforcement or the industry traceback consortium. | Within 24 hours of each request |
| 911 access | 47 CFR 9.10 (formerly 20.18) | Provide access to basic and enhanced 911 to the extent the host network supports it, and sell only E911-capable handsets. | Ongoing |
| Hearing aid compatibility | 47 CFR 20.19, Form 855 | Offer the required share of hearing aid compatible handsets, publish handset information, certify annually. | Annually, January filing window |
| Number portability | 47 CFR Part 52 | Support port-in and port-out for your subscribers. | Ongoing |
| Lawful intercept | CALEA | Support lawful electronic surveillance. Capability usually sits in the host network, so the division of responsibility has to be documented. | Ongoing |
Robocall Mitigation Database
This is the obligation MVNOs most often miss. The FCC's position is that an MVNO reselling voice is a voice service provider under the robocall rules, even though it does not run the network that would implement STIR/SHAKEN. In February 2026 the Enforcement Bureau issued an advisory specifically to MVNOs, noting that compliance across the segment was still inconsistent.
The consequences are operational, not only financial. Other providers are prohibited from accepting traffic directly from a provider that is not in the database, so a missing or removed filing can stop your customers' calls. Inaccurate filings carry a $10,000 base forfeiture, and failing to update the filing within 10 business days of a change carries $1,000, both assessed on a continuing basis.
Your mitigation plan has to describe your know-your-customer process. For an MVNO that means subscriber onboarding and identity checks, which is where the obligation reaches into your BSS.
CPNI
CPNI covers what you know about a subscriber because they are your customer: numbers called, call times and durations, services taken, usage. The rules require you to record consent status before using CPNI, train staff and discipline misuse, authenticate customers without relying on readily available biographical data, and notify the Secret Service and FBI within seven business days of determining a breach, before telling customers.
The FCC has also adopted SIM change rules that explicitly cover resellers of wireless service, requiring secure authentication before executing a SIM change and specific staff training on SIM swap fraud. As of September 2026 the eCFR shows no compliance date set for that paragraph, so it is adopted but not yet enforceable. Build for it now. It will apply to you.
911 and hearing aid compatibility
Resellers carry a 911 obligation independent of the host network: you must give subscribers 911 and E911 access to the extent your host network supports it, and the handsets you sell must be able to pass location information to emergency services.
Hearing aid compatibility applies to MVNOs and resellers that offer handsets. Unless you qualify for a de minimis exception, the current benchmark is 85% of handset models offered. The FCC is moving the industry to a 100% compatibility standard, with manufacturers filing against it from January 2027. Check the transition date that applies to service providers before planning your device range. Eligibility for the de minimis exception does not remove the annual Form 855 filing.
What changed in 2026
- February: FCC enforcement advisory confirming MVNOs must file in the Robocall Mitigation Database and respond to traceback. First annual RMD recertification deadline on 1 March 2026.
- February: higher base forfeitures for inaccurate or out-of-date RMD filings took effect.
- May: the FCC exempted non-facilities-based providers, including resellers and MVNOs, from Disaster Information Reporting System reporting. Outage reporting obligations elsewhere are not removed by this change.
- Pending: the FCC has open proceedings on expanded know-your-customer and know-your-upstream-provider requirements for voice providers. These are proposals, not rules, as of September 2026.
State obligations
Federal law stops states from regulating wireless rates and market entry, but many states still require registration before you offer service. Requirements vary widely: some ask only for corporate contact details, others for service descriptions, geographic scope and more. On top of registration come state and local taxes, 911 fees and state universal service contributions, which usually have to be collected from subscribers and remitted on schedule. Plan state compliance per state, not as a single task.
Where the BSS fits
Almost every obligation above depends on records that live in your billing and subscriber systems rather than in a legal file:
- Form 499 revenue reporting draws on billed revenue broken down by service type.
- CPNI compliance needs consent status, authentication events and access logs per subscriber.
- Your robocall mitigation plan depends on the identity checks you run at onboarding.
- Tax and fee remittance depends on correctly rated and invoiced usage by jurisdiction.
Why platform choice matters for compliance
If those records are incomplete, the filing is only as accurate as the spreadsheet someone builds the week before the deadline. When you evaluate a platform, ask how it produces each of these records, not only whether it can bill.
TelcoEdge provides cloud-native BSS/OSS for MVNOs covering billing, subscriber and customer operations, and SIM and eSIM lifecycle.
Related Pages
FAQs
Does an MVNO need an FCC licence?
Not a spectrum licence. An MVNO uses a host network's licensed spectrum. It does need to register with the FCC and USAC, hold Section 214 authority if it offers international service, and meet the ongoing obligations above.
Does a data-only or IoT MVNO have the same obligations?
Not all of them. The Robocall Mitigation Database and traceback rules apply to providers of voice service interconnected with the public telephone network using North American numbers. A data-only offering without that kind of voice service falls outside those specific rules, though registration, USF reporting and privacy obligations can still apply. Confirm your classification with counsel, because the line depends on how the service is built and sold.
Which deadlines should go in the compliance calendar first?
1 March for CPNI certification and Robocall Mitigation Database recertification, the January window for Form 855, the annual Form 499-A plus quarterly Form 499-Q, and the 24-hour traceback response, which is not a calendar date but needs a named owner from day one.