AtServiceTech

WHATSAPP · GUIDE

Become a WhatsApp Tech Provider: Meta Setup Steps

A business messaging SaaS that onboards multiple customers should use Meta's partner onboarding path, not a single developer test number shared across clients. Evaluate the Tech Provider model first and confirm Meta's current eligibility requirements before building production onboarding.

Choose your provider model

Meta describes Tech Providers as businesses that offer WhatsApp services to client businesses. Client businesses onboarded by a Tech Provider generally add their own payment method and Meta bills their WhatsApp usage; the provider can bill separately for its own software or services. A Solution Partner model includes additional partner capabilities such as credit lines and direct billing for WhatsApp usage, and has separate qualification requirements.

  • Start with the Tech Provider path unless AtServiceTech specifically needs Solution Partner credit-line and WhatsApp usage billing features.
  • Do not tell customers that AtServiceTech can waive Meta billing or provide a shared credit line unless the required Meta partner status and access are approved.
  • Provider terms, account features, verification, and limits can change; confirm current requirements in Meta's partner onboarding before implementation.

Prepare Meta business and developer accounts

Keep AtServiceTech's own legal business identity separate from the businesses that will connect to the platform. Meta partner verification and customer onboarding are different processes: verifying AtServiceTech does not verify each customer's business.

Steps

  1. Create or select the AtServiceTech Meta Business Portfolio and keep its business details, domain, and contact information accurate.
  2. Register a Meta developer account and create an app using the WhatsApp business messaging use case.
  3. Configure the app for Embedded Signup v4 and select only the WhatsApp products and permissions needed for the product.
  4. Complete Meta's provider onboarding and business verification steps for AtServiceTech.
  5. Request App Review and Advanced Access for the required WhatsApp business messaging and management permissions; provide accurate product screencasts, test credentials, privacy policy, and data-handling disclosures requested by Meta.
  6. Test onboarding and messaging with Meta's test assets and approved accounts before accepting customer production connections.
  • Meta currently documents whatsapp_business_messaging and whatsapp_business_management for Cloud API-related messaging and management scenarios; request only the permissions required by the selected onboarding products.
  • Build and publish a privacy policy that explains what WhatsApp account, phone, message, and webhook data the service processes, why it is used, retention, support access, and deletion/revocation procedures.

Provider approval is a launch gate

Do not expose a production Connect WhatsApp button before Meta has approved the required permissions and provider access, and the server-side token exchange, webhook verification, tenant isolation, and deletion paths have passed security testing.

  • Meta's Partners overview explains Tech Providers, Solution Partners, and client onboarding.
  • Meta's Tech Provider onboarding is the authoritative source for current enrollment steps.
  • The dashboard currently says Coming soon because these prerequisites and the production integration are not complete.