US Carrier (MNO) Consent Requirements

Summary

The 3 major US MNO carriers* have set the below requirements for accessing their data for relevant Prove services. Mobile Auth℠ cannot be enabled until your MNO applications are submitted and approved by the carriers. Please reference your MSA for full details.

Note*: ATT requires additional considerations. Talk to your sales representative for more info.

Customer Pre-Requisites Prior to Prove Submission to MNOs:

• Customer must provide the Production URL(s) where MNO Consent language will live once published in Production.
• Customer must provide the estimated timeline of when consent language will be live. Note that T-Mobile will not approve until language is live.
• Customer must provide a mockup of the page where the end user accepts these terms and conditions (consumer should not be able to proceed until checking the consent box). Please see example mockup below.

Required MNO Consent Language

You authorize your wireless carrier to use or disclose information about your account and your wireless device, if available, to {Enterprise Customer Name} or its service provider for the duration of your business relationship, solely to help them identify you or your wireless device and to prevent fraud. See our Privacy Policy for how we treat your data.

Required Language Placement

The US Mobile Carriers require consumers to implicitly accept carrier consent language in the customer CX flow prior to calling the endpoint in scope. For Pre-Fill flows, we recommend inserting this language in the Terms & Conditions or Privacy Policy and implicitly referencing.

MNO Terms and Conditions should be displayed on either the Landing Page or the Challenge Page, but not on both.
See speak to your Prove representative for more detail.

If you will be implementing Mobile Auth℠, the MNO consent language should be displayed and implicitly accepted on your Landing Page (referenced in Terms and Conditions).

📘

Self-Serve

For the option, please contact your sales representative.