How to Get WhatsApp Business API Approval in India (2026)
Most "approval" delays on the WhatsApp Business API in India come from treating one process as two. Business verification in Meta Business Manager is one approval; provisioning your WhatsApp Business Account (WABA) and phone number is another, and each blocks different things. This guide separates the two, lists what Indian businesses need to submit, and covers the display name and template approvals that stall most launches. To skip the provisioning paperwork, The Tech Pad's free account provisions your WABA through Meta's embedded signup, and your first month on paid plans is free.
The two approvals
1. Business verification (Meta Business Manager). Meta confirms your business is a real, registered legal entity. You complete it under business settings in Business Manager with your registered business name, address, and supporting documents. It unlocks verified status, the ability to move past the entry messaging tier, and fewer review surprises. An unverified business can still start at the entry tier, but volume growth waits on verification.
2. WABA and phone number provisioning. This is the plumbing: creating your WhatsApp Business Account, attaching the number you will send from, and connecting it to the Cloud API. It unlocks API messaging, template submission, and your messaging-limits dashboard. Meta's embedded signup creates the WABA, adds your number, and connects the API in one sitting instead of the manual developer-console route.
| Approval | What it is | Typical timeline | Common blockers |
|---|---|---|---|
| Business verification | Meta confirms your business exists and matches its registration | Varies — typically days | Name mismatches between documents and your Business Manager entry; incomplete GST/PAN details |
| WABA + number provisioning | Creates your WhatsApp Business Account and connects your phone number to the API | Immediate with embedded signup; manual provisioning runs through several serial review steps | A restricted or previously banned business; business details that contradict your registration |
| Display name | The name customers see in the chat header and profile | Usually quick — often hours — when it matches your registration | Generic or category-style names; ALL CAPS, emoji or symbols; mismatch with website or registration |
| Template approvals | Each reusable message is reviewed before it can be sent outside the 24-hour window | Utility and authentication: minutes to a few hours; marketing: a day or more | Wrong category; missing or inconsistent sample values; variables at the start or end of the message |
Both are mandatory, but not sequential — provisioning can finish before verification does. Send the paperwork early and let provisioning run in parallel.
Documents Indian businesses need
Meta does not publish one fixed document list for India — it depends on your entity type and what you enter in Business Manager — but requests for Indian businesses cluster around three documents:
- GST registration. Your GSTIN and the registration certificate, commonly requested to confirm you are an operating business.
- PAN. The PAN card of the business or proprietor/partners, used to match the entity.
- Business registration proof. Certificate of Incorporation for a company or LLP, Udyam registration for small businesses, or shop-and-establishment or partnership registration where applicable.
Keep clean scans of all three handy. Most rejections at this stage have nothing to do with validity — the name on the document does not exactly match the business name you typed into Meta Business Manager: "Tech Pad Retail Pvt Ltd" on the certificate and "Tech Pad" in the form gets flagged. Enter the legal name exactly as registered and keep your display name consistent with it. You will also need the phone number you register: Meta verifies it with a one-time code by SMS or call before it goes live.
Display name rules and why names get rejected
Your display name is what customers see in the chat header, and Meta reviews it before you can start business-initiated conversations at volume. Rejections cluster into predictable buckets:
- Generic or category names. "Bakery", "Online Store", "Customer Care" — anything that describes a category instead of naming your brand gets rejected. The name must include your actual brand.
- Format violations. ALL CAPS, emoji, symbols, extra spaces, and promotional words ("OFFERS", "SALE", "BEST DEALS") are automatic problem areas. Plain title case, brand only.
- Mismatch with your website or registration. The top rejection reason: the name does not match the brand on your website, your registration, or your Business Manager entry — "Tech Pad" on your domain but "TechPad Offers" as your display name gets rejected.
Fix and resubmit rather than appeal — a corrected name clears faster. Pick the display name once, matching your registered brand, and keep it identical across Business Manager, your website, and your templates.
Opt-in: the approval Meta audits later
Unlike business verification, opt-in is not a one-time approval screen — consent is a standing requirement Meta audits against when messages draw complaints, checking whether you have evidence each recipient agreed to hear from you. In India that expectation aligns with the DPDP Act: a checkbox and privacy note at the point of capture (checkout, lead form, signup page) is the baseline, and you should store when and how each contact opted in.
The practical rules:
- Collect opt-in through your own channels (checkout, forms, in-store). Never buy lists or scrape numbers.
- Record the timestamp and source of each consent; a delivery log is part of your evidence if Meta asks.
- Give recipients an obvious way out and honor it: opt-outs should suppress future business-initiated messages.
Our guide to [collecting opt-in at checkout](/blog/whatsapp-opt-in-shopify-checkout-consent/) walks through a consent checkbox flow that meets both Meta and DPDP expectations for Indian e-commerce.
Template approval: UTILITY vs MARKETING
Every message you send outside the 24-hour customer-service window must be a Meta-approved template, and each template is approved individually. Approvals hinge on category and content:
- Category must match intent. Utility covers transactional messages a customer expects (order updates, delivery status); authentication covers OTPs and login codes; marketing covers promotions. Meta's classifier rejects mislabeled templates — miscategorization is the top rejection reason, and labeling a promotional blast "utility" does not survive review.
- Sample values must be realistic. Reviewers and the classifier judge the placeholder examples you submit; fake-looking samples like "test" or "123" draw rejections.
- Variables follow rules. Use
{{1}},{{2}}for dynamic content — but not at the start or end of the message. Each variable carries a type (text, amount, date) that must stay consistent across sends.
Utility and authentication templates typically approve in minutes to a few hours; marketing takes a day or more with stricter review. Cost-wise, utility runs roughly ₹0.10–0.30 per message in India and marketing about 2–3× utility — check Meta's current rate card, and see our [WhatsApp Business API pricing in India](/blog/whatsapp-business-api-pricing-india-2026/) before you budget. When a template is rejected, the fix is usually in the details — see [rejected reasons and fixes](/blog/whatsapp-template-rejected-reasons-fixes/) and [template categories and pricing in 2026](/blog/whatsapp-template-category-pricing-2026/).
Timeline: what takes minutes vs days
Set expectations by the route you choose:
- Embedded signup (via a Business Solution Provider). The WABA, phone number, and API connection are provisioned inside the signup flow — minutes, not days. Business verification still runs separately, but you can set up templates and test while it does.
- Manual developer route. Create a developer account and app, add the WhatsApp product, create the WABA, then add and verify your number — serial steps in the developer console, each with its own review.
- Business verification. The slowest variable step — typically days, depending on document quality and matching. It also gates tier growth, so start it first.
- Display name. Usually hours when it matches your registration; a rejection adds a resubmission cycle.
- Templates. Utility and authentication clear in minutes to a few hours; marketing takes a day or more.
Once approvals land, your number starts at the entry messaging tier and climbs with sustained, high-quality sending — see how [messaging limits and tiers work in 2026](/blog/whatsapp-messaging-limits-tiers-2026/) so you do not mistake a tier cap for an approval problem.
BSP vs going direct
You can build against the WhatsApp Cloud API directly, or go through a Business Solution Provider (BSP). Direct gives you full control — but you own the app credentials, the code that talks to the API, template submission loops, error handling, and any inbox or campaign tooling. For most Indian businesses that is infrastructure, not advantage.
A BSP handles the platform layer. With The Tech Pad, embedded signup provisions your WABA and number when you sign up, the template hub submits and tracks approvals with one click, and you get a shared team inbox, campaigns, delivery logs, and free connectors for WordPress, WooCommerce, and Shopify on top. You still complete business verification and the display name step yourself — those are Meta's calls — but nothing about the plumbing is on your plate. Our roundup of the [best WhatsApp API providers in India](/blog/best-whatsapp-api-providers-india-2026/) compares embedded signup support, template tooling, and pricing across the field.
Start with a free account
Approval is two document runs and a few review cycles — the provisioning half is the busywork. The Tech Pad's embedded signup provisions your WABA during signup, the template hub handles submissions and tracking, and the shared inbox and campaigns work from day one. Start with the free account at thetechpad.com/wa — your first month on any paid plan is free, and [pricing](/pricing) shows what comes after.