Error Code: M.8702 is a known Public Mobile system error that specifically triggers when an account configuration failure happens right at the final stage of processing a transaction.
It almost always happens during one of three scenarios.
A New Activation / Sign-Up: You input your payment, the payment system goes through, but the system crashes while trying to build the profile.
A "Stuck" Number Port: The activation fails because the system rejected the old provider's account number or IMEI data.
A Reactivation / Plan Change: A glitch in the payment portal locks you out when trying to submit a new transaction.
Here is the exact step-by-step approach to handle this error and clear it up.
Check Your Bank Statement First. Because this error occurs after payment info is submitted, the system often successfully charges your credit card even though it threw an error screen.
Before trying to submit the transaction again (which can double-bill you), log into your banking app. If you see a pending or posted charge from Public Mobile, stop trying to force the transaction. Your account is created on the financial backend, but a support agent needs to manually flip the flag to turn your service on. Skip straight to Step 3.
Flush the System Cache (If you weren't charged).
If your card wasn't billed, the error is likely a localized data caching glitch between your device and Public Mobile's web servers. Clear the pipes entirely:
If using a PC/Mac Web Browser: Close all tabs, clear your entire browser cache/cookies, close the browser completely, open a fresh Incognito / Private Window, and attempt the process again. If using an iPhone: Delete the Public Mobile app entirely, restart your iPhone, redownload the app from the App Store, and log back in. If using an Android: Go to Settings > Apps > Public Mobile > Storage. Tap Clear Cache and then Clear Data. Reboot your phone, reopen the app, and try again. The Porting Rule: If you are trying to transfer a phone number from an old carrier when this error hits, use your previous carrier's Account Number rather than your device's IMEI code. The IMEI tracking field is a frequent culprit for throwing the M.8702 block.
Open a Ticket with a CSA (The Ultimate Fix). What to include in your message:
Hi there, I am getting Error Code: M.8702 while trying to complete my account configuration. (State whether or not your credit card was already charged). I have already cleared my browser cookies, app cache, and tried incognito mode but the error persists. Could an agent please check the profile creation flag on the backend database switch and activate my profile manually? Thank you
Keep a close eye on the envelope icon in the top-right corner of the Public Mobile Community Forum. A real agent will message you back directly in that inbox within a few hours to confirm they have pushed your profile configuration through.
