Meta initiated the rollout of an updated account structure for the WhatsApp Business Platform on September 23, 2026, automatically migrating existing accounts into two components to support greater flexibility for businesses and partners. The change creates a WhatsApp Account that holds the phone number and can link to several Messaging Accounts, each tied to a specific integration or provider for independent management of templates and payments. According to Meta’s developer documentation, this evolution allows a single number to handle diverse functions such as promotional messaging, utility updates, payments processing and customer support calls without requiring separate lines or merged billing records.
Under the revised framework, the WhatsApp Account serves as the container for the business phone number and future username, while each Messaging Account manages partner-specific details including message templates, billing methods and webhook configurations. Meta’s documentation explains that templates remain unique to each Messaging Account to avoid overlap, and payment settings stay isolated per partner to maintain clear financial separation. The update reaches all businesses by mid-October 2026, with the company handling the migration automatically so that existing integrations continue without immediate disruption.
Businesses can now collaborate with different providers simultaneously using the same WhatsApp number, routing conversations based on permissions while preserving a unified thread for the end customer. Meta’s overview of the account model evolution notes that one partner might manage marketing messages, another utility notifications and a third payments or call-based support, all under one number. The structure supports enhanced display name approvals and integrates with ongoing expansions in WhatsApp payments available in select markets, according to platform updates.
The legacy WhatsApp Business Account previously combined all elements into one entity, which limited multi-partner setups and complicated billing when scaling operations. Meta’s developer resources state that the new separation addresses those constraints by introducing distinct identifiers for the WhatsApp Account and Messaging Accounts, with phase two of the rollout adding new Graph API versions that require targeting the WhatsApp Account ID for certain calls. Phase three will make the transition mandatory, ensuring full adoption across the ecosystem.
This account model change coincides with broader feature enhancements to WhatsApp, including improved calling from web browsers and expanded bill payment options that a Meta announcement earlier in 2026 said would cover thousands of providers across dozens of categories in key regions. Companies using the platform for customer engagement benefit from reduced friction in managing multiple service types through one number. Meta’s documentation emphasises that no immediate action is required from businesses or partners during the initial migration phase.
Developers integrating with the Cloud API or Embedded Signup will see updated interfaces in Meta Business Suite that display separate tabs for WhatsApp Accounts and Messaging Accounts. The 2FA PIN for certain phone numbers is also being deprecated gradually as part of the rollout, Meta’s technical guidance indicated. The update forms part of ongoing efforts to streamline business communications on a platform that Meta reports handles billions of messages daily across consumer and enterprise users.
