On-Behalf-Of account ownership model deprecation | Developer Documentation
Meta provider reference: the historical Meta On-Behalf-Of ownership model. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and Secret.
Start with the relevant ChatArchitect customer guide and the service API quick start. The original reference is retained below; its parameters, programme requirements and optional capabilities require checking in Meta documentation for that separate implementation.
On-Behalf-Of account ownership model deprecation
Updated: Nov 14, 2025
We have deprecated the On-Behalf-Of (“OBO”) account ownership model and replaced it with partner-initiated WABA creation. All existing WABAs created under the OBO model should have been transferred to business customers by October 1, 2025. Post 1st October 2025, all the eligible OBO accounts will be auto-migrated in batches through the end of 2025.
Deprecation timeline
Payment methods
Partner-initiated WABA creation does not support automatic payment setup. Instead, you must share your credit line with the business customer via the API. See Partner-initiated WABA creation for details.
Multi-Partner Solutions
Business customers cannot be onboarded to a Multi-Partner Solution as part of the
partner-initiated WABA creation process, but can be added to an MPS afterwards. See Partner-initiated WABA creation for details.
Marketing Messages API for WhatsApp
Existing OBO model WABAs need to be transferred to business customers if you want to use them with the Marketing Messages API for WhatsApp, but this can be done as part of the Marketing Messages API for WhatsApp onboarding process.
No comments to display
No comments to display