How to Handle User Account Data When a Recycled Phone Number Is Assigned to a New User

Background: phone number 111 originally belongs to user A. After A stops using it, the carrier recycles the number and assigns it to user B.

When B logs in with WeChat and authorizes phone number 111, the system looks up the number, finds it linked to A’s primary account, and flags an "account conflict".

The system does not merge accounts automatically; it pauses the flow and hands the decision to the user.

The front‑end then displays A’s masked information—nickname, avatar, binding time, historical order count—so B can see that the number is tied to an existing account.

Option 1: Continue using the account associated with the phone number. This suits cases where the user recognizes the old account (e.g., changed WeChat but kept the same phone). The system unbinds all channel bindings from A’s account, binds B’s WeChat to it, and retains A’s points, level, free cards, and coupons. B must confirm via SMS code to prove ownership of number 111.

Option 2: Abandon the old account and create a new one. This is the proper exit for recycled‑number scenarios. After seeing A’s avatar and history, B selects this option. The system performs two actions: it unbinds 111 from A’s account (clearing A’s phone field) and creates a brand‑new primary account for B, binding 111 to it. The entire operation is fully audited.

A’s account is not lost; its points, level, and assets remain, but the account becomes phone‑less. A can later recover the account by filing an appeal or rebinding a phone number.

The core logic consists of two steps: display the conflicting account information for user judgment, and execute a complete account migration based on that judgment.