Meta Embedded Signup Explained: Getting Your Own WhatsApp Business API Number in India
A business owner is told they need to "connect their WhatsApp number" to a piece of software, and a Meta-branded popup appears asking them to log in. It feels unfamiliar, maybe even a little suspicious, handing a business number over to some tool they just signed up for. Here's what that popup is actually doing, step by step.
What you're actually authorizing
Embedded Signup is Meta's own official flow, launched from inside a software provider's dashboard, where you log into your own Meta Business account, not the provider's, pick or create your Business Manager and WhatsApp Business Account, and verify the phone number with an OTP Meta sends directly to that number. The provider is granted permission to send and receive messages through the WhatsApp Cloud API for that number. Nobody ever sees or receives your personal WhatsApp app password, because the consumer WhatsApp app and this Business API authorization are two completely separate systems that don't share a login.
Before You Start
- Two-factor authentication enabled on your Meta Business Manager beforehand; the flow can fail partway through without it
- The number isn't currently linked to the personal WhatsApp app or another API provider, it has to be unlinked first or the signup will reject it
- Access to the OTP on that number, since Meta verifies it live during the flow
How to Connect Your WhatsApp Number to a Business Account
- Log into your own Meta or Facebook account inside the signup popup
- Create or pick your Meta Business Manager
- Create or select a WhatsApp Business Account inside it
- Enter the phone number you want to use and verify it with the OTP Meta sends to that number
- Confirm the permissions screen, which names the specific provider asking for access
What If It Asks for Business Verification, or the Signup Fails?
Two things trip people up here. Meta sometimes requires Business Verification on your Meta Business Manager before it'll hand out full WhatsApp API access, which can add a few extra days if you haven't done that before. And if your account has two-step verification enabled, which Meta recommends, you'll need that six-digit PIN during the flow. It isn't your WhatsApp password or an OTP. It's a separate PIN that exists so nobody who hijacks your SIM can take over the number.
Why this matters more than it sounds like it should
This is the actual mechanism that makes "your own number" a real, checkable fact rather than a sales claim. The number stays registered to your own Meta Business Manager. The software provider only ever holds API-level permission to send and receive on it, not ownership of the account itself.
This exact flow is what's behind the "connect your own WhatsApp number" step in ZiroWait's onboarding, and the setup page walks through it live rather than just describing it, so you can see what you're actually authorizing before you click confirm.