> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/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/docs/resources/meta-business-verification/partner-led-business-verification-plbv-for-whatsapp.md).

# Partner-led Business Verification (PLBV) for WhatsApp

Partner-led Business Verification (PLBV) helps trusted businesses get verified in as little as 48 using 360dialog.

{% 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](/docs/resources/meta-business-verification/classic-business-verification.md) Guide\
﻿​
{% endhint %}

PLBV is the fastest, easiest and most reliable way to verify businesses on the WhatsApp Business Platform, and it can provide access to full WhatsApp API capabilities from day one. PLBV can be initiated using the Client Hub or at the end of the Embedded Signup, after number registration.

PLBV expedites business verification and onboarding without compromising the integrity of the WhatsApp Business Platform, by leveraging trust signals from 360dialog (business and person legitimacy checks, and registration documents).

## PLBV Integrity Checks

Before submitting a business for verification, 360dialog must verify and confirm 5 criteria:

* The business is a legal entity.
* The account owner is a representative of the business.
* The business complies with the WhatsApp Business Messaging Policy.
* The documents are valid and representative of the business.
* All [prerequisites](#prerequisites) are met & additional 360dialog integrity checks are passed.

Only if **all 5 criteria** are verified by 360dialog can we proceed to submit the Business for verification.

The BSP's role in the PLBV process is to share documentation with Meta that provides **evidence** the business is legitimate and that the applicant has a connection to the business. \
﻿\
If we decline to submit the business for PLBV, the [Classic Business Verification](/docs/resources/meta-business-verification/classic-business-verification.md) process via Meta Business Suite > Security Centre is still available.

### Eligibility

* PLBV is available for Cloud API and Coexistence phone numbers.
* PLBV is not available for Government Agencies.

### Prerequisites

Before requesting PLBV, confirm the business meets all of the following:

* The business has an account with 360dialog (a Client account with a verified email owned by the business).
* The business has a channel with an active subscription.
* The WABA asset is shared with 360dialog
* The business has a website.
* None of the business's WABAs are disabled.

### Document requirements

* We only accept business documents for validation. We do not accept personal documents or IDs.
* All business details in the uploaded documents must exactly match the details listed in the Business Info section of the Business Portfolio, including Legal Business Name, Business Address, Business Phone Number, Business Website (if applicable) and TAX ID.
* The business name shown on the document should be visible on the website as readable text (for example, in the footer).

### Process and timing

* Ensure there are no open or in-progress Classic Business Verification requests before requesting PLBV. If a request is already open, you must wait at least 3 days before submitting the business using PLBV. Running both processes simultaneously causes delays.
* Up to 3 PLBV attempts are allowed per business. After that, the Classic Business Verification process is required.

## PLBV Paths

There are two paths available to use PLBV:<br>

1. [PLBV using the Client Hub (Recommended)](#plbv-using-the-client-hub-recommended)
2. [PLBV using Embedded Signup](#plbv-using-embedded-signup-new-accounts)
3. PLBV using your Integration Partner

PLBV using Chat Support directly is no longer available.&#x20;

***

## PLBV using the Client Hub (Recommended)

Client Users can submit a PLBV request to 360dialog from the Client Hub.

{% stepper %}
{% step %}

#### Register a phone number

Launch the Embedded Signup to create a WABA and register a phone number. \
If you already have a phone number registered and the channel is active, you can skip this step.&#x20;

{% endstep %}

{% step %}

#### Select the channel&#x20;

Select the channel and click > **Verify business**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FZ7FuentAU8IgM7B9Cms0%2FScreenshot%202026-09-16%20095345.png?alt=media&amp;token=58cba48d-946b-4e2b-b20a-dbb85b84d61a" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Select Business

Select the Business to verify.
{% endstep %}

{% step %}

#### Upload documents

Upload accepted. PDF documents.&#x20;

{% endstep %}

{% step %}

#### Complete Business Information

You will be presented with a screen on which you must complete and verify business information:&#x20;

<table data-search="false"><thead><tr><th width="236.18182373046875">Business Information</th><th>Note</th></tr></thead><tbody><tr><td>Company Legal Name</td><td>This must match exactly the business legal name on i) the documentation uploaded ii) The <strong>Legal business name</strong> in Meta Business Suite > Business Info, and iii) the business website</td></tr><tr><td>Registered Address</td><td>This must match exactly the address on i) the documentation uploaded ii) The Address in Meta Business Suite > Business Info, and iii) the business website</td></tr><tr><td>Company Number</td><td>Company Registration Number</td></tr><tr><td>Account Owner Name</td><td>Full Name of the Account owner</td></tr><tr><td>Account Owner Role</td><td>Role / position of the Account owner</td></tr><tr><td>Account Owner Email</td><td>Primary email of the Account owner</td></tr><tr><td>Business Website URL</td><td><p>The business must have a live website that meets the following conditions:</p><ul><li>It is publicly and globally accessible.</li><li>It uses a secure (HTTPS) connection.</li><li>All links are working.</li><li>It is not a landing page, placeholder, template, or in maintenance mode.</li></ul><p>Most importantly, the website must clearly describe the business. A visitor should be able to identify the business vertical and its intended use case for WhatsApp.</p></td></tr><tr><td>Confirm authorized representative</td><td>Acceptance required gt</td></tr><tr><td>Confirm acceptance of <a href="https://whatsappbusiness.com/policy/">WhatsApp Business Messaging Policy</a></td><td>Acceptance required gt</td></tr><tr><td>Note</td><td>Any additional information that might help the chance of a succesful outcome. </td></tr></tbody></table>
{% endstep %}

{% step %}

#### Confirm legal Name

Confirm that the Company Legal Name provided during the submission matches the Legal Business Name on Meta Business Suite > **Business Info**<br>
{% endstep %}

{% step %}

#### Review and submit

Review all the information provided and click **submit**.

{% endstep %}

{% step %}

#### 360dialog Review (internal)

Once we receive the request, we review all the information provided. If the requirements are met, we submit the business to Meta for verification.

If there are issues with one or more of the integrity checks, we may contact you for clarification. In that case, we raise a support ticket proactively and contact the initiator of the request by email.

If the requirements for PLBV are not met, we will decline to submit the business to Meta for verification using PLBV.

{% endstep %}

{% step %}

#### Outcome

Meta will review the business and information provided, including the documents uploaded, and provide an outcome, usually within 48 hours.
{% endstep %}
{% endstepper %}

## PLBV using Embedded Signup

Business admins can initiate PLBV **using the Embedded Signup** after number registration.

{% stepper %}
{% step %}

#### Launch the Embedded Signup

Launch the Embedded Signup to create a WABA and register a phone number.&#x20;

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FZrccqJLBzWU7HoP4N1vf%2Fimage.png?alt=media&amp;token=a52fc506-e996-4800-aaf0-2dcd7035ccc9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Click 'Finish and upload the documents'

After phone number (OTP) verification, click "Finish and upload documents".

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FAXdliToCfJ0Uq9vm2yXc%2Fimage.png?alt=media&amp;token=247e8878-0fcc-4b0d-afe0-ee7323e771e9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Upload documents

Upload accepted. PDF documents.&#x20;

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FRXEDGs8aFscyC5EUMBk9%2Fimage.png?alt=media&amp;token=40e3afbb-4769-4827-8110-3df4a362ee52" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Provide information to support

After uploading the documents via Embedded Signup, start a chat with our support team, request PLBV, and send us the following information:<br>

<table data-search="false"><thead><tr><th width="236.18182373046875">Business Information</th><th>Note</th></tr></thead><tbody><tr><td>Company Legal Name</td><td>This must match exactly the business legal name on i) the documentation uploaded ii) The <strong>Legal business name</strong> in Meta Business Suite > Business Info, and iii) the business website</td></tr><tr><td>Registered Address</td><td>This must match exactly the address on i) the documentation uploaded ii) The Address in Meta Business Suite > Business Info, and iii) the business website</td></tr><tr><td>Company Number</td><td>Company Registration Number</td></tr><tr><td>Account Owner Name</td><td>Full Name of the Account owner</td></tr><tr><td>Account Owner Role</td><td>Role / position of the Account owner</td></tr><tr><td>Account Owner Email</td><td>Primary email of the Account owner</td></tr><tr><td>Business Website URL</td><td><p>The business must have a live website that meets the following conditions:</p><ul><li>It is publicly and globally accessible.</li><li>It uses a secure (HTTPS) connection.</li><li>All links are working.</li><li>It is not a landing page, placeholder, template, or in maintenance mode.</li></ul><p>Most importantly, the website must clearly describe the business. A visitor should be able to identify the business vertical and its intended use case for WhatsApp.</p></td></tr><tr><td>Confirm authorized representative</td><td>Acceptance required gt</td></tr><tr><td>Confirm acceptance of <a href="https://whatsappbusiness.com/policy/">WhatsApp Business Messaging Policy</a></td><td>Acceptance required gt</td></tr><tr><td>Note</td><td>Any additional information that might help the chance of a succesful outcome. </td></tr></tbody></table>
{% endstep %}

{% step %}

#### 360dialog Review (internal)

Once we receive the request, we review all the information provided. If the requirements are met, we submit the business to Meta for verification.

If there are issues with one or more of the integrity checks, we may contact you for clarification. In that case, we raise a support ticket proactively and contact the initiator of the request by email.

If the requirements for PLBV are not met, we will decline to submit the business to Meta for verification using PLBV.
{% endstep %}

{% step %}

#### Outcome

Meta will review the business and information provided, including the documents uploaded, and provide an outcome, usually within 48 hours.
{% endstep %}
{% endstepper %}

## PLBV using your Integration Partner

If you work with a 360dialog Integration Partner, they may support submitting a PLBV request through their own platform. Contact your Integration Partner directly for more information on their process.

***

### View Status

You can view the status of the PLBV case from the Client Hub. \
If we require clarification or more information, you will see the status: **Review request**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2Fsi1sgflAgtHid3mdfyGb%2FScreenshot%202026-09-16%20105201.png?alt=media&amp;token=3b31bd99-d3f2-4d46-9cd9-a401d9756441" alt=""><figcaption></figcaption></figure>

### Business Info

The Business should ensure that the Meta Business Suite > Settings > [Business Info](/docs/resources/meta-business-manager.md) section is fully completed.

The legal business name must match the name shown on the supporting documentation provided.

The business website must be live and fully functional.

If there are any discrepancies or uncertainties regarding the business information, we may request a screenshot of the Business Info section for verification.

Please note that all fields in the Business Info section must be fully completed before proceeding with Partner-Led Business Verification (PLBV). Incomplete or inconsistent information may result in rejection or delays.

### The Outcome

Meta usually provides an outcome within 48 hours. Note that Meta makes the final decision: 360dialog submitting a business for verification does not guarantee that it will be verified.

Our support team will communicate the outcome in the open support case.

On a successful outcome, the business webhook endpoint should receive a `phone_number_quality_changed` event, indicating that:

* the messaging limit has increased to 2,000 per day
* the display name is visible following review

For details, see the [Webhook events](/docs/messaging/webhook/webhook-reference.md) and notifications documentation.

### Troubleshooting&#x20;

* **Mismatch detected / request declined**: Ensure the details under Meta Business Portfolio > Business Info match the documents (legal name, address, registration/VAT).
* **WABA restricted / disabled**: Resolve the WABA status issue first. Businesses with restricted or disabled WABAs are not eligible for PLBV.
* **Insufficient proof of activity**: Provide a recent document, issued within the last 60 days.
* **No webhook received**: Check that the webhook endpoint is reachable and subscribed, and review recent delivery logs.
* **"Verified" status not visible in Business Info**: This is expected. The verification was initiated in the Partner Portal rather than the Security Centre, so the status appears in the "WhatsApp accounts" section of the Business Portfolio instead.
* **Tech Providers**: PLBV is not available to businesses applying to become a Tech Provider. To become a Meta Tech Provider, a business must use Classic Business Verification.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.360dialog.com/docs/resources/meta-business-verification/partner-led-business-verification-plbv-for-whatsapp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
