Article summary
A BSUID is a business-scoped backend identifier introduced with WhatsApp usernames. It changes integration identity handling, but it is not a Number Checker result or a universal person ID.
A WhatsApp Business-Scoped User ID (BSUID) is an integration identifier, not a phone-validation score. Meta introduced it alongside usernames so a business can address and recognize a WhatsApp user in supported Business Platform flows even when a phone number is not the visible identifier. Number Checking remains a separate phone-list workflow.
The official definition
Meta’s developer presentation on WhatsApp usernames describes BSUID as a new backend identifier for users who adopt usernames. It is scoped to a business portfolio rather than being a public, global identity shared across every company.
Phone, username and BSUID are different keys
| Identifier | Scope | Main operational role |
|---|---|---|
| Phone number | Numbering plan and subscriber service | Calling, legacy contact and Number Checking input |
| Username | User-selected WhatsApp name | Display and discoverability |
| BSUID | User–business portfolio relationship | Backend messaging and webhook identity |
| CRM contact ID | One organization | Internal customer record |
Why a portfolio scope matters
The same person can have different BSUIDs when interacting with different business portfolios. A business therefore must not sell, exchange or treat BSUIDs as universal identity keys. Even inside a corporate group, portfolio boundaries and approved parent identifiers need explicit integration design.
Do not infer country from the BSUID prefix
The identifier format can contain a country component, but it does not prove present residence, citizenship, language or transaction market. Store business market and user preference from first-party evidence rather than deriving a personal profile from an opaque technical key.
How Number Checking fits
AIPUSH WS Number Checking accepts phone numbers in TXT and returns the fields defined by the selected task in Excel. It does not generate BSUIDs, read Business Platform webhooks or replace the integration’s contact book. A phone check and a webhook identity migration have different inputs, owners and controls.
Build a non-destructive identity crosswalk
Store crm_contact_id, phone_e164, bsuid, username, business_portfolio_id, observed_at and source as separate fields. Never overwrite the phone with a BSUID. When an update event or mapping conflict appears, preserve both values and route it to reconciliation.
Test migration with four cases
Exercise phone present/username absent, phone present/username present, phone unavailable/BSUID present, and identifier-change events. Verify inbound routing, outbound addressing, delivery status, suppression and audit logs. A happy-path API call is not enough.
Privacy and permission survive the migration
A new identifier does not renew consent, bypass opt-out or justify merging records. The business must carry permission and suppression across identifier changes, minimize retention and explain its processing. BSUID improves continuity; it does not confer ownership of the person.
