WhatsApp Solution Partner vs Tech Provider: What Meta Actually Means

Short answer: Both a Solution Partner and a Tech Provider can offer the full range of WhatsApp Business Platform services. The difference is financial, not technical. A Solution Partner is a Meta Business Partner that can extend a credit line to clients and invoice them directly for API usage. A Tech Provider has no credit line and cannot directly invoice for API usage, so the client attaches their own payment method to Meta. Neither tier grants a capability the other lacks.

If you have spent any time shopping for WhatsApp API access, you have read the term BSP, short for Business Solution Provider, roughly four hundred times. It appears on comparison posts, vendor homepages, and agency pitch decks. What almost none of them mention is that Meta's current developer documentation does not use it. The partner program is described in terms of Solution Partners and Tech Providers, and understanding which one you are talking to changes how you buy.

Where the BSP label came from

It came from the On-Premises API, which Meta retired on October 23, 2025. Under that model, API access really was gated. Businesses could not self-serve. An approved partner hosted the containerized API for you, submitted your number, and resold you message capacity. That partner was the Business Solution Provider, and because it was a genuine bottleneck, the acronym became shorthand for the whole category.

The Cloud API replaced it and changed the economics. Meta hosts the API itself now. A business or a developer can build against it directly. Partners still exist and are still valuable, but they compete on software and service rather than on holding the key to the door. The renaming reflects that. "Solution Partner" and "Tech Provider" describe what a company does for you commercially. "Business Solution Provider" described a permission structure that no longer exists.

This is not a pedantic point. When a vendor tells you that you must go through an authorized BSP to get the WhatsApp Business API, they are either working from a 2022 script or hoping you are. Neither is a great sign about the rest of their advice.

Solution Partner vs Tech Provider, side by side

Read that last row twice, because it is the one that matters. Meta's definition of both types includes "messaging services, billing, integration support, and customer support." The functional distinction is the credit line and the ability to invoice for API usage. Everything else is the same platform, the same endpoints, the same webhooks, and the same message rates.

Which one should you buy from?

Buy from a Solution Partner when procurement wants a single vendor relationship. Some finance teams genuinely cannot cope with a variable monthly charge appearing on a Meta payment method attached to a marketing manager's corporate card. A Solution Partner can put the message usage on the same invoice as the software, extend payment terms, and give you one purchase order to approve. For a mid-market or enterprise buyer, that administrative simplicity is often worth more than a few tenths of a cent per message.

Buy from a Tech Provider when you would rather see Meta's charges unmediated. You attach your own payment method, Meta bills you at its published rates for delivered templates, and the provider bills you for its software. Nothing is hidden inside a blended per-message price, which makes it very hard for anyone to mark up your messages without you noticing. If you are cost-sensitive and comfortable with two invoices, this is the more transparent arrangement.

What should not drive the decision is a belief that one tier unlocks features. It does not. If a salesperson implies that Solution Partner status gets you higher messaging limits, faster template approval, or access to some restricted API surface, that is not accurate. Messaging limits are set at the business portfolio level and start at 250 unique customers per rolling 24 hours for new portfolios, rising through 2,000, 10,000, 100,000, and unlimited based on business verification and your template quality rating. Meta controls that ladder, not your partner.

What neither tier can change

No partner, at any tier, can alter what Meta will deliver. The most consequential example for American businesses: Meta's documentation states that WhatsApp "does not currently deliver marketing template messages to WhatsApp users with United States phone numbers." That pause began on April 1, 2025 and, as of July 2026, no resume date has been announced. It is enforced at Meta's delivery layer, so it applies identically to Solution Partners, Tech Providers, and businesses connecting straight to the Cloud API.

Utility templates still deliver to US numbers, which covers order confirmations, shipping updates, appointment reminders, quotes, and renewal notices. Authentication templates still deliver. And any free-form reply sent inside the 24-hour customer service window, which opens when a customer messages you first, delivers at no cost. Service conversations have been free for all businesses since November 1, 2024.

Nor can any partner change the billing model. Since July 1, 2025 Meta charges per message, and you are charged only when a template message is delivered. The rate depends on the template category and the recipient's country. What a partner can change is what it adds on top, and that varies wildly: Twilio publishes a per-message platform fee of $0.005 inbound or outbound above the Meta fees it passes through, while 360dialog charges a flat monthly fee per registered phone number and markets no markup on Meta rates. The tier label tells you nothing about which model a vendor uses. You have to ask.

The question to ask on the sales call

Forget the tier for a moment and ask this instead: who will own my WhatsApp Business Account and my phone number? The right answer is that both sit inside your own Meta Business Account, with the partner granted access. Then switching providers means revoking one and granting another, and you keep your number, your approved templates, and the quality rating you spent months building.

The wrong answer, which is more common than it should be, is that the partner owns the WABA. Leaving then means starting over. That single question separates vendors who expect to keep you through service from vendors who expect to keep you through lock-in, and it cuts across both of Meta's tiers. A Solution Partner can be a hostage-taker and a Tech Provider can be a model citizen, or the reverse.

Ask for a sample invoice too, with Meta's message cost on one line and the provider's fee on another. Anyone quoting a single blended per-message number is marking up Meta's rates and would prefer you did not compare. Our page on choosing a WhatsApp business solution provider runs through the rest of the checklist, and if you are still deciding whether you need a partner at all, going direct on the Cloud API is a genuinely viable path for teams with engineers.

A note on how this ends up on your books

One underrated consequence of the tier you pick: it decides where the cost shows up. With a Solution Partner extending a credit line, WhatsApp usage lands as a single vendor bill that flows through the same accounts payable process as every other supplier invoice, with the same approval chain and the same terms. With a Tech Provider, Meta charges your payment method directly and the software vendor bills separately, which usually means one predictable subscription and one variable card charge that finance has to reconcile against message volume every month.

Neither is wrong. But if you are the person who will be explaining a fluctuating Meta charge to a controller each quarter, it is worth knowing which arrangement you signed up for before the first invoice arrives rather than after.