Migrate to messaging_account_id Before 31 December 2026

What Is the messaging_account_id Deadline in 2026?

The deadline is 31 December 2026. Under WhatsApp's new account model, the Messages API gains a messaging_account_id parameter. The older paid_messaging_account_id parameter is supported only as a deprecated, backward-compatible alias, and Meta says to migrate to messaging_account_id by 31 December 2026, after which the alias is planned for removal in a future Graph API version.

For Indian businesses, the same date carries a second and more serious deadline. Eligible customers must migrate every account in their business portfolio to INR billing by 31 December 2026, because from 1 January 2027 Meta will no longer deliver messages from their non-INR accounts. One date is a code cleanup. The other is a delivery cut-off.

Why Does messaging_account_id Exist in 2026?

Because one phone number can now be linked to more than one Messaging account. Under the new account model, each partner working with a client gets its own Messaging account for templates and billing, and each billing currency can have its own Messaging account too. When a single access token can reach several of those on the same number, Meta cannot tell which one to bill and attribute a message to. messaging_account_id is how you tell it.

Meta states the rule as a single condition: include the parameter whenever the access token you are sending with has messaging access to more than one Messaging account on the business phone number in your request. Everything else, the multi-partner cases, the multi-currency cases, a direct developer holding several Messaging accounts on its own number, is an example of that one rule rather than an exception to it.

When Do You Actually Need to Send It in 2026?

Only in multi-Messaging account situations. If your token reaches exactly one Messaging account on the number you are sending from, the question does not arise, because there is only one account to bill. The table below sorts the common setups.

The timing of the requirement is staged. At Phase 1, general availability in late 2026, the parameter is optional. From Phase 2 in H1 2027 the newest Messages API version requires it for multi-Messaging account setups, while older versions still accept calls without it and Meta attempts to resolve the account from your app's association. From Phase 3 in H1 2028, every Messages API version requires it in those setups.

What Does messaging_account_id Do to Billing and Analytics in 2026?

It decides where a message is counted. Meta explains that a message counts toward the analytics and the charges of the Messaging account it was sent from, and that messaging_account_id is what selects that Messaging account when more than one is reachable. Get it wrong and nothing fails loudly. The message is delivered, billed and reported against the wrong account.

• Analytics: a message appears in the analytics of the Messaging account it was sent from.
• Charges: a message is billed to that Messaging account's payment method.
• Currency: because currencies can sit on separate Messaging accounts, the parameter also decides which currency a message is billed in.

What Is the INR Billing Deadline for Indian Businesses in 2026?

WhatsApp billing localisation launched on 1 January 2026 for partners and directly integrated businesses whose Sold-To country is India in Billing Hub. Meta calls these eligible customers. Eligible customers must ensure every account in their business portfolio is migrated to INR by 31 December 2026 to avoid disruption, because from 1 January 2027 Meta will no longer deliver the messages of non-INR accounts belonging to eligible customers.

Meta provides a Currency Migration API, available since 1 June 2026, to make the move faster. Brazil follows the same pattern a year later: eligible Brazilian customers must migrate to BRL by 30 June 2027, with non-BRL delivery stopping on 1 July 2027.

The link between the two deadlines is direct. The new account model lets one phone number carry several Messaging accounts in different currencies. An Indian business mid-migration may briefly have both a USD and an INR Messaging account on the same number, which is exactly the situation where messaging_account_id decides which one a message is billed to.

Prepaid billing with UPI in India

Meta also added a guide in September 2026 for accounts in India that fund messaging with UPI top-ups instead of invoiced billing. It covers how the funds check works and why a send can return accepted and still be rejected for insufficient funds on the status webhook, with error 131042. Teams on prepaid UPI billing should treat the status webhook, not the API's acceptance response, as the record of whether a message actually went out.

How Do You Migrate Before 31 December 2026?

Treat it as two parallel workstreams: one in the code, one in Billing Hub. Neither is large, and both have the same deadline.

Code workstream

1. Search every integration for paid_messaging_account_id, including any provider SDK you depend on.
2. Replace it with messaging_account_id. Meta documents precedence when both are supplied, but the clean state is to send only the new name.
3. List every access token and, for each phone number, how many Messaging accounts that token can reach.
4. Send messaging_account_id explicitly wherever a token reaches more than one, rather than relying on Meta's resolution.
5. Plan the move to the Phase 2 Messages API version for 2027, since that is where the parameter becomes required.

Billing workstream for India

1. Confirm your Sold-To country in Billing Hub, since that is what makes you an eligible customer.
2. List every account in the business portfolio and its current billing currency.
3. Migrate each non-INR account to INR using the Currency Migration API or Billing Hub, well before 31 December 2026.
4. Verify sends after each migration by checking status webhooks rather than API acceptance.
5. Brief finance that invoices and payment methods will change currency.

Who Has to Act: the Business, the Partner or the Developer in 2026?

If you work through a provider, the right question to ask them this quarter is short: have you replaced paid_messaging_account_id, and have our accounts been moved to INR? For the cost changes already live from 1 October 2026, see the service message pricing hub.

What Are the Common Mistakes in 2026?

• Treating the INR deadline as a billing preference. From 1 January 2027 non-INR accounts of eligible customers stop delivering.
• Assuming a provider has handled it. Ask, and confirm in Billing Hub.
• Leaving paid_messaging_account_id in place. Migrate by 31 December 2026.
• Relying on Meta to guess the account. Send messaging_account_id whenever a token reaches more than one Messaging account.
• Ignoring misattribution. A message with the wrong account is billed and reported against the wrong account, silently.
• Trusting accepted on prepaid UPI billing. Insufficient funds can still reject the send on the status webhook.
• Leaving the 2027 upgrade until 2028. Phase 3 makes the parameter required on every API version.

Key Takeaways for 2026

31 December 2026 is a double deadline for Indian WhatsApp users: one in the code, one in the currency.

• Replace paid_messaging_account_id with messaging_account_id by 31 December 2026; the alias is planned for removal in a future Graph API version.
• Send messaging_account_id whenever your access token can reach more than one Messaging account on the number.
• It is optional at Phase 1, required on the newest API version from H1 2027, and required on every version from H1 2028 in those setups.
• A message counts toward the analytics and charges of the Messaging account it is sent from.
• Eligible Indian customers must migrate all accounts to INR by 31 December 2026, or Meta stops delivering their non-INR messages from 1 January 2027.
• The Currency Migration API has been available since 1 June 2026.
• On prepaid UPI billing, a send can be accepted and still rejected for insufficient funds.

Distk helps growth teams across India and internationally audit WhatsApp integrations for deprecated parameters, sort out which Messaging account each send belongs to, and get the INR migration done before it becomes a delivery outage. If 31 December 2026 is on your calendar, that audit is where we start.

Sources

• Updates to WhatsApp Business accounts, Meta for Developers, for messaging_account_id, the alias deadline and the phase timeline.
• Pricing on the WhatsApp Business Platform, Meta for Developers, for India and Brazil billing localisation.
• WhatsApp changelog, Meta for Developers, entries dated 29 August and 8 September 2026.