Meta asks me to verify a new device or location. What now?

In short: this is Meta protecting your business portfolio, not a refusal of your number for Coexistence. On the same computer and browser, open business.facebook.com, complete the verification Meta asks for, wait a few minutes and connect again. Nothing was authorized, and the attempt cost nothing.

ZapClaw connects your number to the official WhatsApp API through Coexistence, and the app stays on your phone.

Start for free

What Meta shows

All three usually point to the same check, and the steps below clear it.

Why it happens

When you sign in to Facebook from a device, browser or location Meta does not recognize, Meta asks you to prove it is you before that login can act on your business portfolio. For a short time after a new login it also pauses some business actions, and connecting a number to an app is one of them. The check is about your Facebook login, not about your number.

How to clear it

  1. On the same computer and browser you use for ZapClaw, open business.facebook.com.
  2. Enter the business portfolio you are connecting and complete the verification Meta asks for (usually a code). Meta may also offer to approve the login from a phone or computer where you are already signed in.
  3. Make sure two-factor authentication is on in your personal Facebook account, under Accounts Center > Password and security. The connection needs it, and Meta may ask for it right after this check.
  4. Wait a few minutes before you try again. Meta asks for a pause after a new login and does not say how long it lasts.
  5. Reload ZapClaw and click Connect WhatsApp again.

Do every step in the same browser: the check is about the device and browser you are using, so verifying in a different browser may not clear this one.

If the Next button keeps spinning

A pending check like this one can leave Meta's Next button spinning with no message. Close Meta's window, follow the steps above and start the connection again. Closing the window is safe: ZapClaw only receives access when Meta's window finishes.

If it keeps happening

All the requirements are on What you need to connect.