To check business verification status on Meta, open the correct business portfolio and review its business verification information in the Security Center.
Read the complete message, including any request for additional action. A status label is useful only when you know which business it belongs to and what the accompanying instructions say.
This guide explains where to start, how to interpret the information you find, and what to record before seeking assistance.
For the classic business verification flow, 360dialog’s documentation identifies Meta Business Suite → Security Center as the place to track progress. It also states that the verified status appears in Meta Business Suite after approval.
You can start from the Meta Business Security Center.
Navigation and available options can vary. If your verification request began through a particular product or provider, also review the instructions associated with that process.
Before interpreting any status, confirm that you are viewing the intended business.
This matters when your account has access to several portfolios or when different businesses use similar display names.
Check:
The selected portfolio name.
The business portfolio ID.
The business information associated with it.
Whether it matches the portfolio used for your submission.
Record the identifier with your verification notes. A name alone may not be enough to distinguish two similar portfolios.
Within the relevant portfolio’s settings, locate the Security Center and inspect the business verification section.
Read the status together with any explanation, action button, or request shown below it.
Do not use an unrelated account indicator as a substitute. For example, an advertising account message or a public badge may concern a different asset or process.
If you are unsure what you are looking at, capture the section heading and surrounding explanation rather than only the status word.
The following table describes common situations in plain language. It is an interpretation guide, not a promise that every account uses these exact labels.
| Situation shown | What to establish | Practical next step |
|---|---|---|
| Verification completed | The result belongs to the intended business | Record the status and check your original requirement |
| Submission under review | Whether any action is requested | Monitor the submission and associated notifications |
| Additional information requested | The specific missing or unclear detail | Prepare the requested response |
| Submission unsuccessful | The reason or explanation available | Review the issue before resubmitting |
| Verification not started | Whether your business needs and can access the process | Check the relevant requirement |
| Verification option unavailable | Whether this is an access, eligibility, or workflow issue | Review the account message and original instructions |
Avoid drawing conclusions from a single word without checking the surrounding text.
Look for messages related to the same business and submission.
Compare the portfolio identifier, submission date, and any case reference. If several people are involved, ask who completed the last action and whether anyone has already responded.
When an email says action is needed, sign in through Meta’s business tools and inspect the corresponding request there.
Keep the status displayed in the account separate from a supplier’s progress update. A message saying “documents prepared” describes work performed; it does not establish that verification is complete.
Start by recording when the submission was completed and whether the account requests further information.
If an estimated review period is displayed, use it as a reference. Do not assume that an estimate is a guaranteed approval deadline.
While waiting:
Keep one person responsible for monitoring updates.
Preserve the submission details and case reference.
Respond to any specific request through the appropriate process.
Avoid making unrelated changes simply because the status has not moved.
If you seek support, describe the current message and submission history. “My BM is not working” gives less useful context than a precise account of what you see.
Review the explanation available in the account or associated notification.
Identify whether the issue concerns business information, supporting evidence, or another stated requirement.
Then compare that explanation with what was submitted. A new submission should address the identified issue rather than repeat the same information without review.
For example, if the concern is an inconsistent business name, inspect the entered name and relevant records before replacing unrelated files.
If you need help understanding the next step, review the Meta Business Verification and Tech Provider services available through BMXMDN. Ask for a clear description of the review and assistance included.
First, confirm that you selected the correct portfolio and are using an account with appropriate access.
Next, identify the product or notification that prompted the verification requirement. Not every missing option has the same cause, and a missing button alone does not prove rejection.
The provider documentation notes that an unavailable Start Verification button may indicate that a portfolio is not yet eligible for that flow.
Record the actual message rather than assuming that creating another portfolio will resolve the issue.
Prepare a short support summary:
Business portfolio ID: [Identifier]
Current message: [Exact wording]
Submission date: [Date, if applicable]
Last completed action: [Brief description]
Additional information requested: [Details or none shown]
Assistance needed: [Specific question]
Attach a screenshot only when it helps explain the issue. Remove unrelated personal information, payment details, and sensitive business records.
Do not include passwords, authentication codes, or recovery codes in a routine support request.
If you are evaluating a verified BM offer, ask to inspect the current status of the exact portfolio involved.
Confirm the portfolio identity, the business represented, and the authorized access arrangement. A screenshot of another portfolio does not establish the status of the proposed item.
Keep the questions separate:
Is the relevant business shown as verified?
What assets are included?
What permissions would your team receive?
What relationship authorizes your use?
Verification status alone does not answer all four.
A business name alone is insufficient to reliably identify the relevant portfolio and inspect its private verification information. Use authorized access to the correct business environment.
Do not treat a review-in-progress message as a rejection. Read the explanation and check whether action is required.
No. Inspect the configuration and requirements of each relevant asset separately.
It records what was shown at a particular time. Request a current inspection if the present status matters to your decision.
First review the account instructions and available support options. Do not assume that a repeated submission will resolve an unexplained delay.
Checking the correct portfolio, reading the full message, and recording the submission history gives you a clearer basis for action.
If you need assistance reviewing your situation, visit BMXMDN and explain the requirement you are trying to satisfy. Request a proposal that clearly identifies the work included, the information you must provide, and how progress will be documented.
