Verification Loop After Identity Verification — Fix Stuck ID Upload, Session & Cooldown Issues

Hi! A verification loop after identity verification usually means the platform accepted one step (or showed “completed”), but your current login session is still being routed back through the same security checkpoint.

We’ll keep this low-risk: no “keep trying until it works,” no risky account changes, and no sharing codes or documents with anyone outside the official flow.

To narrow it safely, tell me:
1) Which service/app is looping (Google, Microsoft, Facebook/Meta, ID.me, a bank/KYC portal, etc.)?
2) What exactly happens after you verify (does it say “Verified,” “Approved,” “Identity confirmed,” or does it just refresh)?
3) Is the loop on document upload, selfie/video, SMS/OTP, or a general “verify it’s you” prompt?

That’s helpful — “submit looks successful, then returns to the same identity page” is a common document verification loop pattern.

There are a few safe buckets we can test without guessing a “magic fix”:
• Session/token mismatch: the upload is completed, but the verification result isn’t being attached to the same login session (stale cookies, blocked third-party storage, or a stuck redirect).
• Cooldown / rate limiting: repeated submissions can trigger “try later,” and the system may temporarily stop advancing the flow.
• Upload constraints: file type/size, cropping, glare, or the browser not completing the upload handshake can silently fail and loop you back.
• Risk signals: VPN, rapid device switching, or unusual location changes can keep you in the strictest verification path.

Quick clarifiers (no changes yet): Are you on mobile or desktop? And did this start after anything changed — new phone, new browser, VPN/Private Relay, travel, or switching networks?

That combination (VPN + strict blocker + multiple retries) can absolutely produce a verify-again loop, even if your document image is fine.

Here’s how we keep it safe and avoid making cooldowns worse:

Step A — pause retries: If you’ve seen “come back later,” stop re-submitting for now. Cooldowns can stack and the system may keep routing you back to the same checkpoint.

Step B — confirm whether the upload is actually completing: Without changing account details, do one controlled test in a clean environment:

• Use a private/incognito window (or a separate browser profile).
• Temporarily disable only the blockers for that one tab (not uninstall — just for the verification page).
• Keep VPN off and stay on one stable network.

The goal is not “brute force,” it’s to see if the loop is caused by a browser/session issue or by the verification review state on the account.

Before you try anything: when it loops back, do you ever see a message like “We received your submission,” “Under review,” “Pending,” or does it instantly return to “Upload ID”?

Instant return with no “received/pending” text often points to the submission not being associated with your active session (or not fully completing). The “spinner then reset” is typical of a redirect loop caused by a blocked script, blocked storage/cookies, or a request that fails quietly.

Safe checks you can do without “messing up” your account:

1) Storage/cookie check: In the private window, make sure cookies aren’t blocked for that site. Some verification flows rely on short-lived session tokens.

2) File constraints check: Use a clear, flat photo with all corners visible and no glare. Also try a standard format (JPG/PNG) and keep the file size reasonable. (We’re not trying to re-upload a hundred times — just one clean attempt.)

3) Network consistency: Stay on one connection and keep VPN off. Switching IPs mid-flow can reset the checkpoint.

4) Device-path check: If you have access on a phone browser, try one attempt there later (not immediately if you’re getting cooldown warnings). Sometimes the mobile upload path behaves differently than desktop.

When you saw “come back later,” was it after multiple uploads in a row, or after requesting codes/verification too often?

Two different factors could be overlapping here — and it’s good you mentioned both:

• Immediate loop (technical): suggests the upload isn’t sticking to your session (blocker/cookies/session token), which prevents the system from even reaching “pending.”
• Identity consistency (policy): nickname vs legal name can matter in some identity checks. But usually you’d still see a “submitted / pending / review” status before any decision is made.

Because you’re seeing an instant reset, I’d prioritize confirming the technical side first — otherwise you can’t even get to the review stage.

One controlled test (only once): private window, VPN off, blockers paused for that page, upload a clean image, then stop. If it still snaps back instantly, that’s strong evidence of a session or flow issue rather than “your ID got rejected.”

Also, a safety note: don’t follow random “support” DMs offering to “verify for you.” In verification-loop situations, scammers often ask for codes or documents.

If the controlled test changes anything (even a new message like “pending”), tell me the exact wording — that’s a big clue.

Yes — that’s another common flavor of the problem: verification completed, but verification doesn’t “stick” across sessions.

When that happens, the usual causes are different from “upload fails”:
• Device trust not persisting: the service can’t store the “trusted device” token (blocked cookies, strict privacy settings, clearing site data, or logging in through changing IPs).
• Sign-in risk signals: rapid location changes, VPN toggles, new device fingerprints, or unusual sign-in patterns can trigger repeated challenges.
• Method mismatch: the account wants a specific verification method (authenticator, backup email, phone) but the available method is outdated or partially configured, so it keeps prompting.

Notice we’re not doing anything risky here — we’re just identifying which bucket you’re in.

For your Facebook case: we first need to see whether the submission can reach a “pending/review” state. For the Microsoft-style loop: we’d focus more on whether the browser/device is allowed to keep the “remember this device” state and whether you’re hitting a cooldown or security policy prompt.

Great question — having an “evidence pack” helps a lot, and it keeps you from repeating risky attempts.

Capture these details (no sensitive data beyond what’s shown on-screen):
1) Timestamp (date/time) of each controlled attempt (only one per session).
2) Exact page wording (e.g., “Confirm your identity,” “Verify it’s you,” “Upload ID,” “Try again later”).
3) Whether you see any status change (submitted/pending/review) or it instantly resets.
4) Environment notes: browser + private window, VPN off, network type, and whether blockers were paused for that page.
5) Any error behavior: spinner then reload, blank page, redirect back, or message about too many attempts.

That lets support differentiate a verification workflow bug from a policy review outcome or a cooldown state.

That’s the right approach. Controlled, consistent attempts reduce risk and make it easier to see what’s actually happening (session issue vs cooldown vs verification method enforcement).

If anything changes — like you finally see “submitted/pending,” a different verification method appears, or the cooldown message disappears — that’s a signal the state is moving. And if you get any unexpected messages asking you to send codes or documents outside the official site, treat that as a red flag.