WhatsApp Business API Onboarding Documents in India

WhatsApp Business API Onboarding Documents in India: Complete Checklist

The usual WhatsApp Business API onboarding documents in India include your business registration proof, PAN, address proof, authorised representative details, and documents for the phone number you want to use. The exact checklist depends on your legal structure, Meta Business account status, and the WhatsApp Business Solution Provider or technology partner handling the API onboarding.

WhatsApp Business API is now generally referred to as the WhatsApp Business Platform. It is designed for businesses that need shared inboxes, customer support workflows, notifications, lead management, chatbots or integrations with a CRM, website, payment system or internal software.

The document collection is not just an administrative step. Correct legal names, matching addresses and access to the right Meta accounts can prevent delays during business verification and phone-number activation.

What WhatsApp Business API Onboarding Involves

WhatsApp API onboarding normally has several connected stages:

1. Creating or preparing a Meta Business account.
2. Adding the organisation’s legal and business information.
3. Completing business verification, if required.
4. Connecting a WhatsApp Business Account, commonly called a WABA.
5. Adding and verifying a business phone number.
6. Setting the display name and business profile.
7. Creating message templates for outbound notifications.
8. Connecting the API to an inbox, CRM, chatbot or other software.

A provider may complete some of these tasks for you, but the business owner still needs to supply accurate information and approve access requests.

A small clinic, school, NGO or D2C brand may have fewer documents than a private limited company with several brands. However, all applicants should expect some form of identity, legal-entity and contact verification.

API onboarding is different from using the WhatsApp Business app

The WhatsApp Business app can be installed on a phone and used by a small team with limited features. The WhatsApp Business Platform is intended for programmatic messaging and multi-user operations.

API onboarding is relevant when you need features such as:

• A shared customer-support inbox
• Multiple agents handling conversations
• Automated replies and routing
• Website or CRM integration
• Order, appointment or payment notifications
• Lead capture from campaigns
• Conversation history connected to your business systems
• Approved templates for initiating customer conversations

The API does not remove WhatsApp’s rules on consent, message quality, templates or user blocking. It also does not mean that every message can be sent freely to every contact.

Core WhatsApp Business API Onboarding Documents in India

The following documents are commonly requested during WhatsApp Business API onboarding in India. A provider may ask for all or only some of them, depending on the organisation and the status of its Meta Business account.

1. PAN card of the business or organisation

The PAN is one of the most important identity documents for an Indian business. For a company or LLP, this is normally the entity’s PAN. For a sole proprietorship, the proprietor’s PAN may be used along with the business name and supporting registration or tax documents.

For NGOs and charitable organisations, the organisation’s PAN is generally more appropriate where one exists. The legal name shown on the PAN should be consistent with the registration certificate, GST certificate or other official records submitted during verification.

Check the following before uploading:

• The PAN number is readable.
• The legal name is visible.
• The document is not cropped in a way that removes important information.
• The name does not conflict with the name entered in Meta Business Manager.
• The uploaded file is clear and in an accepted format.

A PAN card alone may not establish that the organisation is actively operating from a particular address. Additional business registration or address documents may therefore be required.

2. Business registration or incorporation proof

The required document depends on your legal structure.

Common examples include:

• Certificate of Incorporation for a private limited or public limited company
• LLP incorporation or registration certificate
• Partnership deed or firm registration document
• Shops and Establishments registration, where applicable
• Udyam Registration Certificate for eligible MSMEs
• GST registration certificate
• Trust deed or society registration certificate
• Section 8 company incorporation documents
• Government registration or authorisation documents for certain institutions
• Registration documents for educational, healthcare or charitable organisations

A sole proprietor may not have a separate incorporation certificate. In that case, providers may accept a combination of the proprietor’s identity document, business proof, GST certificate, Shop and Establishment registration, Udyam certificate, bank document or another official record.

The important point is that the document should demonstrate a connection between the legal entity and the business name being used on WhatsApp.

3. GST registration certificate

A GST certificate is frequently useful for business verification in India, although not every organisation or business is registered under GST. Some small businesses, organisations or activities may not be required to register, depending on their circumstances and applicable rules.

Where available, the GST certificate can help confirm:

• Legal business name
• Trade name
• Principal place of business
• GSTIN
• State of registration
• Nature of the registered entity

Make sure the trade name and legal name are entered correctly. A common issue is using a brand name in one place, the proprietor’s personal name in another and a registered company name in a third. These names may be related, but the relationship needs to be clear in the records submitted.

Do not obtain or submit a GST certificate merely to satisfy an onboarding checklist. GST registration has tax and compliance implications and should be handled with a qualified tax professional.

4. Address proof

Business address proof may be requested even when the address appears on another registration document. Typical documents may include:

• GST registration certificate
• Shops and Establishments registration
• Certificate of Incorporation showing the registered office
• Recent utility bill
• Bank statement or official bank document
• Municipal licence
• Property tax document
• Registered rent or lease agreement
• Government-issued registration certificate

If the business operates from a rented office, the provider may ask for an additional document connecting the organisation to that premises. A utility bill in the landlord’s name may not always be enough by itself.

For a home-based business, the proprietor should use documents that accurately represent the business address. Do not edit or alter an address document to make it match another record.

5. Identity and contact details of the authorised representative

The person completing onboarding generally needs to be connected with the organisation. Providers may ask for:

• Full name
• Work email address
• Business phone number
• Position or role in the organisation
• Identity document, where required
• Proof of authority to act for the business

The person should normally be a proprietor, director, partner, trustee, office-bearer, senior employee or another authorised representative.

Use a business email address where possible. A personal Gmail address may work in some situations, particularly for small businesses, but a domain-based email can make the relationship with the organisation clearer.

If an agency or technology partner is onboarding the account on your behalf, the business should understand which Meta account owns the assets. The client should not lose control of its Business Manager, WhatsApp account or phone number simply because an external provider helped with setup.

6. Company or organisation website

A website may be requested as part of the business identity and public-presence check. It should show enough information to connect the website with the organisation.

Useful pages include:

• Business or organisation name
• Contact details
• Physical or registered address, where appropriate
• About page
• Services or products
• Privacy policy
• Terms of use or customer-support information
• NGO registration or programme information, where relevant

A website is not a substitute for a legal document. A simple landing page may establish a public presence, but the provider or Meta may still ask for formal records.

The name on the website should not contradict the legal details being submitted. If the brand name differs from the legal entity, explain the relationship through the website footer, About page, legal notice or business documents.

7. Phone-number ownership and verification details

The phone number used for WhatsApp API must be available for verification. Depending on the setup, you may need access to SMS or voice calls sent to that number.

Keep these points in mind:

• The number should be controlled by the business or authorised organisation.
• Someone must be available to receive the verification code.
• The number should not be actively connected to a regular WhatsApp account unless the provider supports a migration or coexistence process.
• Landline numbers may have different verification requirements.
• Virtual or temporary numbers can create ownership and recovery problems.
• The number should be suitable for ongoing customer communication.

If you are migrating a number from the WhatsApp Business app, ask the onboarding provider how chat history, contacts and existing account settings will be handled. Do not delete an existing account before understanding the migration process.

8. Brand and display-name information

Your WhatsApp display name may be reviewed separately from the legal name. The display name should have a clear connection with the organisation, product, service or public-facing brand.

Prepare:

• Preferred display name
• Legal entity name
• Brand name, if different
• Website URL
• Business category
• Short business description
• Customer-support hours
• Email and phone contact details

A brand name that has no visible relationship with the submitted organisation may cause questions. For example, if “ABC Foods” is the customer-facing brand but the legal entity is “XYZ Retail Private Limited”, the website and documents should make that connection understandable.

The display name is not the same as a verified badge. A display name can be configured as part of the business profile, while any additional account recognition or subscription-related feature has its own eligibility and process.

Documents by Indian Business Structure

Different organisations should prepare different document sets. The table below is a practical starting point, not a guarantee of what Meta or a provider will request.

This list is intentionally broad. A provider may ask for fewer documents for an account that already has a verified Meta Business account, or more documents if names, addresses or ownership details do not match.

Meta Business Verification and Document Matching

Meta verification is often confused with a WhatsApp profile check. In practice, business verification generally relates to the organisation and its Business Manager or Meta business portfolio, while WhatsApp setup involves the WABA, phone number, display name and messaging configuration.

Why matching information matters

Verification problems commonly arise from inconsistencies such as:

• PAN shows one legal name and GST shows another without an explanation.
• The website displays only a brand name with no link to the registered entity.
• The address in Meta Business details differs from the submitted registration proof.
• The authorised representative’s email does not appear connected to the organisation.
• The phone number belongs to an employee who leaves the organisation.
• The business has several similar names and the provider cannot identify the correct legal entity.
• A document is expired, unreadable or missing relevant pages.

Before starting API onboarding, prepare a single master sheet with:

• Exact legal name
• Trade name
• Brand name
• Registered address
• Operating address
• PAN
• GSTIN, if applicable
• Website
• Authorised representative
• Business email
• Preferred phone number
• Legal entity type

Use the same spelling and punctuation wherever possible. If the legal name contains “Private Limited”, “LLP”, “Foundation”, “Society” or another suffix, do not casually remove it from official fields.

What if the business is not eligible for GST?

Not every organisation is required to register under GST. If you do not have a GST certificate, use other legitimate records such as incorporation proof, Udyam registration, Shop and Establishment documentation, trust or society registration, or an appropriate address document.

The absence of a GST certificate does not automatically mean that an organisation cannot use WhatsApp Business Platform. The relevant requirements may depend on the account, country, provider and verification flow.

What if the brand name differs from the legal name?

This is common for D2C brands, schools, clinics and NGOs. The solution is not to replace the legal entity name with the brand name in every field.

Instead, show the relationship clearly:

• Put the legal entity in legal-business fields.
• Use the customer-facing brand where the display-name field allows it.
• Mention the brand and legal entity on the website.
• Keep invoices, privacy policies and contact pages consistent.
• Provide a trademark or brand document if requested and available.
• Ask the provider which name should be used for each field.

Phone Number, SIM and Migration Checklist

The phone-number stage creates practical problems because the number becomes part of the WhatsApp account’s identity.

Before onboarding, decide whether to use:

• A new number dedicated to customer communication
• An existing business number
• A number currently used on the WhatsApp Business app
• A landline or office number
• A number used by a call centre or customer-support team

A dedicated business number is often easier to manage. It reduces the risk of losing access when an employee changes role and avoids mixing personal conversations with customer-support conversations.

For an existing WhatsApp number, confirm:

1. Who legally controls the number.
2. Who receives the verification code.
3. Whether the current WhatsApp account must be removed or migrated.
4. Whether existing chats will remain available.
5. Whether the same number can be used with the chosen setup.
6. How two-factor authentication and account recovery will work.
7. Which team member will own the Meta account.

Do not share verification codes in a group or send them to an unknown person. The code allows account activation and should be handled like a password.

Provider, BSP and Access Requirements

Most Indian businesses use a provider, integration partner or WhatsApp Business Solution Provider for API onboarding. Some companies use Meta’s Cloud API directly with their own technical team. The commercial and technical arrangement differs, but the document principles remain similar.

Your provider may ask for:

• Business documents
• Meta Business Manager access
• Admin approval
• Phone-number access
• Website and privacy policy details
• Business profile information
• Message use case
• Sample templates
• Opt-in process
• CRM or helpdesk requirements
• Billing and GST details

Questions to ask before authorising access

Ask the provider:

• Who owns the Meta Business account?
• Who owns the WABA?
• Who owns the phone number and display name?
• Can the business change providers later?
• What happens if the monthly service is stopped?
• Are conversation, template or platform charges separate from implementation charges?
• Who will manage templates and quality issues?
• Is there a support process for rejected messages?
• Will the business receive administrator access?
• How will customer data be protected?

The provider should not need unrestricted access to unrelated assets. Review permissions carefully and give only the access required for onboarding and integration.

For Indian businesses handling customer data, also review your privacy notice, vendor agreements, access controls and retention practices. The Digital Personal Data Protection Act, 2023 and other applicable legal requirements may be relevant depending on your organisation, data categories and operations. A WhatsApp integration does not replace the need for responsible consent and data handling.

Message Templates, Consent and Indian Compliance

Documents are only one part of approval. Your messaging use case also matters.

Businesses commonly use WhatsApp for:

• Order updates
• Delivery notifications
• Appointment reminders
• Admission or fee-related communication
• Donation acknowledgements
• Customer-support replies
• Lead follow-up
• Service alerts
• Marketing campaigns

You should be able to explain how users provide their phone numbers and consent to receive messages. Examples include a website checkbox, an enquiry form, an order process, an in-store form or an opt-in flow initiated by the user.

Avoid uploading scraped contact lists or sending unsolicited promotional messages. Users may report or block the business, and poor message quality can affect the account.

Marketing communication in India may also intersect with consent, telemarketing and customer-preference rules. For regulated sectors such as healthcare, education, finance and charitable fundraising, additional restrictions may apply to the content and handling of personal information.

A message template should be specific and useful. It should not hide the commercial purpose of the message or make claims that the business cannot support.

For example, an appointment reminder can identify the clinic, appointment date and support contact. A promotional message should be sent only where the customer has provided an appropriate opt-in and should offer a practical way to stop future messages.

Common Reasons Onboarding Gets Delayed

Legal name mismatch

The most frequent issue is inconsistency between the name entered in Meta Business settings and the name shown on submitted documents. Decide which name is the legal entity and which is the brand before submission.

Incorrect address

Old certificates, branch addresses and rented-office documents can create confusion. Use the address that the submitted document actually supports, and explain the relationship between registered and operating addresses when needed.

Unclear business ownership

An agency may create an account using its own details, while the client assumes the account belongs to the client. Decide ownership before onboarding. The business that will use the number should normally control the core business assets.

Unavailable verification number

If the SIM is with an employee, receptionist or former agency, verification can stop immediately. Keep the number and recovery process under business control.

Weak website presence

A website that has no business name, no contact information or only placeholder text may not adequately support the organisation’s identity. It should be accurate, current and aligned with the submitted records.

Unsupported or incomplete documents

Blurry scans, cropped certificates, password-protected files and screenshots with missing pages may be rejected. Use clear, complete files and retain originals securely.

Premature template preparation

Some businesses write templates before deciding the actual customer journey. First define the use case, opt-in source, support process and escalation route. Then prepare templates that reflect the real workflow.

Assuming verification guarantees approval

Business verification does not guarantee that every display name, template or message use case will be approved. These are related but separate decisions.

A Practical Document Preparation Process

Use this process before starting API onboarding.

Step 1: Identify the legal entity

Write down the exact organisation that will own the account. For a brand, this may be a company, partnership, proprietor, trust, society or Section 8 company.

Step 2: Collect a clean document set

Create a secure folder with:

• PAN
• Registration or incorporation proof
• GST certificate, if applicable
• Address proof
• Website URL
• Authorised representative details
• Phone-number ownership information
• Brand or trademark documents, if relevant

Do not upload documents randomly through multiple vendors. Confirm where they are being submitted and who can access them.

Step 3: Reconcile names and addresses

Compare every document with the information in Meta Business settings. Record any difference and prepare an explanation or supporting document.

Step 4: Prepare access and approvals

Make sure the authorised person can log in to the relevant Meta account and approve business, phone-number or provider requests. If the director, trustee or proprietor must approve something, schedule it rather than waiting for an unavailable person.

Step 5: Document the messaging use case

Write a short description covering:

• Who sends messages
• Who receives them
• How users opt in
• Which messages are transactional
• Which messages are promotional
• How users contact human support
• How opt-outs are recorded

Step 6: Confirm ownership and exit options

Before agreeing to onboarding, know who owns the WABA, phone number, templates, customer data and integration credentials. Ask how the setup can be transferred if you change software providers.

Frequently Asked Questions

What documents are needed for WhatsApp Business API onboarding in India?

Most businesses should prepare PAN, legal registration or business proof, address proof, authorised representative details, website information and access to the phone number being registered. A GST certificate is useful where available but may not apply to every organisation. The final checklist depends on the legal structure and provider.

Is GST registration compulsory for WhatsApp Business API?

GST registration is not automatically compulsory for every business or organisation using WhatsApp Business Platform. If your entity is registered under GST, the certificate can support identity and address verification. If you are not required to register, ask the provider which alternative documents it accepts.

Can a sole proprietor use WhatsApp Business API?

Yes, a sole proprietor can generally apply using the proprietor’s PAN and appropriate business or address proof. The provider may ask for Udyam registration, Shop and Establishment proof, GST registration or another document connecting the proprietor to the business name. Brand information should be consistent across the website and profile.

Can an NGO, trust or school use WhatsApp Business API?

Yes, an NGO, trust, society or school can prepare its parent organisation’s registration certificate, PAN, address proof and authorised representative details. If the school or programme uses a different public name, show its connection to the registered organisation on the website and in supporting records.

Can I use my existing WhatsApp Business number for API onboarding?

Often, an existing number can be migrated or handled through an available coexistence arrangement, but the exact process depends on the provider and current account setup. Confirm what happens to existing chats, contacts, profile information and access before making any change. Never deactivate the number without a migration plan.

How long does WhatsApp API onboarding take in India?

There is no fixed timeline for every application. It depends on document quality, business-verification requirements, Meta review, phone-number access, provider processes and whether the names and addresses match. Preparing a consistent document set usually reduces avoidable back-and-forth, but it cannot guarantee approval or a particular completion date.

Where to Start

First identify the legal entity that will own your WhatsApp Business Platform account. Then collect its PAN, registration proof, address document, website details, authorised representative information and a business-controlled phone number.

Next, compare the names and addresses across all documents, decide whether you need a new number or migration, and write down your consent and messaging process. Before granting access to a provider, confirm ownership of the Meta Business account, WABA, phone number and templates.

For help reviewing the onboarding checklist, connecting WhatsApp API to your CRM or setting up a shared inbox, talk to the Govindani Infotech team on WhatsApp.