Updated on October 25, 2026
A WhatsApp BSP (Business Solution Provider) is what the market calls a company that resells and operates the official WhatsApp Business API for other businesses. In Meta’s current documentation, that role is called Solution Partner, and it sits alongside two other partner types: Tech Provider and Tech Partner. The practical difference comes down to who pays Meta for messages, whether the partner can extend a credit line to clients, and which Meta programs it can join.
This article explains each type based on Meta’s partner documentation, shows what changes for the business that hires one, and lists the questions worth asking before you sign with any intermediary.
Why the WhatsApp Business API has partners
Cloud API is a Meta product, but Meta does not directly serve most of the businesses on the platform. Meta’s documentation defines partners as companies that deploy value-added solutions “as WhatsApp authorized service providers” on behalf of their clients.
In practice, a partner handles one or more of these pieces:
- the app registered with Meta, with approved permissions;
- the client signup flow (Embedded Signup);
- tokens, webhooks and sending infrastructure;
- billing, support and sometimes a ready-made product (CRM, chatbot, campaign platform).
If you have an engineering team, you can integrate directly with Meta with no partner at all. Here the focus is on decoding the labels you run into when you research vendors.
Meta’s three partner types
Solution Partner (the “BSP”)
Solution Partners are Meta Business Partners that offer the full platform package: messaging, billing, integration support and customer support. What sets them apart is the credit line. With it, clients don’t need to add their own payment method during onboarding, and the partner can invoice API usage directly.
Meta warns that becoming a Solution Partner is “a lengthy process” and suggests the Tech Provider route if you don’t need a credit line or direct invoicing of API usage.
Tech Provider
A Tech Provider can also offer every platform service, on its own or together with a Solution Partner. The difference is that it has no credit line: after onboarding, the client adds its own payment method, Meta bills the client directly for API usage, and the Tech Provider bills separately for its own services.
Tech Partner
A Tech Partner is a Tech Provider that also is, or can become, a Meta Business Partner. The upgrade unlocks the partner accelerator program and benefits such as training, analytics reports and client matching, according to Upgrading to a Tech Partner.
Comparison
| Solution Partner | Tech Provider | Tech Partner | |
|---|---|---|---|
| Offers full platform services | Yes | Yes | Yes |
| Has a credit line | Yes | No | No |
| Client skips payment method setup | Yes | No | No |
| Invoices API usage directly to the client | Yes | No (Meta bills the client) | No (Meta bills the client) |
| Is a Meta Business Partner | Yes | No | Yes |
| Eligible for the accelerator program | Yes | No | Yes |
| Access to Direct Support | Yes | Yes | Yes |
Source: Partners, Meta documentation.
There is also a fourth case Meta calls “other partners”: agencies that only use Meta Business Suite and don’t need API access. They just need a verified business portfolio, and the client shares its WhatsApp account with them.
How a company becomes a Tech Provider
The path is described in Become a Tech Provider:
- App and portfolio. Create a Meta app with the WhatsApp use case, connected to a business portfolio.
- Business verification. Required before App Review.
- App Review. Submit two videos: one showing a message sent from your app and received in WhatsApp, and one showing a template being created. A screen recording of the dashboard cURL script or of WhatsApp Manager is accepted as an alternative.
- Advanced access. Request Advanced access to
whatsapp_business_messagingandwhatsapp_business_management. Without it, calls on accounts owned by other businesses return error200.
You can also go through the process together with a Solution Partner by entering its app ID to create a joint solution (a Multi-Partner Solution). In that setup, the Solution Partner can extend its credit line to the clients the Tech Provider brings in.
Onboarding limits
Embedded Signup caps how many new clients a partner can onboard per week:
| Partner status | New clients per rolling 7 days |
|---|---|
| Default | 10 |
| Business Verification, App Review and Access Verification completed | 200 |
| More than 200 per week | Must become a Meta Business Partner |
Requirements to become a Tech Partner
To apply for the upgrade, a Tech Provider must, according to Meta:
- have completed every Tech Provider step;
- average at least 2,500 daily messages (sent or received) over the last 7 days, or average 200 daily calls over the same period;
- have 10 or more active clients (that sent at least one message in the last 30 days);
- keep a business phone number quality rating of 90% or better.
The process includes applying to be a Meta Business Partner with the WhatsApp specialty, signing up for the Partner Portal and enrolling in the Business Messaging Accelerate program. Meta estimates “a few weeks” to get through the approvals.
What changes for the business that hires a partner
Who pays Meta
This is the most important question. With a Solution Partner using its credit line, message costs show up on the partner’s invoice. With a Tech Provider, Meta requires the client to add a credit card to its own account and bills it directly. That affects reconciliation, currency and the risk of an outage: since October 1, 2026, the pricing page warns that accounts without a payment method stop getting service messages delivered once the free monthly tier is used up.
Tokens and access to your accounts
Meta tells Tech Providers and Tech Partners to use business tokens exclusively. These are scoped to the single client who completed Embedded Signup. Solution Partners use a system user token only to share their credit line. If you integrate directly with no partner, you use your own system user token, as covered in permanent WhatsApp API token.
The assets stay yours
According to the Embedded Signup documentation, clients onboarded through that flow own all of their WhatsApp assets and have full access to WhatsApp Manager, and the partner cannot restrict that access. In practice, the number, the portfolio and the verification stay under your company’s name.
Several partners on the same number
Under the new account model, rolling out between September 23 and mid-October 2026, the old WABA splits into a WhatsApp account (number and identity) and a Messaging account (templates, billing and webhooks). According to Updates to WhatsApp Business accounts, a single number can be shared with several partners, each with its own Messaging account and isolated billing. One exception: if a partner attaches its credit line to a client-owned Messaging account, that account can’t be shared with another partner. Switching or adding vendors is now simpler; see how to switch WhatsApp API providers without losing your number.
Coexistence needs a partner
Connecting a number that is already on the WhatsApp Business app to the API, while keeping the app on the phone, is done through a partner’s Embedded Signup. See what syncs in WhatsApp coexistence.
Questions to ask any vendor
Before you sign, get written answers to these:
- Who pays Meta for messages: me, with a card on my own account, or you, on your invoice?
- Are Meta’s rates passed through at the official list price or with a markup? In which currency?
- Will the portfolio, number and account be under my company’s name?
- Do you support coexistence with the WhatsApp Business app?
- Do webhooks arrive in Meta’s format or in a proprietary one?
- How do I leave: can I move the number to another vendor or integrate directly?
The article how to choose a WhatsApp API provider turns these questions into a 10-point checklist.
What about Vectalk?
Vectalk is a managed proxy for Meta’s official WhatsApp Cloud API. Your application talks to Vectalk using the same payloads as Meta, and webhooks follow the format in Meta’s documentation. For billing, you pay Vectalk and Vectalk pays Meta, with no card on file at Meta. Vectalk also supports coexistence, so the number keeps working in the WhatsApp Business app and on the API at the same time.
To explore the API, read the documentation or create your account. For sales questions, use the contact page.
Frequently asked questions
Are a BSP and a Solution Partner the same thing?
In practice, yes. “BSP” is the term the market uses; Meta’s current documentation calls this partner type a Solution Partner. What defines it is being a Meta Business Partner with a credit line it can extend to clients.
Do I need a partner to use the WhatsApp Business API?
No. A business can create its own Meta app and integrate directly with a system user token. A partner makes sense when you don’t want to run the app, tokens, webhooks and billing yourself, or when you need something that depends on one, such as coexistence. See how to get access to the WhatsApp API.
Is a Tech Provider worse than a Solution Partner?
Not necessarily. Both can offer the same services and both get Meta’s Direct Support. The core difference is billing: with a Tech Provider, Meta bills you directly; with a Solution Partner using a credit line, the partner invoices you.
How do I know which partner type my vendor is?
Ask, and check the billing flow. If after onboarding you have to add a card to your own Meta account, API usage is billed by Meta directly. If message costs show up on the vendor’s invoice, there is a credit line or another pass-through arrangement.
Can I change partners later?
Yes. Under the new account model, you can add a partner to the same number without migrating it. The guide on switching WhatsApp API providers covers what to watch for with templates and billing.
Official sources consulted on October 25, 2026: Partners overview, Become a Tech Provider, Upgrading to a Tech Partner, Embedded Signup, Access tokens, Updates to WhatsApp Business accounts, Pricing.