WhatsApp Embedded Signup: connecting a customer's number without losing them
Last updated 23 October 2026
Short version. Embedded Signup is the Meta-hosted popup that lets one of your customers connect their WhatsApp number to your software without leaving your app and without you ever touching their credentials. It is the difference between onboarding that takes a minute and onboarding that takes a week of emails. If you build anything multi-tenant on WhatsApp, you need it.
And if your flow broke recently: Embedded Signup v2 and v3 were deprecated on 15 October 2026, including their public preview versions. v4 is the one to be on.
What is Embedded Signup?
Meta describes it as "an authentication and authorization interface that is compatible with desktop and mobile". In practice it is a popup you launch from your own page. Your customer signs in to their own Meta account inside it, picks or creates a WhatsApp Business Account and a phone number, verifies that number, and grants your app permission to send messages on it.
What comes back to you is the set of identifiers you need to operate that number: the WhatsApp Business Account ID and the phone number ID. From there your software can send and receive on the customer's behalf.
The part that matters commercially: the customer's assets stay the customer's. They own the WhatsApp Business Account. You are granted access to it, and access can be revoked by them. That is the right shape for a product somebody might one day want to leave.
Why does it exist?
Because the alternative is appalling. Without it, connecting a customer's number means walking a non-technical business owner through the Meta Business Suite: create a business portfolio, verify the business, create a WhatsApp Business Account, add a phone number, verify it by SMS, find the right settings panel, generate a token, and send that token to you over email.
Every one of those steps is a place somebody stops. Worse, the last one trains your customers to paste credentials into email, which is a habit you do not want to be responsible for teaching.
We shipped Embedded Signup from day one for exactly this reason. A shop owner who has already decided to try something will not survive a seven-step configuration in a dashboard they have never seen.
What do you need before you can use it?
Four things, and the third is the one that takes time.
A Meta app with WhatsApp added as a product.
Tech Provider or Solution Partner status. These are different programmes with different obligations, covered below.
Advanced access for two permissions: whatsapp_business_management and whatsapp_business_messaging. Meta is unambiguous here: "You will not be able to onboard business customers until your app has been approved for advanced access for each of the permissions it requires." This is App Review, with the screencast and the written use case, and it is not same-day. Budget for it at the start of a project rather than the week you planned to launch.
A verified business portfolio. The verification is on your own Meta business, not your customer's.
Tech Provider or Solution Partner?
This choice decides who pays Meta, and it has consequences well beyond billing.
As a Tech Provider, your onboarded customers add their own payment method to their own Messaging account, and messaging begins once they have. Meta bills them directly, at Meta's published rates. You are not in the money path at all.
As a Solution Partner, you hold a line of credit with Meta, accept the Credit Allocation API terms in Business Settings, and share that credit line with each customer as part of onboarding. You are billed by Meta and you bill your customers.
Solution Partner sounds like the more serious option, and for a large BSP it is. But understand what sharing a credit line does: it creates an allocation into the customer's Meta business portfolio that, per Meta's own documentation, only the party that granted it can revoke. A customer who later wants to attach their own payment method, or move to another provider, cannot simply do it — somebody at your company has to act first.
We have been on the receiving end of that, and wrote up what it takes to get such an allocation removed, including the wording that eventually worked. It is the reason Jabee is a Tech Provider: our customers get billed by Meta directly, and nothing of ours sits inside their portfolio that only we can remove.
Which version should you be on?
v4. Meta deprecated Embedded Signup v2 and v3 on 15 October 2026, "including their public preview versions".
If you integrated in 2024 or 2025 and have not touched it since, this is worth checking today rather than when a customer reports that the popup does nothing. Deprecation of an onboarding flow fails in the least visible place in your product: not for existing users, who are already connected, but for new ones, who simply do not arrive.
What goes wrong
The failures we have hit or watched others hit, in rough order of frequency.
App Review not approved yet. Everything works in development mode with your own test number, and nothing works for a real customer. The flow completes and the permissions are not there. This is the single most common cause of "Embedded Signup is broken".
The number is already on the WhatsApp Business app. A number signed in to the consumer-facing WhatsApp Business app cannot be moved to the API without being removed from it first, and that move is one-way with no route back. Most small businesses in this market are using their main number on that app, which is why so many of them start with a spare SIM.
No payment method on the customer's side. As a Tech Provider, onboarding can complete successfully and messaging still not work, because the customer has not added a card to their Messaging account. Worth detecting and saying plainly, because from the customer's point of view they finished your setup and nothing happened.
Treating the popup result as the end of the job. It is the start. You still have to subscribe your app to the customer's WhatsApp Business Account webhooks, register the phone number, and store the identifiers against your tenant. If you skip the webhook subscription, messages to that number arrive nowhere — see handling Cloud API webhooks in Node for the receiving side.
Assuming the display name is live. Meta can approve a display name and customers will still see the old one until the number is re-registered. The API reports success and the phone shows otherwise, which is a confusing afternoon the first time it happens.
Frequently asked questions
What is WhatsApp Embedded Signup? A Meta-hosted popup that lets a business connect its own WhatsApp number to your software without leaving your app. The customer signs in to their own Meta account, selects or creates a WhatsApp Business Account and phone number, and grants your app permission to message on it. You never handle their credentials.
Do I need to be a Tech Provider to use Embedded Signup? You need to be either a Tech Provider or a Solution Partner. As a Tech Provider your customers add their own payment method and Meta bills them directly. As a Solution Partner you hold a line of credit with Meta and share it with each customer during onboarding.
Which version of Embedded Signup should I use? v4. Meta deprecated v2 and v3 on 15 October 2026, including their public preview versions.
What permissions does Embedded Signup need? whatsapp_business_management and whatsapp_business_messaging, both at advanced access. Meta will not let you onboard business customers until your app has been approved for advanced access on every permission it requires, which means going through App Review.
Why does Embedded Signup work for me but not for my customers? Almost always because your app has not been approved for advanced access yet. In development mode everything works with your own test number and nothing works for a real customer.
Can a business use its existing WhatsApp number? Only if that number is not currently signed in to the WhatsApp Business app. Moving a number onto the API means removing it from that app first, and the move is one way with no route back, so many businesses start with a spare SIM.
Sources
- Meta, Embedded Signup overview: what the flow is, the v2 and v3 deprecation on 15 October 2026, Tech Provider versus Solution Partner obligations, and the advanced-access requirement for whatsapp_business_management and whatsapp_business_messaging. Read 23 October 2026.
- Meta, Embedded Signup implementation. Read 23 October 2026.
Written by Mu'men Tayyem, founder of M4B1 in Dubai. These are notes from building Jabee, a WhatsApp AI assistant that answers customers from a business's own website and calls the business's own APIs as agent tools.