AtServiceTech

WHATSAPP · GUIDE

WhatsApp Embedded Signup v4: Client Onboarding Steps

Embedded Signup lets an authorized SaaS provider launch a Meta onboarding flow from its own portal. The customer signs in to Meta, selects or creates business assets, accepts applicable terms, and grants access. Your application must securely finish the server-side exchange and account registration after the browser flow returns.

Configure Embedded Signup v4 in Meta

Meta's current documentation marks Embedded Signup v2 and v3 as deprecated on October 15, 2026. Start new implementations with v4 and recheck Meta's version notes before launch.

Steps

  1. In the Meta developer app, configure Facebook Login for Business for Embedded Signup and choose the WhatsApp Cloud API product flow.
  2. Select the assets and permissions the customer must authorize. Request only the features AtServiceTech will actually provide.
  3. Configure allowed domains, redirect/origin settings, app mode, privacy policy, and callback handling for the production and development environments.
  4. Load Meta's supported JavaScript SDK and launch the signup flow only after an authenticated AtServiceTech workspace administrator clicks Connect WhatsApp.
  5. Handle cancel, error, and success outcomes explicitly; never treat closing the popup as a successful connection.

Complete the server-side connection

The browser flow returns an exchangeable authorization code and business asset identifiers. The code is not a permanent access token. Send the code to your own backend over an authenticated, CSRF-protected session, then exchange it with Meta from the server.

Steps

  1. Validate the signed-in workspace, user permission to manage messaging, and a single-use state/nonce before accepting the callback.
  2. Send the authorization code from the browser to a same-origin backend endpoint; do not put Meta app secrets in frontend code.
  3. Exchange the code server-to-server for the customer-scoped business token and store it encrypted in a secret store or encrypted database field.
  4. For standard Cloud API onboarding, complete the required phone-number registration step. Follow the separate Meta flow for WhatsApp Business app coexistence if you intentionally support it.
  5. Subscribe the app to the customer's messaging account webhooks and persist the returned account and phone identifiers against the correct workspace.
  6. Confirm onboarding only after all required post-flow calls succeed. If one fails, show a pending/needs-attention state and provide a safe retry path without duplicating connection records.
  • Never return access tokens to the browser, include them in logs, or reuse one customer's token for another customer.
  • Meta's Embedded Signup overview and implementation guide describe the flow and server-side post-onboarding requirements.

Keep account identifiers separate

Meta's WhatsApp account model is evolving. Do not assume one WABA identifier represents every asset forever. Store the WhatsApp account identity, messaging account identity, phone-number ID, and displayed phone number in separate fields; use the identifiers required by each current API operation.

  • Keep the original provider response and onboarding event metadata needed to diagnose connection issues, but exclude secrets from that audit data.
  • Treat the current Meta account-model documentation as versioned platform behavior and keep API calls adaptable to account-model changes.
  • See Meta's WhatsApp account model updates.