Skip to main content
Open Tenants > Multi-partner solution to see and control managed billing for every customer account connected through your solution. To automate this, use the Funding API.

​
Monitor customer accounts

Detected accounts are grouped by Business Portfolio. Open a portfolio to see:
  • detected customer WABAs and their connection state
  • 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.

​
Stop and resume funding for a portfolio

Kapso funds eligible portfolios by default. Open a Business Portfolio to stop or resume funding for every WhatsApp account in it. Stop funding first shows the accounts that would be affected. If something would make the change unsafe, Kapso lists the blockers and does not run it. Otherwise you confirm by typing STOP FUNDING <business portfolio id>, and Kapso revokes its credit line from those accounts in the background. If the accounts change between the review and the confirmation, the change is rejected and you review again. Resume funding turns automatic funding back on. Kapso funds eligible active accounts in the portfolio on the next check. Stopping funding does not stop your own sends. When messages run through your infrastructure, Kapso cannot block them; it only removes its credit line from the accounts. Customers may need their own Meta payment method afterwards — see Leaving managed billing.

​
Review funding activity for an account

Open an account from the Actions column of the portfolio table to see its funding history: when Kapso attached or revoked its credit line, when automatic funding ran, and what failed. Current attachment status is shown above the history and is tracked separately from past failures. A retired attachment on Kapso’s side does not by itself mean Meta revoked the allocation — only explicit confirmation from Meta does. Attempts are listed newest first, and the steps inside an attempt run oldest to newest. The header of an attempt shows the latest step observed so far, not a guaranteed final result. Steps that belong to the same operation are grouped; because activity loads a page at a time, an attempt can gain more steps when you load older activity. Activity recorded before operation grouping existed appears as individual entries. Expand a step for diagnostic details, including its event ID and the Meta trace ID when Meta returned one. Quote these when contacting support. Only activity for accounts your project owns or has previously had attached is shown. Steps covering a shared credit line are limited to portfolio-level facts and never include another customer’s names, identifiers, or error details. Viewing activity is read-only. It never retries funding, changes an attachment, or calls Meta.