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

# Who Charges You for WhatsApp — Meta or ChatSyncs?

> Why WhatsApp automation involves two separate bills from two separate companies — Meta's usage-based conversation pricing and ChatSyncs' own platform subscription.

Two separate companies bill for two separate things — mixing them up is the most common pricing
confusion:

* **Meta** charges for using WhatsApp itself — the conversations that actually go out.
* **ChatSyncs** charges for the platform that lets you send, automate, and manage those
  conversations.

Paying one does not include the other.

## Meta's side: usage-based conversation pricing

* Charged directly by Meta, against the Business Portfolio's own payment method — not routed
  through ChatSyncs at all.
* Based on conversation category (Marketing / Utility / Authentication / Service), destination
  country, and only on delivered messages.
* A payment method has to be on file in Meta before sending template messages — see
  [How to Add Payment Method for WhatsApp API Billing](/learn/chatsyncs-setup-and-configuration/add-payment-method-for-whatsapp-api-billing-in-chatsyncs).

Full breakdown: [What WhatsApp API Pricing Really Means](/learn/chatsyncs-overview/what-whatsapp-api-pricing-really-means-in-chatsyncs).

## ChatSyncs' side: the platform subscription

* A separate recurring fee for the software itself — the shared inbox, chatbot builder,
  broadcasting, subscriber manager, integrations, and everything layered on top of the raw API.
* Billed by ChatSyncs, independent of how many WhatsApp conversations you send.
* See [chatsyncs.com](https://chatsyncs.com) for current plans.

## Budgeting for both

|             | Meta                            | ChatSyncs                    |
| ----------- | ------------------------------- | ---------------------------- |
| Charges for | The WhatsApp conversations sent | The platform/software        |
| Billed by   | Meta, to the Business Portfolio | ChatSyncs, as a subscription |
| Scales with | How many messages you send      | Flat recurring cost          |

Planning WhatsApp automation costs means adding both — not assuming one covers the other.

## Frequently asked

<AccordionGroup>
  <Accordion title="Does my ChatSyncs subscription include WhatsApp messaging costs?">
    No — Meta bills conversation usage separately, based on how many messages you send and what
    category they fall into.
  </Accordion>

  <Accordion title="Why do I need to add a payment method in Meta if I already pay ChatSyncs?">
    Because Meta's conversation charges are billed by Meta directly to the Business Portfolio,
    not through ChatSyncs. See [How to Add Payment Method for WhatsApp API Billing](/learn/chatsyncs-setup-and-configuration/add-payment-method-for-whatsapp-api-billing-in-chatsyncs).
  </Accordion>

  <Accordion title="If I stop paying ChatSyncs, do I lose my WhatsApp number?">
    No — the number and WABA belong to your Meta Business Portfolio regardless of which platform
    manages it. See [What Is a BSP — and Can You Move to ChatSyncs From One?](/learn/chatsyncs-overview/what-is-a-bsp-and-can-you-move-to-chatsyncs-from-one) for
    how that ownership works.
  </Accordion>

  <Accordion title="Is Meta's pricing different depending on which platform I use?">
    No — Meta's conversation pricing is the same whether you send through ChatSyncs, a different
    BSP, or a direct API integration. Only the platform subscription fee differs by provider.
  </Accordion>
</AccordionGroup>

## Gotchas & common mistakes

<Warning>
  * **Don't assume a ChatSyncs plan's message volume covers Meta's charges** — the two are billed
    independently even where a plan mentions volume.
  * **A missing Meta payment method blocks template sends**, not ChatSyncs itself — if messages
    fail to send despite an active ChatSyncs subscription, check billing on the Meta side first.
</Warning>