Meta is rolling out a Business-Scoped User ID (BSUID) for WhatsApp users in India. After the rollout, Meta may omit the customer’s mobile number and instead place the BSUID in customer_identifier. The BSUID consists of a two-letter country code, a dot, and a 128-character alphanumeric string, for example IN.3243412413241241. If your systems validate customer_identifier strictly as a phone number, WhatsApp events that contain only a BSUID will fail to reach you unless you adjust your logic.
| Field | Where | Today | After BSUID rollout |
|---|---|---|---|
| customer_identifier | Envelope root | Customer phone number in E.164 | Phone number in E.164; the BSUID (not E.164) if and only if the phone number is missing |
| meta_bsuid | conversation object in each payload | Not present | New. BSUID as received from Meta |
| meta_username | conversation object in each payload | Not present | New. WhatsApp username as received from Meta |
| Event | Method |
|---|---|
| message.received | POST |
| message.sent | POST |
| message.delivered | POST |
| message.read | POST |
| message.failed | POST |
| message.link_tracking | POST |
| conversation.assign | POST |
| conversation.close | POST |
The conversation object in every event listed above now carries meta_bsuid and meta_username.
| What Meta sends | customer_identifier | meta_bsuid | meta_username |
|---|---|---|---|
| Phone number only (no BSUID rollout yet) | Phone number | Absent | Absent |
| Phone number and BSUID | Phone number | BSUID | Username, if the user has set one |
| BSUID only (phone number missing) | BSUID | BSUID | Username, if present |
Whenever Meta supplies a phone number, it takes precedence. The BSUID is used only when the phone number is missing, and the new meta_ fields are forwarded unchanged in every case.
{
"company_id" : "69ddcadb46536124",
"event_id" : "event-6576745fc0df84a7d230bfae2d1d8f3bd51fd0428d1001150755b15a265219c37f0b0770",
"event_type" : "message.received",
"event_sequence" : 1,
"event_version" : "1",
"timestamp" : "2026-04-20T10:06:07.835252916Z",
"channel" : "whatsapp",
"direction" : "incoming",
"session_id" : "e8e99f13-f41e-4655-b393-09e03cb5f91c",
"system_identifier" : "1196177000238423",
"customer_identifier" : "917779812955",
"payload" : {
"id" : "1975ec0a-67fe-4a37-af4b-4ed7449862ab",
"action" : "incoming",
"status" : "received",
"data" : {
"type" : "text",
"context" : { "body" : "Offer" }
},
"conversation" : {
"id" : "e8e99f13-f41e-4655-b393-09e03cb5f91c",
"customer_country_code" : "91",
"customer_contact" : "7779812955",
"customer_name" : "Suraj Singh",
"meta_bsuid" : "IN.3243412413241241",
"meta_username" : "suraj",
"status" : "assigned"
},
"phone_number_id" : "1196177000238423",
"mode" : "lc",
"source" : "lc"
}
}If Meta omits the phone number, the payload is identical except that customer_identifier holds the value IN.3243412413241241, matching payload.conversation.meta_bsuid.
As of October 2026, Meta still provides the mobile number for Indian users, so your current setup continues to work for now. Meta has not announced an exact go-live date and may provide only short notice. Update and test your integration ahead of time to avoid any disruption.
Email support@myoperator.com or call +91 81029 81029 if you need additional sample payloads or assistance testing the new behaviour.
Keywords
BSUID, Business-Scoped User ID, WhatsApp webhook, WABA webhook, customer_identifier, meta_bsuid, meta_username, Meta, phone number, integration update, conversation object, MyOperator