360dialog WhatsApp BSUID Migration

360dialog, a direct WhatsApp Business Solution Provider, passes Meta WhatsApp Cloud API payloads with minimal transformation. This means your infrastructure must handle the BSUID fields that Meta is introducing.

Key Changes

The contacts[0].user_id field in the inbound message payload will contain the Business Scoped User ID for users who contact you via a WhatsApp username. Your webhook must be updated to capture and store this identifier.

Raw Meta Payload Structure

{"contacts":[{"profile":{"name":"User"},"wa_id":"1234567890","user_id":"BSUID.a1b2c3d4e5f6"}],"messages":[{"from":"BSUID.a1b2c3d4e5f6","text":{"body":"Hello"}}]}

Migration Steps

Update your webhook parser to extract contacts[0].user_id
Add a bsuid column to your user/contact database table
Modify your message processing pipeline to use BSUID as the primary lookup key when available
Implement a backfill strategy to link existing wa_id records to new BSUID entries during the dual-mode window

Testing with 360dialog

Use 360dialog's webhook simulator or the RezervSpot BSUID Audit Tool to validate your endpoint before the Q4 2026 cutoff.