WhatsApp account vs. Messaging account: the new WABA structure

Updated on October 28, 2026

Since September 23, 2026, Meta has been splitting the old WhatsApp Business Account (WABA) in two: the WhatsApp account (WAAC), which holds the phone number and profile, and the Messaging account, which holds templates, billing and webhook subscriptions. The migration is automatic, current IDs and tokens keep working, and the Messaging account inherits the WABA ID. The most practical consequence: switching or adding a provider no longer requires migrating the number; you just share the WhatsApp account.

Why Meta changed the WABA

The Updates to WhatsApp Business accounts page explains the problem. The WABA bundled the number, templates, billing, webhooks and partner access into a single entity. To work with two partners, a business needed two numbers, and end users saw two different contacts for the same brand.

The new model separates the business identity (the number) from messaging operations (templates and billing). One number can have several Messaging accounts, one per integration, each with its own templates, payment method and metrics. WhatsApp users still see a single contact.

What lives in each account

Asset	Before (WABA)	After (new model)
Phone number	WABA	WhatsApp account (WAAC)
Business username (upcoming)	didn’t exist	WhatsApp account
Business profile and catalogs	WABA	WhatsApp account
Templates	WABA	Messaging account (one per partner)
Billing and payment method	WABA	Messaging account
Webhook subscriptions	WABA	Messaging account
Conversation history and quality	Number	Number (unchanged)
Business verification	Portfolio	Portfolio (unchanged)
Access tokens	App + WABA	App + Messaging account (same tokens)

A few details the table doesn’t show:

• Each WAAC holds a single number. To group numbers, Meta uses a hierarchy with a primary WAAC and linked WAACs. Sharing the primary one grants access to every number in the set.
• The WAAC always belongs to the client (or direct developer). The Messaging account can belong to the client or the partner.
• In the Terms of Service, the WAAC is called the “WhatsApp Business Account” and the other one the “Messaging account”. Worth knowing when you read a contract.
• Templates aren’t shared between Messaging accounts. If you need the same template in two, create it in each or use the template migration API. When templates are migrated, quality rating and messaging tier reset to defaults, with an adjustment period of 2 to 4 weeks.
• Throughput and messaging limits stay where they were. Throughput belongs to the number, and the unique-recipients-per-24-hours limit belongs to the portfolio; when several partners use the same number, they share both.

Want to try it while you read? Create a Vectalk account and send your first message through the official API. Create free account →

What changes (and what doesn’t) in the API

The list of what doesn’t change is long: Cloud API, Business Management API and Marketing Messages API endpoints; POST /<PHONE_NUMBER_ID>/messages; phone number IDs; tokens; template workflows; number registration; business verification; display names; quality; and the whatsapp_business_account webhook subscription, now made with the Messaging account ID (the same as the WABA ID). GET/POST/DELETE /<WABA_ID>/message_templates stays the same.

What changes comes in three phases:

Phase	When	What ships	What you do
1. General availability	Sept 23, 2026 through mid-October 2026	Automatic migration; Messaging accounts keep the WABA ID; WAACs created but IDs not exposed; messaging_account_id optional	Nothing, unless your token reaches more than one Messaging account on the same number
2. New Graph API version	H1 2027	WAAC ID returned alongside the number ID; new endpoints; whatsapp_account webhook topic; separate permissions for WAAC and Messaging account scopes; messaging_account_id required on the new version in multi-account setups	Capture waac_id in events and adopt the new version if you have several Messaging accounts
3. Mandatory transition	H1 2028	APIs that take the phone number ID in the path (including /messages and /marketing_messages) require the WAAC ID	Have your code migrated during 2027

Meta notes that the whole page is subject to change. The 2027 and 2028 dates are half-years, not specific days.

The messaging_account_id parameter

When your token can reach more than one Messaging account on the same number, Meta can’t tell which to bill. This parameter resolves it:

curl -X POST 'https://graph.facebook.com/<API_VERSION>/<PHONE_NUMBER_ID>/messages' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{
    "messaging_product": "whatsapp",
    "to": "15551234567",
    "messaging_account_id": "<MESSAGING_ACCOUNT_ID>",
    "type": "template",
    "template": { "name": "order_shipped", "language": { "code": "en_US" } }
  }'

Rules from the Messaging accounts page:

• if the token reaches only one Messaging account on that number, Meta picks it for you;
• if it reaches two or more and you omit the parameter, the message may be billed to the wrong account or the request may be rejected;
• paid_messaging_account_id is a legacy alias: migrate to messaging_account_id by December 31, 2026; if you send both, messaging_account_id wins;
• to check whether a Messaging account has a payment method, call GET /<MESSAGING_ACCOUNT_ID>?fields=primary_funding_id; without that field, it can’t send paid messages.

Typical cases that need the parameter: a direct developer outsourcing marketing to a partner on the same number, a partner that received two Messaging accounts from one client, and a client billed in different currencies (each currency requires its own Messaging account).

IDs in webhooks

In phase 1 nothing changes in code, but the waba_id in events now means the Messaging account ID. In phase 2, events gain waac_id. Store all three (waac_id, phone number ID and waba_id) in your instance records. If your CRM is also adapting to usernames and BSUIDs, it’s worth doing both data model changes together.

Switching providers got simpler

This is the most visible impact for anyone buying API access. Since August 18, 2026, Meta documents that phone number migration between partners isn’t supported in the new model. Instead:

1. The client shares the WhatsApp account (WAAC) with the new provider.
2. Embedded Signup automatically creates a new Messaging account for that provider, returning its ID in the WABA ID field.
3. The number, conversations and quality rating stay where they were; there’s no downtime.
4. The client decides whether to keep or remove the previous provider, whenever they want.

Two caveats. First, because templates are isolated per Messaging account, the new provider starts without your templates: recreate or migrate them. Second, registration with the new provider is routed to the already registered number without resetting the PIN, and Meta is phasing out the 6-digit two-step verification PIN for eligible Cloud API numbers (still, keep sending a valid pin to /register until Meta announces a different contract). More context in how to switch WhatsApp API providers and registering a number on the Cloud API.

When a provider is removed from a Messaging account, it receives the account_update webhook. For setups with more than one partner on the same number, Meta launched Conversation Routing on September 23, 2026, which defines which partner receives each inbound message.

Coexistence and the new structure

WhatsApp Business app numbers in coexistence (connected to the API while still using the app) are migrated too. During coexistence onboarding, Meta converts the client’s existing WABA into a backward-compatible Messaging account (same ID) and shares both the WhatsApp account and that Messaging account with the partner; no partner-specific Messaging account is created. The coexistence guide now requires subscribing to account_update. What syncs between app and API is covered in WhatsApp coexistence: what syncs.

What changes in Meta Business Suite

For businesses already migrated, Meta Business Suite shows two tabs: WhatsApp accounts (numbers and usernames) and Messaging accounts (templates and billing). Until your business is migrated, WhatsApp Manager and Business Suite keep the old view, so the docs may be ahead of what you see. If you manage several brands, this changes the routine described in WhatsApp API for agencies.

How it works with Vectalk

Vectalk is a proxy for the official WhatsApp Cloud API. Connecting still happens through Embedded Signup under Instances → Connect account, which imports phone_number_id, waba_id and the token; under the new model, that waba_id is the Messaging account ID. If you’re coming from another provider, Meta’s rule for the new model applies here too: the number isn’t migrated; the WhatsApp account is shared with the new provider. Step by step in the quickstart; sign up at apps.vectalk.com.br/register.

Frequently asked questions

Did my WABA ID change?

No. The WABA ID became the Messaging account ID and keeps working in template, webhook and Business Management API calls.

Do I need to change my code now?

Only if your token can reach more than one Messaging account on the same number; in that case, send messaging_account_id. Also replace paid_messaging_account_id with messaging_account_id by December 31, 2026. The bigger task, using WAAC IDs, is for 2027, ahead of phase 3 in 2028.

Can I use two providers on the same number?

Yes. The new model was built for that: each provider has its own Messaging account, with separate billing. They share the number’s throughput and the portfolio’s messaging limit.

Do my templates come with me when I switch providers?

Not automatically. Templates belong to the Messaging account. Recreate them with the new provider or use the template migration API, knowing that quality and tier restart from defaults.

Is phone number migration between providers still possible?

Not in the new model. Meta documents that the request is rejected if the destination WhatsApp account doesn’t own the number. The path is sharing the WAAC.

---

Official sources consulted on October 28, 2026: Updates to WhatsApp Business accounts (updated September 22, 2026), Managing Messaging accounts (updated August 29, 2026), Onboarding changes (updated June 26, 2026), WhatsApp Business Platform changelog.