Skip to main content
There are two independent paths: stay pay-as-you-go only (top up balance, no paid plan) or subscribe to a plan and use only monthly credits (balance is optional, as backup). You do not need to mix both.

​
What is it?

It’s how Notifique charges for your sends. You pay per message sent, not for API access. Think of two different wallets: Each send debits credits or balance, never both at once. The workspace shows which one the next send will use.

​
What is a credit worth?

1 credit = R$ 0.001 (one tenth of a cent). Same idea as arcade tokens: you buy a bunch at once, and each machine takes a different number of them.
  • 1,000 credits = R$ 1.00
  • 100,000 credits = R$ 100.00
Each channel consumes a different number of credits (table below).

​
Which path fits you?

On path B, many users rely on monthly credits only and never top up balance. Balance only kicks in if you topped up and credits run out before renewal.

​
Path A: pay-as-you-go only

For users who do not want a paid plan and prefer to pay as they send.
  1. Account on the Free plan (no monthly credits)
  2. Try with R$ 1 balance for 48 h
  3. Top up when ready to send for real (min. **R30∗∗;quickoptions:R 30**; quick options: R 30, R50,R 50, R 100)
  4. Each message debits balance at the pay-as-you-go price (table below)
  5. Each balance batch lasts 90 days (oldest used first)
Summary: no monthly subscription. No plan credits. Everything comes from balance you top up.
The pay-as-you-go price is always a bit higher than the same send paid in credits. That’s on purpose: subscribers pay less per message, like buying wholesale.

​
Path B: paid plan (optional balance)

For users who want a monthly allowance included in the plan.
  1. Subscribe to Basic, Pro, or Business
  2. Every month you get credits that renew on the cycle
  3. Each send uses credits first (table below)
  4. Credits hit zero and you have topped-up balance? Next sends use balance
  5. Credits hit zero and no balance? API returns 402 (INSUFFICIENT_CREDITS, WORKSPACE_BLOCKED)
Summary: the paid plan covers sends via credits. Topping up balance is optional, only as a cushion if monthly credits run out.

​
Plans and included credits

Already subscribed? The new credits land on your cycle renewal, not immediately. The subscription price stays the same: nobody pays more because of the new table.

​
Instance limits (WhatsApp and Telegram)

Applies to paid plans. Limits are per channel, not combined:
  • Plan with N = 2: up to 2 WhatsApp instances and up to 2 Telegram at the same time
  • Not “2 total” across both channels
Need more lines without changing plans? Each extra slot costs R$ 7.90/month and adds +1 instance on each channel, up to 20 slots per workspace.

​
How much each channel costs

Credits come out of the plan; the pay-as-you-go price comes out of your BRL balance.

​
Sending

​
Inbound and AI

Official WhatsApp is charged according to who pays Meta. On the default path (Tech Provider or BYOK), Meta bills conversations directly to you and Notifique charges only the software fee, flat for any destination. On BSP lines Notifique is the one paying Meta, and the price varies by recipient’s country and template category. See Official WhatsApp by country.

​
SMS: three speeds, three prices

SMS is the only channel where you pick the route. Like choosing express, standard, or economy shipping: the faster it moves, the more it costs. Pick it in the send body:
speed is not priority. options.speed picks the carrier route and changes the price. options.priority only sets the order in Notifique’s internal queue and changes nothing about the amount charged. Sending priority: "high" makes the SMS neither faster at the carrier nor more expensive.
An invalid value in options.speed returns 400 with options.speed must be full, standard, slow.

​
Where to manage in the dashboard

  • Balance: view balance, top up, enable auto top-up
  • Plans / Subscription: current plan and credit renewal
  • The workspace shows whether the next send uses credits or balance
Billing errors: Error responses.

​
Next steps