> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/onboarding/meta-business-verification.md).

# Meta Business Verification

Meta Business Verification for Partners

***

Meta Business Verification confirms the legitimacy of a company within Meta's ecosystem. As a Partner, verification applies to you in two separate situations that use different methods: verifying your own business, and helping your Clients verify theirs.

### Verifying your own business

To verify your own business, use **Classic Business Verification**. This flow is completed directly in your Meta Business Portfolio and is not submitted by 360dialog on your behalf.

Verifying your business is required to:

* Register as a Meta Tech Provider.
* Onboard more than the standard number of phone numbers as a Partner.
* Establish trust across your Meta assets (Facebook, Instagram, and WhatsApp).

How it works:

* Initiate verification at any time from Meta Business Portfolio > Security Centre.
* Documents must be uploaded by an authorised representative of your business.
* Meta reviews submissions within up to 14 business days. You can track progress in the Security Centre.

{% hint style="info" %}
**Verify your Business Portfolio**\
Business Verification is a prerequisite for the Meta Tech Provider Program. See [Become a Meta Tech Provider](https://claude.ai/partner/get-started/tech-provider-program/become-a-meta-tech-provider.md).&#x20;
{% endhint %}

For the full step-by-step guide, see the Client documentation:

{% content-ref url="/spaces/-M4sMxKjL6eJRvZn6jeG-887967055/pages/6phcPq9pFMBI4exQ1Fx7" %}
[Classic Business Verification](https://docs.360dialog.com/docs/resources/meta-business-verification/classic-business-verification)
{% endcontent-ref %}

### Verifying your Clients' businesses

Your Clients can be verified in three ways. The first, Classic Business Verification, is always available to any Client and is completed directly in Meta with no involvement from 360dialog. The other two routes both use Partner-led Business Verification (PLBV).

{% hint style="warning" %}
**Update 01/09/2026: PLBV Temporarily Paused**\
We have temporarily paused the submission of new PLBV requests while we review the integrity process with Meta. This pause will remain in place until further notice.\
﻿In the meantime, you can proceed with verification through Meta using the Classic Business Verification process. You can follow our step-by-step guide here: 👉 [Classic Business Verification](broken://pages/6phcPq9pFMBI4exQ1Fx7) Guide
{% endhint %}

Partner-led Business Verification (PLBV) is a faster route in which 360dialog submits a Client's business documents to Meta on their behalf, as their Business Solution Provider. It relies on trust signals from 360dialog, such as business and person legitimacy checks, to expedite the process, and can unlock full WhatsApp API capabilities from day one. Before submitting, 360dialog validates the business against Meta's requirements, and Meta usually returns an outcome within 48 hours. The two PLBV routes differ only in how the Client's documents are collected.

#### Classic Business Verification (client-led)

Your Clients can always verify their own business directly, using Classic Business Verification. This route does not involve 360dialog in the submission.

* The Client initiates verification from Meta Business Portfolio > Security Centre.
* Documents must be uploaded by an authorised representative of the Client's business.
* Meta reviews submissions within up to 14 business days.

See the Client documentation.

#### PLBV via the Embedded Signup

The Client uploads their documents during the Embedded Signup, and 360dialog submits them to Meta. This is the lowest-friction route and requires no development work.

1. The Client launches the Embedded Signup to create a WABA and register a phone number.
2. After phone number (OTP) verification, the Client selects "Finish and upload documents" and uploads the required business documents.
3. 360dialog validates the business, then submits the documents to Meta.
4. Meta reviews and returns an outcome, usually within 48 hours.

<div align="left"><figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2F39gqAfG9akXX5zUqd40m%2Fes_upload_docs.avif?alt=media&amp;token=6a41efaf-e697-4cc6-a0be-e1617654a9a6" alt="" width="563"><figcaption></figcaption></figure></div>

See the Client documentation:

{% content-ref url="/spaces/-M4sMxKjL6eJRvZn6jeG-887967055/pages/5m3iSHm64xJUYiZFVBA1" %}
[Partner-led Business Verification (PLBV) for WhatsApp](https://docs.360dialog.com/docs/resources/meta-business-verification/plbv)
{% endcontent-ref %}

#### PLBV via the Partner API

{% hint style="info" %}
**PLBV via the Partner API**

The PLBV endpoints on the Partner API are available on the Growth and Premium Partner Plans only.
{% endhint %}

You can collect the required Client information and documents using whatever method suits your onboarding (web forms, APIs, automation, or manual collection) and submit the request to 360dialog through the Partner API. 360dialog then submits to Meta.

Submit a case with `POST /api/v2/partners/{partner_id}/clients/{client_id}/plbv/cases`, providing:

* One to three documents (PDF, JPEG, JPG, or PNG), each 5 MB or smaller.
* The matching document types, in the same order as the documents.
* The Client's Meta business portfolio ID (`client_business_id`).

Track cases with \
`GET /api/v2/partners/{partner_id}/clients/{client_id}/plbv/cases` (list) and \
`GET /api/v2/partners/{partner_id}/clients/{client_id}/plbv/cases/{case_id}` (retrieve). Requests are authenticated with your Partner API key.

See the full schema and error codes in the Partner API reference:&#x20;

{% content-ref url="/pages/8a838234271aa49f8af845d7f8a044bfa0bf19c7" %}
[Partner Led Business Verification (PLBV)](/partner/partner-api/api-reference/partner-led-business-verification-plbv.md)
{% endcontent-ref %}

{% hint style="info" %}
**PLBV constraints (both routes)**

* Up to 3 PLBV attempts are allowed per Business. After that, Classic Business Verification is required.
* PLBV and Classic Business Verification cannot run at the same time. If a Classic request is pending, wait three days before triggering PLBV.
* PLBV is available for Cloud API and Coexistence phone numbers. It is not available for Government Agencies.
* Meta makes the final decision. Submitting a business to 360dialog does not guarantee verification.
  {% endhint %}

### Which method applies

| Scenario                    | Method                        | How it is submitted                                                  | Typical approval time   |
| --------------------------- | ----------------------------- | -------------------------------------------------------------------- | ----------------------- |
| Your own (Partner) business | Classic Business Verification | You submit in Meta Business Portfolio > Security Centre              | Up to 14 business days  |
| Client verifies directly    | Classic Business Verification | The Client submits in Meta Business Portfolio > Security Centre      | Up to 14 business days  |
| Client via Embedded Signup  | PLBV                          | The Client uploads in the Embedded Signup; 360dialog submits to Meta | Usually within 48 hours |
| Client via Partner API      | PLBV                          | You submit documents via the Partner API; 360dialog submits to Meta  | Usually within 48 hours |

### Related

For document requirements, accepted document types by country, and Meta Verified for Business, see the Client documentation:&#x20;

{% content-ref url="/spaces/-M4sMxKjL6eJRvZn6jeG-887967055/pages/qazxw5WHIRAHSY8W49bR" %}
[Meta Business Verification](https://docs.360dialog.com/docs/resources/meta-business-verification)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/partner/onboarding/meta-business-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.