Hi! When a Facebook account is disabled and you see identity verification failed, it usually means the review flow couldn’t accept what was submitted (or couldn’t match it to the account details), not necessarily that you “did something wrong.”

We’ll keep this risk-aware: no “spam submit,” no buying “recovery services,” and no sharing codes or documents with anyone in DMs.

To narrow it down fast, tell me:
1) What’s the exact message you see (wording matters)?
2) Is it asking you to upload an ID, do a selfie video, or confirm info like date of birth/name?
3) Did you recently change your profile name, add a nickname, or update your birthday/email/phone?

Good call to pause. Repeated ID submissions can trigger a cooldown (the “try later” message) and sometimes reduce the options you see in the flow for a while.

There are a few common buckets for “couldn’t confirm” outcomes:
• Info mismatch: ID name/birthday doesn’t closely match what’s on the account (including spelling, order, nickname vs legal name).
• Image/file issue: glare, blur, cropped edges, low resolution, unsupported format, or the ID text isn’t readable.
• Policy/risk checkpoint: the account is disabled and the system is enforcing a stricter identity proof step, sometimes with limited retries.

Quick safe questions (no changes yet):
1) Did Facebook show any hint like “doesn’t match your profile” vs “can’t read your document”?
2) Was the ID a passport/driver’s license/national ID? (Different document types can behave differently.)
3) Are you doing this on mobile, desktop, or both?

That “shortened last name” detail is a strong clue. In identity checks, even small differences can look like a mismatch, especially during a disabled account review where the system is cautious.

Before you submit anything again, let’s do safe diagnostics that don’t change your account and don’t add more failed attempts:

1) Consistency check: Pick one device + one network (no VPN) and don’t bounce between Wi-Fi/cellular. Switching signals can raise “unusual login” friction and change which checkpoint you get.

2) Document-readability check (offline): Look at the photo you uploaded. Can you clearly read every line of text, and are all four corners visible? Glare on holograms and cropping are common rejection triggers.

3) Match check: Compare your Facebook profile name (the one the account uses) to the legal name on the ID. If the last name is shortened or missing parts, that can explain “couldn’t confirm” even with a legit ID.

Two important things there:

1) “You can’t use this feature right now” often points to a rate-limit/cooldown on the verification tool. It’s not a permanent verdict by itself, but it’s a sign to stop attempts and avoid making the flow stricter.

2) Those paid “restore” emails are a huge red flag. Disabled-account situations attract scams. Don’t send your ID, login code, password, or “verification link click” to anyone. Official flows don’t require paying a stranger.

About the cropped photo: if corners/text were cut off or the glare covered details, that can absolutely lead to “identity verification failed.” But the safest move is not “try again immediately.”

Safe next checks:
• Save screenshots of the exact error wording and the date/time you last attempted.
• Verify any email you received is actually from Meta/Facebook domains and matches what you see when you try to log in (phishing often doesn’t match your real account state).
• If you see an “Account Status” or “Review” page, note whether it says “submitted,” “in review,” or “can’t confirm identity.”

That “disabled → confirm identity → fails → start again” pattern is basically a verification loop, and it’s usually driven by one of these:

• Method acceptance issue: the system isn’t accepting the uploaded document (readability, type, file format).
• Matching issue: the account name/details don’t align closely enough with the ID (shortened surname can matter).
• Attempt cooldown: multiple submissions push you into a temporary block, so the flow resets but won’t process a new attempt yet.

On your Business concern: yes, personal account status can impact access to linked assets (Pages, ad accounts, Business Manager) because permissions flow from the profile. That’s why we want clean, escalation-ready notes instead of more rapid attempts.

Quick clarifiers to understand risk level:
1) Do you have any other admins on the business page/business portfolio (so the page doesn’t go completely unmanaged)?
2) Was the disable sudden after a login, after changing security settings, or after posting/running ads?
3) Do you remember the exact profile name shown on the disabled screen (same spelling as your ID or the shortened version)?

Your description points to a combination of mismatch + risk signals (travel + VPN) + cooldown from multiple attempts. Any one of those can increase strictness; together they often produce the “start again” loop.

I can’t promise what Facebook will allow or when, but here’s the safest diagnostic way to think about it (without “guess-fixing”):

Most likely causes (diagnosis only):
• Name alignment: shortened surname on the profile vs full legal name on the ID can cause “couldn’t confirm” with no detailed reason.
• Submission quality: cropped edges/glare makes automated checks fail even if the ID is valid.
• Cooldown timing: “feature not available” usually means “stop and wait,” not “keep trying in different browsers.”
• Network consistency: switching locations/VPN can lock the flow to stricter identity confirmation steps.

Practical low-risk move right now: stop attempts, keep one stable device/network for the next check, and prepare a clean “evidence pack” (screenshots, exact wording, timestamps, what document type you used). That helps you avoid accidental escalations like new security prompts or longer cooldowns.

Exactly — pausing is the safest move.

Here’s what to document (quick, useful, and support-friendly):
• The exact error text (“couldn’t confirm your identity,” “you can’t use this feature,” etc.) + screenshot.
• Date/time of your last submission attempt (cooldowns are often time-based).
• Which method it asked for (ID upload vs selfie video vs confirm info).
• Document type used (driver’s license/passport/national ID) and whether the uploaded image had any crop/glare/blur.
• Name alignment note: “profile uses shortened surname; ID shows full legal name.”
• Environment note: travel/VPN on/off, and which device/network you used.

Also: keep any suspicious “restore your account” emails as evidence, but don’t click their links. If something changes (the flow starts showing “in review” or offers a different verification method), that’s a meaningful signal the state is moving.

You’re welcome. With disabled-account identity checks, the biggest win is avoiding extra failed attempts and keeping your notes clean. If you later see a new option (different document type prompt, “review in progress,” or a verified email from Meta that matches what you see on-screen), that’s when you reassess calmly instead of looping.