> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gateway.connexease.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How Connexease and Meta fees fit together, and when each one is charged.

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. They are deducted at different points in the message lifecycle, which is the most common source of confusion when reconciling a balance.

## Fee Structure

| Fee                           | Amount                      | When Deducted          | Applies To             |
| ----------------------------- | --------------------------- | ---------------------- | ---------------------- |
| Connexease Infrastructure Fee | \$0.001 (flat)              | On successful API send | All messages           |
| Meta Template Fee             | Varies by market + category | On confirmed delivery  | Template messages only |

<Note>
  **Non-template (session) messages** do not incur a Meta fee. Only the Connexease flat fee is charged.
</Note>

## Total Cost Example

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

| Step                         | Action                   | Balance  |
| ---------------------------- | ------------------------ | -------- |
| Start                        | —                        | \$5.0000 |
| API call succeeds (HTTP 200) | −\$0.0010 Connexease fee | \$4.9990 |
| `delivered` webhook received | −\$0.0009 Meta fee       | \$4.9981 |

If the message is never delivered, only the Connexease fee is charged.