Skip to content

Tech Provider

Meta's partner role for software companies that onboard client businesses to the Cloud API through Embedded Signup, without a credit line or direct billing.

Also called: WhatsApp Tech Provider · Meta Tech Provider · ISV Tech Provider

Reviewed

Interactive lab

Hands on: use the controls to explore. Anything that plays on its own pauses while you are working inside it.

Tick off the Tech Provider launch list

9/9

ticked

Required
7 / 7
Optional
2 / 2

Ready to onboard your first client

Every item ticked.

Everything a software company needs before its first client goes live as a Tech Provider. Required items are marked; tick them to fill the ring and see what is still blocking launch.

Ready to onboard your first client. 9 of 9 ticked.

01What is a Tech Provider?

A Tech Provider is one of the partner roles Meta defines on the WhatsApp Business Platform: a business — typically a SaaS company, CRM, e-commerce or booking platform — whose Meta app onboards other businesses (its clients) and uses the Cloud API on their WhatsApp Business Accounts. Clients connect through the Tech Provider's Embedded Signup, which creates or selects the client's accounts in the client's own business portfolio and shares them with the Tech Provider's app.

The role is defined largely by what it does not include. Unlike a Solution Partner (the role often called a Business Solution Provider, or BSP), a Tech Provider has no credit line, cannot let clients skip adding a payment method and does not invoice clients for API usage: the client adds its own card or payment method and Meta bills the client for messages, while the Tech Provider bills for its software. Tech Providers do get Direct Support, and they can partner with a Solution Partner in a Multi-Partner Solution when clients need the Solution Partner's credit line.

Getting there is lighter than becoming a Solution Partner. The business verifies its portfolio, builds a Business-type app with the WhatsApp use case, and passes App Review for Advanced Access to whatsapp_business_messaging and whatsapp_business_management; the separate access verification step was dropped in October 2025. A Tech Provider that later shows real scale can upgrade to Tech Partner, which adds Meta Business Partner status and its programme benefits.

Key takeaways

  • A Tech Provider is a software company Meta allows to onboard other businesses to the Cloud API and message on their behalf.
  • Becoming one takes a verified business portfolio and App Review approval for Advanced Access to the two WhatsApp permissions.
  • Tech Providers have no credit line: clients add their own payment method and Meta bills them for messages directly.
  • Meta tells Tech Providers to use business tokens exclusively, obtained by exchanging each client's Embedded Signup code.
  • A Tech Provider that meets Meta's volume, client and quality bars can upgrade to Tech Partner and join the Meta Business Partner programme.

02 · How it works, step by step

How does a Tech Provider work?

  1. Step 1

    Verify the business

    Complete business verification for the company's portfolio in Meta Business Suite. App Review cannot be submitted until it is done.

  2. Step 2

    Create the app and build the integration

    Create a Business-type app with the WhatsApp use case, build sending and template management on your own test number, and implement Embedded Signup.

  3. Step 3

    Pass App Review for Advanced Access

    Submit screencasts showing a message sent from your app and a template being created. Approval grants Advanced Access to whatsapp_business_messaging and whatsapp_business_management.

  4. Step 4

    Onboard clients with business tokens

    Exchange each client's Embedded Signup code for a business token, subscribe your app to the client's account, register the number and send.

  5. Step 5

    Make sure the client can pay

    Prompt the client to add a payment method in Meta Business Suite after signup; charged messages fail without one. Or bring in a Solution Partner's credit line through a Multi-Partner Solution.

03Why does a Tech Provider matter?

For a software company, the Tech Provider role is the shortest legitimate path to putting WhatsApp inside its product for many customers. Without it, every customer has to wire its own Meta app and tokens, or the company has to resell a BSP's platform. Understanding the role's limits matters just as much: because there is no credit line, the onboarding flow must include the client's payment method; because tokens are per client, the backend must store and refresh business tokens per account; and because App Review gates Advanced Access, a launch date depends on Meta's review rather than on code.

04A Tech Provider: key facts and limits

Business verification
Required before App Review
Permissions (Advanced Access)
whatsapp_business_messaging, whatsapp_business_management
Access verification
No longer required since October 2025
Credit line
None; clients add their own payment method
Who bills message charges
Meta bills the client directly
Token type
Business tokens, one per client
Direct Support
Yes
Meta Business Partner
No, unless upgraded to Tech Partner

05A Tech Provider in code

# After Embedded Signup returns a code, swap it for the client's business token
curl -G "https://graph.facebook.com/v26.0/oauth/access_token" \
  --data-urlencode "client_id={APP_ID}" \
  --data-urlencode "client_secret={APP_SECRET}" \
  --data-urlencode "code={CODE_FROM_EMBEDDED_SIGNUP}"

Exchange the code server-side; never expose the app secret in the browser.

06 · Common mistakes, and the fix

Common mistakes with a Tech Provider

  • Skipping the payment-method step

    Without a credit line, a client that never adds a payment method cannot send charged messages. Make it a required onboarding step and check it before the first campaign.

  • Using one system-user token for every client

    Meta says Tech Providers should use business tokens exclusively. Exchange and store one per client, so revoking one client never breaks the others.

  • Submitting App Review too early

    Reviewers need to see the real flow. Record screencasts of a working send and template creation from your app, on a test number, with English labels or captions.

  • Promising to invoice clients for WhatsApp messages

    Only Solution Partners bill clients for API usage. A Tech Provider charges for its own software; message charges come from Meta.

07Example: A Pune clinic-software company goes live

A Pune company sells appointment software to 300 clinics and wants each clinic to send reminders from its own WhatsApp number. Its portfolio is verified in a week; App Review approves Advanced Access after a second submission that shows the template-creation screencast more clearly. It adds a "Connect WhatsApp" button that opens Embedded Signup, stores a business token per clinic, and adds a final onboarding step asking the clinic to add a payment method in Meta Business Suite. Clinics pay Meta for messages on their own invoice and pay the software company its subscription; nothing about message billing passes through the software company.

08Tech Provider FAQs

What is the difference between a Tech Provider and a Solution Partner?+
Billing and partner status. A Solution Partner has a credit line, can invoice clients for API usage and is a Meta Business Partner; a Tech Provider's clients pay Meta directly, and it is not a Meta Business Partner unless it upgrades.
How do I become a WhatsApp Tech Provider?+
Verify your business, then pass App Review. Build a Business-type app with the WhatsApp use case and get Advanced Access to whatsapp_business_messaging and whatsapp_business_management; then onboard clients through Embedded Signup.
Who pays Meta for messages sent by a Tech Provider's clients?+
The client does. It adds its own payment method after onboarding and Meta bills it for messages; the Tech Provider charges separately for its own software.
Can a Tech Provider become a Tech Partner?+
Yes, once it meets Meta's thresholds. These include message or call volume, at least 10 active clients and a strong quality rating, followed by a Meta Business Partner application and programme enrolment.

09 · Tips from the bench

Best practices for a Tech Provider

  • Start business verification on day one; it is usually the longest wait.
  • Run debug_token on each new business token and alert if a client's account is missing from granular_scopes.
  • Decide early whether you need a Solution Partner in a Multi-Partner Solution for clients that cannot add a card.

See InfiQ pricing

From definition to your first message

InfiQ is an official Meta Business Partner. Start a 7-day free trial — no card needed — and see this running on your own number.

Start free trialBrowse all 550 terms