BSP vs Tech Provider vs Cloud API
A BSP is a WhatsApp Business Solution Partner: a company Meta has approved to resell WhatsApp access, extend credit and invoice you directly. A Tech Provider builds software on Meta's Cloud API but does not invoice Meta's charges, and a direct integration means your own team calls the Cloud API with no provider in between.
What is a BSP, or Solution Partner?
BSP stands for Business Solution Provider, the older name that most people still use. In Meta's current documentation the term is Solution Partner. According to Meta's solution provider overview, Solution Partners are Meta Business Partners that provide a full range of services to clients: messaging, billing, integration support and customer support.
The feature that sets them apart is the credit line.
Solution Partners have credit lines which can be extended to clients who they bring on board, thus removing the need for those clients to enter their own payment method during the onboarding process.
Meta's credit-line page adds the liability side. The partner is the "Bill To Party" for every business sharing its credit line, and it pays Meta for all of that spend. This is why a Solution Partner can invoice you for messages: businesses pay the partner, and the partner receives an aggregated invoice from Meta.
What is a Tech Provider?
A Tech Provider is a software company that builds on the WhatsApp Business Platform and helps businesses onboard to it. It does not hold a credit line. Meta's overview is plain about the consequence.
Unlike Solution Partners, however, Tech Providers do not have credit lines. Instead, clients onboarded by Tech Providers must provide their own payment method after onboarding is complete. Meta will then bill these clients for API usage, and the Tech Provider will bill for other services.
So with a Tech Provider you hold a Meta account, add your own card or other payment method, and pay Meta for messages. The provider's invoice covers only its own service. Meta also notes that becoming a Solution Partner is a lengthy process, and suggests Tech Provider status for anyone who does not need a credit line or direct invoicing.
WhaBuzz is a Tech Provider. Your numbers connect through Meta's own signup popup, called Embedded Signup.
What does going direct to the Cloud API mean?
Going direct means your business owns the relationship with Meta and no provider sits between you and the API. You create a Meta app, a business portfolio and a WhatsApp Business account, register a number, handle webhooks yourself and send calls straight to Meta's Graph API.
Meta's pricing page uses the phrase "Solution Provider or directly-integrated businesses" when it describes who needs a payment method on file. A directly-integrated business pays Meta, like a client of a Tech Provider, and has no one else to pay for the API itself.
What you give up is everything a provider would build around it: retries for your webhooks, a log of every request, replay, signature handling, multi-number onboarding flows, and someone to ask. What you gain is a smaller moving-parts count and no third-party fee.
Who bills what under each model?
Based on Meta's solution provider documentation, the split looks like this.
| Solution Partner (BSP) | Tech Provider | Direct to Cloud API | |
|---|---|---|---|
| Who pays Meta for messages | The partner, through its credit line | You, on your Meta account | You, on your Meta account |
| Who invoices you for messages | The partner, at a price it sets | Meta | Meta |
| Provider's own fee | Set by the partner | Set by the provider | None |
| Payment method needed on your Meta account | Not at onboarding | Yes | Yes |
Meta's rate for India from 1 Oct 2026 is ₹0.8631 for marketing and ₹0.115 for utility, authentication and service messages, per Meta's rate card. Under a credit line, the partner can bill you more than that, the same, or bundle it into a plan. Under the other two models, Meta bills Meta's rate. The full arithmetic is in the India pricing post.
When is going direct better?
Direct is the right choice more often than providers like to admit. Go direct when:
- You run one or two numbers and your team already writes and operates backend services.
- You want no third-party fee and no third party in the message path.
- Your compliance team requires that only Meta and you handle the data.
- You need a Meta feature on the day it ships and your provider has not added it.
A provider earns its fee when you run many numbers or many customers, when you do not want to operate webhook infrastructure, or when you need onboarding, support or a credit line. The credit line matters if you cannot or do not want to hold a payment method with Meta, which only a Solution Partner can offer.
WhaBuzz sits in between: Meta's own request and response bodies, unchanged, with delivery and logging added. If you outgrow it, your code is already shaped like the Cloud API. See the comparison with Meta's Cloud API for the axes side by side.
Which model suits an Indian business?
For a small Indian team, the practical questions are payment and ongoing cost. Meta is moving eligible Indian customers to INR billing: its pricing page says all Messaging accounts must be migrated to INR by 31 Dec 2026. That affects any model where you hold the Meta account, so Tech Provider and direct customers should plan for it.
If you want a single vendor invoice and no Meta payment method to manage, a Solution Partner fits. If you want to see Meta's charges at Meta's rate and keep your fee predictable, a Tech Provider or direct fits. WhaBuzz is the Tech Provider option, at ₹500 a month for the first number and ₹250 for each additional number, excluding GST, per the pricing docs. It went live on 16 Oct 2026, so it has no long track record. Solution Partners with years of operation can claim one.
Frequently asked questions
Is a BSP the same as a Solution Partner?
Yes, in everyday use. BSP is the older term. Meta's current documentation says Solution Partner.
Can a Tech Provider give me a credit line?
No. According to Meta, Tech Providers do not have credit lines, and their clients must add their own payment method so Meta can bill them.
Do I pay more using a Tech Provider than going direct?
You pay the provider's own fee on top of Meta's charges. Going direct has no provider fee, but you build and run the delivery layer yourself.
Can I move between models later?
Often yes, if the WhatsApp Business account is yours. WhaBuzz connects to the account, not to a provider, and its migration guide lists what carries over. Check your current provider's terms first.
Related reading
- Pricing and Numbers cover what WhaBuzz bills and how connection works.
- WhatsApp Business API pricing in India works through a month of Meta's charges.
- Webhook reliability shows what a provider builds around the raw API.
- Provider comparisons and the WhatsApp API overview.
- Meta's sources: Solution provider overview and credit lines, checked 16 Oct 2026.