Skip to main content
The Connexease Gateway applies two separate fees per message: a flat infrastructure fee charged on every successful send, and a variable Meta fee charged only when a template message is confirmed as delivered. Understanding when each fee is triggered — and how to monitor your balance proactively — helps you avoid unexpected campaign interruptions. This page explains the full billing lifecycle, the 24-hour metadata window, and the current pricing table by country and conversation category.

​
Fee Structure

Each message can incur two separate fees, deducted at different points in the message lifecycle:

​
Billing Triggers

​
1. Connexease Fee — On Send

When your API call returns HTTP 200, $0.001 is immediately deducted from your balance. This fee is independent of whether the message reaches the recipient. This fee applies to all successful sends: text, image, audio, document, template, and interactive messages.

​
2. Meta Template Fee — On Delivery

Applies to template messages only. The fee is deducted when Meta sends a webhook with status: "delivered" and pricing.billable: true. The fee amount depends on:
  • Recipient’s country (derived from the phone number’s country code)
  • Conversation category (marketing, utility, authentication, service)
Non-template (session) messages do not incur a Meta fee. Only the Connexease flat fee is charged.

​
Free Tier (billable: false)

When the delivery webhook contains pricing.billable: false, no Meta fee is deducted. This applies to conversations that Meta has designated as free (e.g. conversations initiated from Click-to-WhatsApp ads).

​
Balance Check

The Gateway checks your balance before forwarding any message to Meta. If the balance is ≤ 0, the request is rejected immediately:
When you receive BILL_001, immediately pause any active campaigns. We recommend setting up balance alerts in Dashboard → Billing → Balance Alerts before this happens.

​
Template Billing Window (24 Hours)

When a template message is successfully sent, the Gateway stores billing metadata (billing account, country, category) keyed by the wamid in Redis with a 24-hour TTL. When the delivery webhook arrives, the Gateway:
  1. Fetches and atomically deletes the metadata by wamid (prevents double-billing).
  2. Calculates the Meta fee from the pricing table.
  3. Deducts the fee from your balance.
If delivery confirmation does not arrive within 24 hours (TTL expires), the metadata is dropped and no Meta fee is charged for that message.

​
Template Conversation Categories

​
Sample Pricing Table (effective January 1, 2026)

All Meta fees are denominated in Euro (€).
The full pricing table for all 30+ markets is available in Dashboard → Billing → Pricing.

​
Total Cost Example

Sending a utility template to a user in Turkey (+90):

​
Recommendations

For high-volume campaigns, estimate total cost before starting and pre-load your wallet with sufficient balance.
Use is_fake=true during development and testing. The billing pipeline runs (balance check) but no fee is deducted and the Meta API is not called.