The order of fixes: IP, device, payment, phone — what to change first
When something is off, changing everything at once destroys the evidence. This is the order that keeps the diagnosis intact.
Why order matters
Every change removes information. If you change the IP, the profile and the payment in one day, you cannot tell which one was the problem — and you have to start the account's history from zero three times.
The order
- Diagnose first, change nothing. Run the IP through the checker: is it hosting, Tor, DROP-listed, or fine? Check the environment card: does the browser agree with the IP?
- Fix the cheapest mismatch. Usually time zone, language, or WebRTC exposure. Free, fast, reversible.
- Fix the IP, if the category is wrong. Hosting or Tor addresses should be replaced with a clean ISP address.
- Fix the browser profile. Only if the IP is clean and the fingerprint is inconsistent (e.g., the profile was copied from another store).
- Fix payment last. Changing payment instruments is visible and slow to re-verify; do it only when you have a concrete reason.
The signals that justify each step
| Change | Justified when |
|---|---|
| Environment (tz/lang/WebRTC) | Mismatch with the IP country |
| IP | Address is hosting, Tor, or changed type |
| Profile | Same fingerprint used on another store |
| Payment | The platform explicitly asks, or the instrument is already flagged |
What not to do
- Do not change all four because one review happened.
- Do not switch IP mid-review.
- Do not reuse the old profile with a new IP.
Keep the record
Log the change date, the old and new value, and the verdict before/after. Our watchlist does that for the IP layer; a simple notes file does it for the rest.