Multi-partner Solutions

A Multi-partner Solution links your Tech Provider app with Kapso. Your app owns the customer relationship. Kapso can run the WhatsApp infrastructure, provide managed billing, or both.

​

Requirements

Before creating a solution:

• complete Meta business and access verification as a Tech Provider
• request the Meta permissions required by your embedded signup flow
• create a WhatsApp embedded signup configuration for your app
• save your Meta app and configuration ID in Kapso if Kapso will run messaging
• use a Platform or Enterprise Kapso project
• ask Kapso to enable Multi-partner Solutions for the project
• maintain the minimum prepaid balance shown in the project

​

Create the solution

In Kapso, open Tenants > Multi-partner solution. Two ways to create it:

• Create with Kapso — Kapso opens Meta’s embedded creation flow and stores the returned solution.
• Create manually in Meta — create and submit the solution request in Meta, then enter the exact solution ID and your app ID in Kapso. Kapso reviews and accepts its side. The solution activates after both partners are accepted in Meta.

Choose:

• Messages processed by: Kapso or Your infrastructure
• App with messaging permission: Your Meta app

Kapso validates the apps and permissions before activating the solution.

​

Solution status

Deactivating a solution keeps existing customer connections. Customers are not moved to another solution.

​

Onboard with Kapso infrastructure

Create a setup link or embed onboarding in your product. Kapso locks the solution to each signup attempt when it starts, so changing the solution mid-flow does not affect onboarding in progress. The connected WABA stays tied to the solution it onboarded with, for billing and analytics. Set meta_billing_mode when creating the setup link:

• customer_managed — the customer pays Meta directly.
• partner_managed — Kapso attaches its credit line and deducts WhatsApp fees from your project’s prepaid USD balance.

​

Onboard with your infrastructure

Follow You run messaging to initialize Meta’s SDK, pass your Solution ID, and complete onboarding on your backend. Meta reports each associated WABA to Kapso. For every eligible active WABA, Kapso checks eligibility and project balance, attaches its credit line automatically, and starts metering from that point — usage from before the WABA was funded is not charged. Kapso checks aggregate Meta usage about every five minutes. Accounts that cannot be funded show a Needs attention state. Kapso retries recoverable failures without creating duplicate funding or charges.

​

Monitor customer accounts

Open Tenants > Multi-partner solution to see:

• detected customer WABAs and their connection state
• managed funding status and WABA currency
• messages and external spend observed in the last 24 hours
• external spend observed in the last 30 days
• when Meta last reported each account

The summary also shows an estimated balance buffer. It compares your available balance with the highest five-minute WhatsApp spend observed in the last 24 hours. It is an estimate, not a spending limit or guarantee.

​

Managed billing

When Kapso runs messaging, a successful WhatsApp connection does not by itself confirm that managed billing was attached. Check the billing result returned by the setup flow. When messages run through your infrastructure, Kapso cannot pause your sends. Keep enough prepaid balance to cover usage reported between Pricing Analytics checks. The balance buffer helps you monitor that exposure but does not block sends. Messages sent through your infrastructure include a 5% managed billing fee on top of Meta’s published USD list rate. This fee is separate from the FX margin applied to non-USD WABAs.

​

WhatsApp Calling

Managed billing for WhatsApp Calling is available for eligible USD WABAs. User-initiated calls are free. Meta charges business-initiated calls based on duration and destination, and Kapso deducts the aggregate cost from your prepaid balance. When calls run through Kapso, Kapso checks billing health and balance before starting a business-initiated call. When calls run through your infrastructure, Kapso checks Meta Call Analytics about every five minutes and cannot block calls made through your own integration. Calling fees are reported as aggregate usage. Kapso does not show an exact Meta fee for an individual call. See Meta message billing for pricing and supported currencies.