Understand pricing and wallets
Understand estimates, reserved and available balances, delivery charges, top-ups, and billing reconciliation.
Check the destination, message category and current quote before sending live traffic. Prices can vary by market, category, usage tier and your project's configured pricing. Use the current calculator or API estimate rather than copying a price from a screenshot.
Where to look
Select the intended project and open Workspace → Billing for balance, top-ups and billing history. Message Logs shows message outcomes and recorded cost. Provider integrations use a shared provider wallet; see provider integration.
Three balance values
| Value | Meaning |
|---|---|
| Settled balance | Balance recorded by completed ledger transactions. |
| Reserved balance | Credit held for accepted messages still awaiting settlement. |
| Available balance | Settled balance minus reserved balance; the amount available to spend. |
The API's legacy balance field is an alias for available balance. A reservation can reduce what you can spend before a final usage charge appears. This is not a second charge.
Follow one message through billing
- A live request is accepted and its estimated amount is reserved before queueing.
- The message proceeds through delivery. A queued/sent state is not a final bill.
- A chargeable delivered/read event captures the reservation and records the usage debit using the locked send-time quote.
- A terminal failure releases the pending reservation. If settlement is below the reservation, the unused difference becomes available.
Repeated callbacks should not create repeated usage debits. Check the actual ledger and request attempts when investigating a discrepancy, especially if fallback/recovery occurred. Do not infer the final charged amount solely from the first queued response.
Top up safely
Start a top-up from Billing, review the amount and complete the hosted checkout when ready. Credit is applied after payment confirmation, so opening checkout alone does not increase the balance. Use top-up history and invoice/receipt records to reconcile a payment; do not start another payment merely because the UI has not refreshed yet.
Project transfers move available credit between projects and are subject to project access and permissions. Confirm the destination project and amount before submitting.
Estimates and usage tiers
Use public calculator endpoints for a general estimate and the project-price endpoint for the project's customer-visible quote. The generated reference contains the supported inputs. Currency and estimated totals in an API response should be treated as values for that request, not a permanent rate card.
Monthly WhatsApp tier progression is tracked by project, market and category at UTC month boundaries. Different markets/categories can reach tiers independently. Avoid promising that all project traffic contributes to a single plan-wide allowance.
Development-key and sandbox sends for supported messaging operations simulate without message charges. Free-text replies require live mode. Media and management operations have their own restrictions; a development key does not make every endpoint available.
When numbers do not match
Compare the selected project/deployment, currency, date range and timezone first. Then compare available versus settled balance, pending reservations, final charged amount and the request's attempts. Keep message IDs and request IDs for support; redact phone numbers and credentials.
The API Reference remains authoritative for current fields. This guide deliberately does not publish internal costs, margins or admin pricing controls.
Updated about 16 hours ago
