How to Verify a WhatsApp Business Account

Documents, Sequence and Rejections (2026)

Quick answer: Read Meta's submission conditions and almost all of them turn out to be paperwork conditions rather than judgments about your business. A legal name typed the way the company is known instead of the way it is registered. A utility bill submitted to prove a company name, which Meta explicitly does not accept for that purpose. A website that loads over plain HTTP. A document in a language Meta's list does not cover, with no stamped translation. Every one of those is checkable before you submit, which is what this page is: the checkable list, the order the three gates actually run in, and what to change when the answer comes back no.

What the badge is, why people call it green when Meta's current documentation says blue, and where Meta's own pages contradict each other about eligibility are all in the companion entry on the WhatsApp green tick. Read that first if you are still deciding whether to bother. Platform choice, per-message pricing and compliance are in the WhatsApp channel guide; the first bot build is the WhatsApp chatbot tutorial.

Three gates, and they do not run in the order you expect

Most setup guides present verification as one step near the beginning. It is three separate reviews, run at different levels of your account, and the sequence contains a genuine surprise.

The surprise is in the middle row. Meta's display-name article says you do not need a completed display-name review or account checks to start, that you can send messages immediately, and that your requested display name "becomes eligible for review once your business becomes eligible for higher messaging limits." Display-name approval is therefore downstream of scaling rather than a gate in front of it, so the sequence below runs scaling before the name review. It is easy to read this sequence backwards, and much published guidance does.

The practical consequence: ship and start messaging while the paperwork runs in parallel. The 30-day registration clock in front of the badge request is running either way.

Gate one: business verification, and the document rules that decide it

Before you start. You need full control of the business portfolio, the highest permission level, or the option will not appear in Security Center. Meta notes that an "Ineligible for verification" state is a real answer meaning you do not need to complete it there, and that businesses paying for ads by monthly invoicing can submit credit-line information instead of documents.

What you type has to match. Meta asks for legal business name, address, phone number and website, and instructs that these match your legal entity's details exactly. It also requires that your website loads and is HTTPS-compliant. That last one takes five seconds to check and is easy to fail if a marketing site moved and a redirect was left on plain HTTP.

Which documents Meta accepts. If no matching public record is found for what you typed, you will be asked to upload documents. Meta lists five primary types, and the fifth carries a restriction that catches people out:

• Certificate or Articles of Incorporation
• Business Registration or License document
• Government-issued business tax document, such as a tax certificate. Self-filed tax documents are not accepted.
• Business bank statement
• Utility bill. Accepted only for business address and phone number, with the legal business name shown on it. Meta states it is not an acceptable document for verifying the legal business name.

Documents must be unexpired and issued by the relevant authority. Meta also asks you to redact personal information it does not need, such as a social security number or its local equivalent, before uploading. We read these as Meta's primary supported types; acceptable documentation can vary by jurisdiction, so check what your own registry issues.

Language rules are a real failure mode. Supporting documents must be in one of twenty-one languages: Arabic, Bengali, English, French, German, Greek, Hebrew, Hindi, Indonesian, Italian, Japanese, Korean, Malaysian, Mandarin, Polish, Portuguese, Russian, Spanish, Thai, Turkish or Vietnamese. Anything else needs an English translation carrying the official stamp of a translating agency. Ukrainian, Dutch, Czech, Swedish, Romanian, Danish, Finnish and Hungarian are among the languages not on that list, so a company whose registry extract comes in one of them should budget for certified translation unless the registry can issue an English or multilingual version.

Confirming the connection. Meta then asks you to prove you are connected to the business you described, by email, phone, text message, WhatsApp message, or domain verification through a meta tag or DNS record. Our suggestion, and it is ours rather than Meta's: take domain verification if you control DNS, because it does not depend on a shared inbox somebody left behind.

Timing, and one trap. Meta says a decision may take up to fourteen business days. The trap: if you edit your business details after verifying, you have to complete the process again. Settle the trading address internally before you submit.

Gate two: the display name

The display name is the business name customers see on your profile, assigned when you add a phone number to your WhatsApp Business account. Meta reviews it for consistency with the WhatsApp Business Messaging Policy and against its display-name guidelines, and approval is a precondition for the badge.

Three notes that are easy to miss:

• You can send before it is approved. Messaging is not blocked by a pending name review.
• Changing the name restarts the review. Any change made after a review has been initiated needs its own approval before the updated name can be used.
• The certificate has a 14-day shelf life, and only matters on the On-Premises API. Meta notifies you to download a certificate when a name is approved; if it expires you resubmit the name for review. Our channel guide's position is that any new 2026 deployment should be on the Cloud API, in which case this step is not yours.

Gate three: the Official Business Account request

By this point most of the work is done. Meta's two enumerating pages differ from each other on one criterion, and a third page adds a notability requirement neither of them lists; the companion green tick entry sets all three side by side and works through what to make of them. For planning purposes what you need from that analysis is short. Four conditions are common to both lists and are the ones you can act on: policy compliance, 30 days registered on the WhatsApp Business Platform, two-step verification enabled on the number, and an approved display name. The fifth is where they part — the developer documentation requires business verification outright, while the help article accepts either business verification or a record of at least 1,000 conversations over 30 consecutive days.

The request itself is a form. In Meta Business Suite, open WhatsApp Manager, click the phone number under WhatsApp accounts, then use the Submit Request button under Phone numbers > Profile > Official business account, which is Meta's own breadcrumb. Meta's instructions have you enable two-step verification before submitting if it is not already on. Via the API, request the official_business_account field on the business phone number to read oba_status.

If the option is not there despite meeting the criteria, Meta's help article on requesting an OBA gives the instruction: contact your Meta point of contact, your Solution Provider's support, or Meta Support to check whether you are eligible for the application process. That is a supported state with a defined escalation rather than a bug to work around, and it makes your platform vendor a legitimate route rather than a bystander.

When it comes back no

A denied OBA request costs you 30 days. You can then submit a new request. Meta states the denial does not limit your ability to share your business details, and lists the business profile fields — picture, email, website, description — as editable at any time. It says the account did not meet the eligibility requirements at that time, not that it is barred.

A failed business verification is usually a document problem rather than a judgment about your business. Meta does not publish a ranked list of causes, so nobody can tell you which one you hit. What Meta does publish is the set of conditions a submission has to satisfy, and each is a plausible failure. Work them in order: does the legal name match the registration exactly; is the document unexpired and authority-issued rather than self-filed; if it is a utility bill, are you using it only for address or phone, with the legal name on it; is it in one of the twenty-one languages or accompanied by a stamped translation; does the website load over HTTPS; did the person submitting have full control of the portfolio.

Our judgment, offered as such: after two denials on the same document, change document type rather than resubmitting the same one more legibly. Articles of incorporation, a government-issued tax certificate and a business bank statement carry different information, and a bank statement is often the easiest to obtain in a clean, current, authority-issued form. We are reasoning from what Meta accepts rather than from an outcome we observed.

Should a small business bother?

The honest cost-benefit turns on one mechanical fact rather than on trust.

Meta documents that a business phone number without Official Business Account status will not appear in search results inside the WhatsApp app, though a user who has saved your number still sees your display name in their own search. So the badge buys in-app findability. If customers reach you by typing your name into WhatsApp, which is how a clinic, a garage or a restaurant taking bookings tends to be found, that is an acquisition channel and the application is worth an afternoon. If every conversation starts from an ad, a website widget, a QR code on a receipt or a link in an email, in-app search is not how anyone finds you and the badge is cosmetic.

Set against that, most of the prerequisites are work you should do anyway. Business verification is one of three routes to lifting your messaging limit past 250 recipients per moving 24 hours, which every growing sender needs regardless of badges. Two-step verification is basic account security. An approved display name is required to look like a real business. Three of the four prerequisites stand on their own merits, which leaves the request form itself as the marginal cost.

The argument against is narrower than the internet suggests and is mostly about sequencing: do not let a badge application block shipping. Meta's own design assumes you are messaging customers throughout.

What your platform can and cannot do for you

Chatbotscape earns affiliate commission on some of the platforms we review. It does not change what we publish. See our affiliate disclosure and how we make money.

No vendor grants verification. Meta does. What a vendor can do is narrower, and worth asking about specifically: verify your business as your onboarding partner, which Meta's Messaging Limits documentation names as one of three scaling paths; surface OBA status in its own interface, since the official_business_account field exists in the API; and escalate to Meta when the application option is missing, which Meta's own pages name as a valid route. None of our platform reviews audited verification-support surfaces at their last refresh, so we have nothing first-hand on which vendors do any of the three. Ask them, and see the ranked best WhatsApp chatbot platforms for the buying decision itself.

A pre-submission checklist

Run this before submitting business verification. Items 1 to 9 are documented Meta requirements. Items 10 to 12 are ours.

1. You have full control of the business portfolio.
2. The legal business name you typed matches your registration exactly.
3. The address and phone match that same registration.
4. Your website loads, and the URL starts with https://.
5. Your document is one of the five primary types Meta lists, or the equivalent your jurisdiction issues.
6. It is not a self-filed tax document.
7. If it is a utility bill, you are using it only for address or phone, and the legal business name appears on it.
8. It is unexpired and issued by the relevant authority.
9. It is in one of the twenty-one supported languages, or has a stamped agency translation.
10. Personal identifiers you were not asked for are redacted. (Meta asks; we treat it as mandatory.)
11. The business details are settled internally, because editing them later forces re-verification.
12. Your connection-confirmation method is one you control — domain verification if you own DNS.

Frequently asked questions

Related guides

• WhatsApp green tick (glossary) — what the badge is, and where Meta's own pages disagree
• WhatsApp chatbots — complete guide — platforms, per-message pricing, compliance
• WhatsApp chatbot tutorial — the step-by-step first build
• WhatsApp automation guide — what to automate first, and what each rung costs to run
• WhatsApp broadcast campaign guide — sending to a list without damaging your number
• WhatsApp Business API (glossary) — the platform all three gates sit on

Sources

• Meta. How to verify your business in Meta Business Suite, Meta Business Help Center — the full-control prerequisite, the Security Center path, the "Ineligible for verification" state, the monthly-invoicing credit-line alternative, the exact-match and HTTPS requirements, the connection-confirmation methods including domain verification, the up-to-14-business-day decision window, the re-verification requirement after editing details, the consequences of false or misleading information, and the statement that business verification does not give a verified badge. facebook.com (read 10 August 2026).
• Meta. Upload official documents to verify your business, Meta Business Help Center — the five primary document types, the exclusion of self-filed tax documents, the utility-bill restriction to address and phone with the legal name required on it, the unexpired-and-authority-issued condition, the instruction to redact personal identifiers, and the twenty-one supported languages with the stamped-translation requirement for anything else. facebook.com (read 10 August 2026).
• Meta. Request a WhatsApp official business account, Meta Business Help Center — the business-verification-or-1,000-conversations-over-30-consecutive-days requirement, two-step verification, display-name approval, the 30-day Platform registration requirement, the Meta Business Suite request path with its two-step-verification instruction, the 30-day wait after a denial, and the escalation instruction when the option is not visible. facebook.com (read 10 August 2026).
• Meta. About WhatsApp Business display name, Meta Business Help Center — that you can send before display-name review, that the name becomes eligible for review once the business becomes eligible for higher messaging limits, the re-review requirement after a change, and the 14-day certificate availability for On-Premises API businesses. facebook.com (read 10 August 2026).
• Meta. Official Business Accounts, WhatsApp Business Platform documentation (page stamped "Updated: May 21, 2026" when read) — the five eligibility criteria, the in-app search behavior for non-OBA numbers, the statement that a denial does not limit other ways of sharing business details, the exclusion of WhatsApp Business app numbers, and the official_business_account field with its oba_status value. developers.facebook.com (read 10 August 2026).
• Meta. Messaging Limits, WhatsApp Business Platform documentation (page stamped "Updated: May 21, 2026" when read) — the 250-recipient starting limit defined as unique recipients contacted outside a customer-service window in a moving 24-hour period, calculated at business-portfolio level and shared across numbers; the three scaling paths to 2,000 including partner verification; and the automatic-scaling criteria of high-quality messaging plus at least half the current limit used in the last seven days, raising the limit by one level within six hours. developers.facebook.com (read 10 August 2026).
• Chatbotscape. What is the WhatsApp green tick? /glossary/whatsapp-green-tick — the badge itself, the blue-versus-green finding, the four-way disambiguation and Meta's contradictory eligibility statements, all read from the same Meta pages on the same date.
• Chatbotscape. WhatsApp chatbots — complete guide 2026. /channels/whatsapp-chatbot-guide — the Cloud API default for new 2026 deployments, per-message pricing, opt-in requirements and the platform shortlist. Last verified 26 May 2026; not re-derived here.
• Chatbotscape platform reviews. Vendor-page verification 26 May 2026; authenticated hands-on sessions 26-30 May 2026. None audited verification-support surfaces.
• Chatbotscape evaluation methodology. /methodology (continuously updated).

About this guide

Chatbotscape launched in 2026 as an independent review site for chatbot platforms. This guide is part of our SMB chatbot Academy. It covers the paperwork, the sequence and the rejection handling; what the badge is and what it is worth are in the companion glossary entry, and platform choice sits in the channel guide. If Meta's requirements have moved since we read them, or your experience of the review contradicts what is here, we want to know: editorial@chatbotscape.com.

Methodology

Every requirement, document rule, threshold and timing on this page was read directly from Meta's own developer documentation and Business Help Center on 10 August 2026, and each is attributed in Sources to the page that supports it. We have not taken a Chatbotscape-owned number through business verification, display-name review or an Official Business Account request, so this page carries no approval times, acceptance rates or rejection statistics of our own. Judgment passages are labeled where they appear rather than presented as Meta statements: the recommendation to use domain verification, the advice to switch document type after two denials, items 10 to 12 of the checklist, and the whole of the "Should a small business bother?" section, which weighs Meta's documented in-app-search behavior against how your own customers reach you and is an editorial argument rather than a reported requirement. Platform characterizations carry over from vendor-page verification of 26 May 2026 and authenticated sessions run 26 to 30 May 2026, none of which covered verification support. See our methodology for how platform facts are verified.

Last updated

11 August 2026 — Initial publication aligned to methodology v3.12.1. Next scheduled refresh: 11 November 2026.