Hi! When verification is stuck at 99%, it usually means the “submission” went through, but the last gate isn’t completing — most often a manual review, a detail mismatch (name/address/legal entity), or a session/UI progress that’s not reflecting the real status yet.

We’ll keep this low-risk: no repeated resubmits, no deleting documents, and no “try random edits” that can reset your place in the queue.

First, tell me what you’re verifying and where you see the 99%:
1) Which platform/service is it (business verification, identity verification, profile verification)?
2) Does it say “pending review,” “processing,” “under verification,” or just a progress ring stuck at 99%?
3) About how long has it been stuck, and did you submit any documents (ID, business docs, video, address proof)?

Thanks — “99% + in review” strongly suggests the platform accepted your upload and you’re waiting on a review decision, but there are a few common reasons it looks stuck even when it’s moving behind the scenes:

• Queue + manual checks: the last 1% is often human review or additional verification checks.
• Missing confirmation step: sometimes there’s a final acknowledgement or info request in a Support Inbox instead of email.
• Mismatch triggers “silent hold”: name/address/legal entity doesn’t perfectly match the documents, so it waits for clarification.
• Duplicate submissions: re-uploading can create parallel requests and slow it down.

Quick safe questions (no changes yet):
1) Did you submit more than once (or click “resubmit” after the first upload)?
2) Is the business name shown in the verification flow an exact match to the registration document (punctuation, LTD/LLC, spacing)?
3) Are you checking the platform’s internal support/messages area, not only email?

Those two details are the exact kind that can keep a verification request “almost complete” without giving you an obvious error.

Why it matters: many verification systems treat the legal name and address formatting as strict fields (even if humans would consider them the same). A missing “LLC” or a suite mismatch can push the request into a “needs review / needs clarification” state — and that’s when the progress often sits at 99%.

Also, resubmitting once doesn’t doom it, but it can create a second request or reset the review order. So from here, the safest approach is to avoid more resubmits and focus on confirmation checks.

Low-risk checks you can do today:

1) Check the Support Inbox / alerts area inside the platform for requests like “provide additional info” (sometimes no email is sent).

2) Confirm the on-screen “submitted details” (business name line, address line, contact email/phone). Write them down exactly as shown — including commas, suite/unit, LLC/Inc.

3) Avoid switching devices/accounts mid-check (different admin profiles can show different verification screens).

Your instinct is right: uploading “just to try” can reset the clock. A stuck progress ring is often a UI indicator, not a live meter — it can sit at 99% the entire time the review is pending.

Before changing anything, let’s separate two possibilities:
• True review pending: the request is in a queue and 99% is just the last-step placeholder.
• Submission state stuck: a browser/app session or cached state is showing the wrong stage (less common, but it happens).

Safe tests to tell the difference (no edits, no resubmit):

1) Alternate view test: open the verification status page in a private/incognito window. If it still shows 99% + “in review,” that’s likely the real status, not a local cache glitch.

2) Timestamp sanity check: is there any “submitted on” date/time or case/reference number? If yes, capture it — that’s useful if you later need to follow up.

3) Notification hygiene: check spam/filtered mail AND any “business notifications” area. Some systems post updates internally first.

There can be “friction factors,” but I’d be careful with that framing because most platforms don’t confirm risk flags directly. What we can say safely is:

• Multiple verification requests across products (business verification, identity checks, profile verification) can add complexity, especially if the underlying account details don’t match everywhere.
• Pending states can persist when the reviewer needs additional info, when documents aren’t fully readable, or when fields don’t line up (like LLC/suite formatting).
• Resubmitting too often can keep you from reaching a decision, because you’re effectively changing the item being reviewed.

A practical, safe “alignment check” you can do without changing the verification request itself:

1) Make sure your business contact email/phone is current and accessible (verification updates sometimes go there).
2) Confirm there aren’t conflicting names/addresses across connected assets (page details vs business info vs billing info). You’re not editing anything yet — just noting differences.
3) Keep a simple log: submitted date, what docs were provided, exact business name/address shown in the flow, and where you checked for updates.

Not “forever,” but the safest next move depends on which detail is mismatched and whether the platform provides a way to update business info separately from the verification request (some do, some don’t). Since you’re already in review, the goal is to avoid actions that restart the queue while still preparing for a clean follow-up if needed.

Here’s a risk-aware way to think about it (diagnosis + prep, not a guaranteed fix):

• If 99% = active review: your best leverage is good documentation: exact details shown, proof that documents match the legal entity, and the submission timestamp.
• If the legal name vs brand name is mixed: reviewers may not know the connection unless there’s a clear match in the documents or the profile fields. That’s a common reason for “stuck” reviews.
• If no updates arrive: you’ll want an escalation-ready summary (what you submitted, when, and what mismatches you noticed).

One question that helps categorize it: does the verification screen show the legal entity name you want reviewed, or does it show your brand/display name?

That’s a reasonable concern — and it’s exactly why we keep changes minimal while a review is active.

The strongest “likely cause” from what you shared is: the request is being reviewed against a name that doesn’t exactly match the legal docs. That can keep the process hovering at 99% because the system sees a submission, but the reviewer can’t finalize a match without consistent identifiers.

What I’d do next (still safe, still not forcing a reset):

1) Capture evidence: screenshot the verification page showing the brand name, the submitted date, and the status “in review.”
2) Prepare a match note: write a one-paragraph explanation you can use if prompted (“Brand X is the DBA/brand of Legal Entity Y LLC at Address Z”). Don’t submit it unless the platform asks — just have it ready.
3) Freeze the inputs: avoid resubmitting new documents or changing core business fields until you see a request for changes or a clear path that doesn’t restart verification.

If the status changes (even to “need more info”), that’s progress. The key is staying consistent and ready to respond once the system actually asks for something.

Exactly — 99% is often “the reviewer has it,” not “you’re one step away.” If you get any new message (request for clarification, rejection reason, or a new document prompt), that wording will tell us whether it’s a mismatch issue, a readability issue, or simply queue timing. And if you ever receive “help” DMs asking for codes or documents off-platform, treat that as a phishing red flag.