Applicability
The following US mobile network operators (MNOs) impose consent and disclosure requirements on use of subscriber or device data in relevant Prove services (for example Mobile Auth in Pre-Fill for Consumers and similar flows). Contractual obligations in your MSA and carrier addenda take precedence where they differ from or extend this page.| MNO | Requirement set |
|---|---|
| Verizon | In scope |
| T-Mobile | In scope |
| AT&T | In scope; additional carrier- or agreement-specific terms may apply |
Information required for MNO approval
For T-Mobile and related approvals, Prove typically requires the following artifacts and metadata (exact package is defined in your MSA and onboarding materials):| Item | Requirement |
|---|---|
| Production URLs | Final URLs where the MNO consent language is published in Production. |
| Go-live timeline | Estimated date when consent language is live in Production. T-Mobile approval is contingent on language being live. |
| UI mock-up | Screen capture or design showing where the customer accepts carrier terms. Acceptance may use either inline copy such as by clicking Continue you agree to our T&C or a dedicated consent control (for example a checkbox). |
Required consent language
“You authorize your wireless carrier to use or share information about your account and your wireless device, if available, to<ENTERPRISE_CUSTOMER_NAME> or its service provider during your business relationship, to help identify you or your wireless device and to prevent fraud. See our Privacy Policy for how we treat your data.”
Replace <ENTERPRISE_CUSTOMER_NAME> with your legal entity or product name as agreed with Prove.
The MNOs require customers to accept carrier consent language in the customer flow before calling the endpoint in scope.
Required language placement
| Rule | Specification |
|---|---|
| Timing | The customer must accept the MNO consent language before any flow step that invokes Prove carrier-assisted checks covered by these MNO programs (for example Mobile Auth prior to downstream Pre-Fill or verification API calls). |
| Page type | MNO terms and conditions may appear on the Landing Page or the Challenge Page, per your approved UX and MSA. |
| Mobile Auth | When Mobile Auth is enabled, the MNO consent language must appear on the Landing Page and be referenced from your Terms and Conditions (or equivalent legal surface). |