Meta Introduces a New WhatsApp Business Account Structure: WAAC and Messaging Accounts Explained (2026)

Meta WhatsApp Business API Update – November 2026

Meta is introducing a major change to the WhatsApp Business Platform by separating business phone numbers from message templates, billing and messaging management.

Under the new account structure, the traditional WhatsApp Business Account (WABA) is evolving into two separate account types:

1. WhatsApp Account (WAAC) – Manages business identity and phone numbers.

2. Messaging Account – Manages message templates, billing, payment methods and analytics.

This change is designed to make WhatsApp Business Platform integrations more flexible, particularly for businesses working with multiple WhatsApp API providers, agencies and technology partners.

For businesses using WhatsApp API for customer support, marketing, authentication, e-commerce and automation, understanding this update is important.

In this article, Afojet Infotech explains the new WhatsApp account structure, its benefits, API changes, migration timeline and what developers need to prepare for.

1. What Is Changing in WhatsApp Business Accounts?

Previously, WhatsApp Business Platform used a single WhatsApp Business Account (WABA) structure that combined several assets:

• Business phone numbers
• Message templates
• Billing and payment methods
• Webhook subscriptions
• Partner access

This structure created limitations for businesses that wanted to work with multiple WhatsApp API providers using the same phone number.

For example, a business might use one provider for WhatsApp marketing and another provider for customer support or OTP authentication. Previously, managing multiple integrations could require separate phone numbers.

Meta's new account structure addresses this limitation by separating phone number ownership from messaging management.

Old vs New WhatsApp Account Structure

Old Structure	New Structure
Single WABA structure	WAAC + Messaging Account
Phone numbers under WABA	Phone numbers under WAAC
Templates under WABA	Templates under Messaging Account
Billing under WABA	Separate Messaging Account billing
Limited partner separation	Multiple partner integrations
Shared account management	Isolated templates and billing

The main advantage is that multiple partners can work with the same business phone number while maintaining separate messaging configurations and billing.

2. What Is a WhatsApp Account (WAAC)?

A WhatsApp Account, also called WAAC, represents the business identity on WhatsApp.

It manages the business phone number and associated business assets.

A WAAC contains:

• Registered business phone number

• Business profile information

• Business usernames (future capability)

• Product catalogs

Each WAAC contains a single business phone number.

Businesses can also connect multiple WAACs into a hierarchy, allowing them to manage several phone numbers as a group.

Example

Suppose ABC Company operates three departments:

• Sales

• Customer Support

• Order Management

The company can manage its business phone numbers under a WhatsApp Account hierarchy.

The business owns its WAAC and can share access with multiple technology partners.

This allows the business to retain control of its WhatsApp identity while working with different service providers.

3. What Is a Messaging Account?

A Messaging Account manages the messaging-related services and billing.

Unlike WAAC, which manages business identity and phone numbers, the Messaging Account handles:

• WhatsApp message templates

• Billing and payment methods

• Messaging analytics

• Webhook subscriptions

A Messaging Account can be owned by the business or by a technology partner.

Each partner working with a client can have a separate Messaging Account.

Example: Multiple WhatsApp API Providers

Consider a business using three different WhatsApp API integrations:

Integration	Purpose	Messaging Account
Provider A	WhatsApp Marketing	Account A
Provider B	Customer Support	Account B
Provider C	OTP Authentication	Account C

All three integrations can use the same business phone number through the shared WAAC.

However, each integration maintains its own message templates, billing and analytics.

Important: Templates created in one Messaging Account are not automatically shared with other Messaging Accounts. They must be created separately or copied using Meta's Template Migration API.

4. Benefits of the New WhatsApp Business Account Model

1. One Phone Number, Multiple API Providers

Businesses can share their existing WhatsApp phone number with multiple technology partners.

For example, a company can use:

• One provider for WhatsApp marketing campaigns.

• Another provider for automated order notifications.

• A third provider for customer support.

• Another integration for OTP verification.

Customers continue seeing the same business phone number instead of multiple WhatsApp contacts.

2. Separate Billing for Each Provider

Each partner can maintain its own Messaging Account and payment method.

This makes billing management easier for businesses working with multiple API providers.

3. Independent Message Templates

Each Messaging Account maintains its own templates.

This helps businesses organize templates according to their messaging requirements and service providers.

4. Easier Partner Onboarding

Businesses do not need to migrate their phone number from one Solution Partner to another.

Instead, they can share their existing WhatsApp Account with a new partner.

This reduces onboarding complexity and avoids unnecessary phone number migration.

5. Better Flexibility for Technology Providers

WhatsApp API providers can specialize in different services, such as:

• Marketing automation

• Customer engagement

• Authentication

• E-commerce automation

• Customer support

• Commerce messaging

This creates opportunities for SaaS platforms and software developers building WhatsApp-based solutions.

5. Important WhatsApp API Changes Developers Should Know

Meta has introduced several technical changes that developers should consider when updating their WhatsApp Business Platform integrations.

A. messaging_account_id Parameter

The new messaging_account_id parameter identifies the Messaging Account responsible for a message.

When an access token has messaging access to multiple Messaging Accounts associated with the same business phone number, Meta cannot always determine which account should be charged.

In these situations, developers must specify the Messaging Account ID.

Example:

POST /{BUSINESS_PHONE_NUMBER_ID}/messages

The message request can include:

{
  "messaging_account_id": "YOUR_MESSAGING_ACCOUNT_ID",
  "messaging_product": "whatsapp",
  "to": "919876543210",
  "type": "text",
  "text": {
    "body": "Thank you for contacting us!"
  }
}

The example illustrates the parameter placement concept. Developers should follow the applicable Graph API version and current Messages API request schema.

B. Deprecation of paid_messaging_account_id

Meta currently supports paid_messaging_account_id as a deprecated, backward-compatible alias.

Developers should migrate their integrations to:

messaging_account_id

Meta has announced December 31, 2026, as the migration target for this alias, with removal planned in a future Graph API version.

C. New WAAC ID

Meta is introducing a new WhatsApp Account ID alongside the existing phone number ID.

Important points:

• WAAC IDs and phone number IDs have a one-to-one relationship.

• They are different ID values.

• Existing phone-number-level APIs continue to work with phone number IDs during the transition.

• New APIs will support WhatsApp Account IDs and phone number IDs.

From Phase 3, APIs targeting phone number IDs in endpoint paths or query parameters must transition to WAAC IDs.

D. Existing Access Tokens

One important point for existing developers is that Meta is maintaining backward compatibility during Phase 1.

Existing access tokens continue working.

Existing phone number IDs, Cloud API endpoints, message payloads and template workflows also continue working during this phase.

6. WhatsApp Business API Migration Timeline

Meta has announced a three-phase transition.

Phase	Expected Timeline	Important Changes
Phase 1 – General Availability	September–October 2026	Automatic account migration and new account structure
Phase 2 – New Graph API Version	H1 2027	New WAAC IDs, new APIs and Messaging Account ID requirements
Phase 3 – Mandatory Transition	H1 2028	Mandatory use of new account identifiers for affected APIs

Phase 1 – General Availability

Meta handles the account migration automatically.

Existing integrations continue working, and developers generally do not need immediate code changes unless they support multiple Messaging Accounts.

Phase 2 – New Graph API Version

Meta plans to introduce:

• New WAAC management APIs

• New Messaging Account management APIs

• New WhatsApp Account IDs

• Separate app permissions

• New WhatsApp Account webhook topic

Developers should begin preparing their applications for the new account structure.

Phase 3 – Mandatory Transition

Meta plans to require the new account identifiers for affected APIs.

Developers should complete their migration work before this phase.

Note: Meta's rollout is phased, and individual businesses may see changes at different times.

7. What Should WhatsApp API Providers and Developers Do?

If you are developing a WhatsApp API integration, CRM, SaaS platform or WordPress plugin, preparing your application architecture is important.

Here are our recommendations:

1. Update Your Database Structure

Consider supporting separate fields for:

• WhatsApp Account ID (WAAC ID)

• Phone Number ID

• Messaging Account ID

• Business Portfolio ID

• Access Token

• Graph API Version

2. Update API Request Handling

Your integration should support messaging_account_id when multiple Messaging Accounts are associated with the same phone number and token.

3. Improve Template Management

Maintain template records according to their respective Messaging Accounts.

Do not assume that templates are shared across different partners.

4. Prepare for Embedded Signup Changes

Review your Embedded Signup integration to handle the updated onboarding flow and the separate Messaging Account created for each partner.

5. Prepare for WAAC IDs

Design your application so that phone number IDs and WAAC IDs can be stored and managed independently.

6. Review Webhook Handling

Continue supporting the existing whatsapp_business_account webhook topic and prepare for the new whatsapp_account topic when it becomes available and relevant to your integration.

8. How Will This Change Affect Businesses Using WhatsApp API?

For businesses already using WhatsApp Cloud API, the transition should generally be automatic.

However, businesses should understand a few important points:

• Their existing phone numbers will remain available.

• Existing integrations continue working during Phase 1.

• Different API partners can use the same business phone number.

• Each Messaging Account maintains separate templates and billing.

• Existing conversations remain uninterrupted when additional partners are onboarded.

• Phone number ownership remains with the business.

Businesses should coordinate with their existing WhatsApp API providers before adding or changing integrations.

9. How Afojet Infotech Can Help with WhatsApp API Integration

At Afojet Infotech, we develop software solutions and integrations that help businesses automate their digital operations.

WhatsApp Business API can play an important role in improving customer communication, order management, authentication and e-commerce automation.

Our development focus includes:

• WhatsApp OTP Login and User Verification

• WooCommerce WhatsApp Integration

• Automated Order Notifications

• WhatsApp Customer Communication

• E-commerce Automation

• Custom WordPress Plugin Development

• API Integration and Custom Software Development

With Meta introducing the new WhatsApp Business Account structure, developers and businesses should start preparing their integrations for the upcoming changes.

Our recommendation is to build flexible integrations that can support the existing WABA-based workflows as well as the new WAAC and Messaging Account architecture.

10. Frequently Asked Questions (FAQs)

1. What is the new WhatsApp Business Account model?

Meta is separating the traditional WABA structure into two account types: WhatsApp Account (WAAC), which manages phone numbers and business identity, and Messaging Account, which manages templates, billing and analytics.

2. Can multiple WhatsApp API providers use the same phone number?

Yes. Under the new model, a business can share its WhatsApp Account with multiple partners while maintaining separate Messaging Accounts for each partner.

3. Will businesses need a new WhatsApp phone number?

No. Existing phone numbers are migrated automatically as part of Meta's rollout. Businesses do not need to obtain a new number simply because of this account structure change.

4. Will exis