Embedded Signup v4: Meta’s Deprecation Banner Names v2 — the Table Also Ends v3

The deprecation banner on Meta’s Embedded Signup overview names one version: v2, gone on 8 October 2026. The versions table on the same documentation set lists v2, v3, and both public-preview lines as available until October 2026. Migrating to Embedded Signup v4 is not changing a version string in extras. For v4, extras is empty and products live in Facebook Login for Business.

Primary: Embedded Signup overview and WhatsApp versioning / Versions (both showing updated 24 July 2026 at fetch). Partner types that decide who bills after signup: Tech Provider vs Solution Partner. Buyer setup: how to get WhatsApp API.

Start here if you ship Embedded Signup

• If your snippet still sets version: "v2" (or omits v4 Login config), treat 8 October 2026 as a hard stop, not a warning.
• Do not assume “the banner only said v2” means v3 is safe. The versions table lists v3 and the preview lines until October 2026 as well.
• v4: create a new Facebook Login for Business configuration, select products, leave extras empty.
• v4 public preview still uses version: "v4-public-preview" if you are testing the preview — that is not production v4.
• Onboarding limits stay: 10 new customers / 7 days until Business Verification + App Review + Access Verification, then 200. More than 200/week needs Meta Business Partner.
• Ominiflow-hosted signup is the partner flow. You do not paste JS. White-label and reseller portals that embed their own button do.

The banner names v2. The table retires more.

Two pages, two levels of precision.

The overview opens with a single operational instruction: Embedded Signup v2 will be deprecated on 8 October 2026. Migrate to v4 before that date.

The versions table (latest version v4) lists:

If your runbook only patched v2 because that is what the red banner said, v3 integrations share the same month. Meta has not published a separate v3 calendar day on that table — only “October, 2026”. Plan the cutover as one migration to v4, not a two-step v2→v3→v4.

Why v4 is not a version-string change

On v2 and v3 you passed an extras object: setup/prefill, features, featureType, sometimes sessionInfoVersion, and a version key.

On v4 production, Meta’s documented extras block is:

extras: {} // The extras object is purposely empty for v4.

Product selection — Cloud API, Marketing Messages API for WhatsApp, Click-to-WhatsApp Ads, Conversions API (WhatsApp) — is done by creating a new Facebook Login for Business configuration and ticking the products. Selecting those products is what puts you on v4. Copy-pasting version: "v4" into an old extras blob is the failure mode the docs are written to prevent.

v4 also documents completion states v2 did not: users can finish with a verified number, an unverified number, or no phone number. Prefill can fill business information; screens are not skipped the way v2 allowed. Session info logging is sent for all flows. Those are behaviour changes in the callback your server already parses.

What still happens after the popup (unchanged jobs)

Embedded Signup still returns WABA ID, business phone number ID, and an exchangeable token code to the window that spawned the flow. Your server still must:

1. Exchange the code for a customer-scoped business token.
2. Register the business phone number for Cloud API.
3. Subscribe the app to webhooks on that WABA.
4. Share a credit line if you are a Solution Partner — Tech Providers do not. Clients add a payment method instead.

That last row is billing, not “more official.” Read it on Tech Provider vs Solution Partner before you promise “go live before they add a card.”

Limits the version bump does not lift

• 10 new customers per rolling 7 days by default. Completing Business Verification, App Review, and Access Verification raises that to 200. Above 200/week: apply to become a Meta Business Partner.
• WABAs originally created via the developer app cannot be selected in Embedded Signup.
• Customers own their assets and keep WhatsApp Manager access. You cannot lock that down.
• App Review advanced access is still required before you onboard real customers in live mode.

What Ominiflow customers actually click

If you create the WABA inside Ominiflow signup, you are not maintaining Embedded Signup JS. The partner hosts the flow, registers the number, and attaches the inbox. Typical go-live with complete Business Manager documents is 5–7 business days (longer if documents bounce).

If you are a reseller, agency, or product that embeds “Connect WhatsApp” on your own domain, you are the integrator. Ship v4 Login for Business before October 2026 or the button stops creating usable assets. Checklist: onboarding checklist · Cloud API get started: get started.

FAQ