WhatsApp API / Pricing field guide
WhatsApp Cloud API Pricing India 2026: Budgeting and Billing Conditions
Build a budget from the effective message rules and your written platform offer. Keep category volumes, billing currency and delivery evidence visible.
- Published
- Reading time
- 8 min
- Attribution
- Pending

This guide publishes the official INR schedule effective 1 October 2026, explains its allowances and tiers, and keeps an invented arithmetic exercise separately labelled. A Meta estimate is not a total payable quote.
In this guide
- Start with the effective rate scope
- Plan categories separately
- Confirm allowances beside the excluded traffic
- Work a marginal-tier example without treating it as a quote
- Separate delivery, platform and tax amounts
- Accepted, delivered and unresolved are different states
- Prepare the inputs before committing a budget
- Frequently asked questions
Part 01
Start with the effective rate scope
Effective 1 October 2026; original INR billing card, per delivered message. This schedule is not the price for messages delivered before 1 October 2026. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.
Keep the original rate-card currency and billing unit. An India INR rate cannot be relabelled as USD, GBP or another currency. A dated card does not establish the applicable price for a different period, and a list-rate sheet alone does not establish tiers, free allowances or account eligibility.
Use the relevant pricing period for the messages you are budgeting. Keep evidence of the recipient market, account billing arrangement and applicable category. If the period crosses a change, split it into the supported periods rather than applying one rate to every day.
The official October 2026 INR list-rate download matches the owner-supplied workbook byte for byte. The official INR tier workbook and current Meta policy pages were also checked on 29 September 2026. This dated schedule applies from 1 October 2026 at midnight in the Messaging account timezone; it is not the pre-October price.
India list rates — INR per delivered message; Effective 1 October 2026
| Category | List rate |
|---|---|
| Marketing | ₹0.8631 |
| Utility | ₹0.1150 |
| Authentication | ₹0.1150 |
| Authentication international | ₹2.4971 |
| Service | ₹0.1150 |
Further reading
Part 02
Plan categories separately
Utility and Authentication use separate marginal volume tiers by recipient market and category, aggregated across messaging accounts owned by the same business portfolio. Authentication international shares Authentication volume accrual. Only the deliveries within a tier receive that tier’s rate; free-entry deliveries do not advance paid tiers. Tiers reset monthly in the account timezone. Marketing and Service have no volume tiers.
Authentication international applies only to listed recipient markets when Meta has established business eligibility, the primary business location is in another country, and the applicable market/account start date and notice period have been met. Selecting a recipient market or reaching a calculator volume does not establish eligibility. Same-country authentication uses the domestic rate. N/A means no international rate is listed, not a zero charge.
Record marketing, utility, authentication and service volumes separately. Confirm classification and any authentication-international treatment before budgeting; an example template does not establish approval or a rate.
Do not discount all traffic because total volume crossed a threshold. A supported utility schedule uses utility volume; authentication uses its own schedule. Each tier applies only to the messages in that tier. Marketing and free service traffic cannot unlock unrelated category tiers.
If you are comparing providers, keep the same period, currency, delivered volume and category mix. Different inclusion assumptions can make two totals look comparable when they describe different services.
Part 03
Confirm allowances beside the excluded traffic
A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.
From 1 October 2026, delivered Service replies are charged at the recipient market’s Service rate after the monthly 1,000 free Service deliveries per business phone number. This allowance is shared across recipient markets and 1:1/group deliveries, counts each delivered group recipient, resets monthly and does not roll over. Service messages require an open 24-hour customer-service window, opened or reset by a customer message. Incoming customer messages are not charged.
From 1 October 2026, delivered Utility templates are charged even inside the 24-hour customer-service window, unless an eligible free-entry window exempts the delivery. The customer-service window controls messaging permission; it does not make all replies free.
Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Use the effective Service allowance and confirmed free-entry conditions below. Utility deliveries inside the 24-hour customer-service window are chargeable from 1 October 2026 unless a qualifying free-entry window exempts them.
Record why a cohort was excluded, which period it covers and what evidence establishes its conditions. Keep unresolved traffic visible. Message-format permission, business verification and a reply-window timestamp answer different questions from invoice treatment.
Further reading
Invented arithmetic exercise
Work a marginal-tier example without treating it as a quote
The following INR rates are invented solely to explain arithmetic. They are not current or historical Meta rates, Whats91 fees or an offer. The example assumes eligible delivered volumes in one synthetic billing period; it deliberately gives service a zero rate by fixture assumption, not by a permanent free-service claim.
At 1,200 utility messages, the first 1,000 use ₹0.10 and only the next 200 use ₹0.08. Repricing all 1,200 at the cheaper rate would produce ₹96.00 and undercount this example by ₹20.00. Adding marketing or service volume does not change that utility calculation.
Authentication has its own invented threshold and rates. Calculate each category from its own schedule before rounding the subtotal. Keep platform, setup and tax unavailable if their terms are unknown; an available Meta-model subtotal is not a total payable amount.
Synthetic delivered-message arithmetic — INR, per message; no real pricing period or account approval; source model checked 29 September 2026
Scroll sideways to see every column →
| Category | Synthetic volume | Invented marginal schedule | Rounded amount |
|---|---|---|---|
| Marketing | 11,000 | ₹0.20, one invented rate | ₹2,200.00 |
| Utility | 1,200 | First 1,000 × ₹0.10; next 200 × ₹0.08 | ₹116.00 |
| Authentication | 1,010 | First 1,000 × ₹0.05; next 10 × ₹0.04 | ₹50.40 |
| Service | 4,000 | ₹0.00 only by this fixture’s explicit assumption | ₹0.00 |
Synthetic INR exercise — not a rate card or quote
Marketing: 11000 × 0.20 = 2200.00
Utility: 1000 × 0.10 + 200 × 0.08 = 116.00
Authentication: 1000 × 0.05 + 10 × 0.04 = 50.40
Meta-model subtotal: 2200.00 + 116.00 + 50.40 = 2366.40
Platform, setup and tax: unavailable; total payable: unavailableThe invented example Meta-model subtotal is ₹2,366.40. The real website calculators use the separate official INR schedule effective 1 October 2026. Do not copy these invented exercise rates into a budget.
Further reading
Part 05
Separate delivery, platform and tax amounts
Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.
Whats91 platform subscriptions: Coexistence ₹699/month or ₹5,000/year; Standard ₹949/month or ₹7,000/year. Monthly billing has a one-time setup fee of ₹1,000 or ₹2,000 respectively; annual billing includes setup. These amounts exclude 18% GST, added on top. Meta message charges pass through separately without Whats91 markup. Add-ons, feature eligibility, trials, renewal, invoice treatment and activation need separate confirmation. No payment or activation is available on this website.
Budget Meta delivery charges by effective card, market, currency, category and tier. The listed Whats91 plan prices, monthly setup fees, annual setup inclusion and 18% GST calculation are on /plans. Confirm feature scope, renewal and any integration work separately.
The platform first-payment amount is not a combined Meta invoice. Confirm final invoice treatment and input-tax-credit eligibility; do not treat unknown delivery, integration or add-on charges as zero.
A provider comparison needs that provider’s dated written terms. Confirm tax inclusion and whether setup recurs at renewal; no multi-year discount is inferred from this message rate card.
Budget lines and required evidence
Scroll sideways to see every column →
| Line | Basis | If missing |
|---|---|---|
| Meta | Effective delivered-message scope | Amount unresolved/unavailable |
| Platform | Listed Whats91 plan and cycle on /plans | Choose a plan and cycle |
| Setup/integration | Listed setup plus separately agreed integration | Integration quote needed |
| Tax | 18% GST on listed platform/setup; confirm other invoice treatment | Confirm any other tax |
| Total payable | All supported components | Do not substitute zero |
Part 06
Accepted, delivered and unresolved are different states
No. An accepted request is not delivery or a final billing record. Reconcile delivered and failed statuses with the applicable rate card and invoice. Missing delivery or pricing evidence leaves billing unresolved, rather than proving a zero charge.
Evidence illustration
Match three separate records

Request
An accepted send request identifies an attempt. It is not proof of delivery.
Delivery
Match status events to the message reference. Keep missing or conflicting states unresolved.
Billing
Apply the effective scope and reconcile the provider invoice as a separate record.
For a monthly budget, use one pricing period and original currency, document confirmed exclusions and round money consistently. Keep platform and tax lines separate from the Meta subtotal.
Consider three reconciliation cases. An accepted request with no delivery evidence is unresolved. A matched delivered event can be evaluated against the effective scope; it is not by itself a final invoice. A failed record must be reconciled with the provider’s billing evidence rather than silently counted as delivered. Never turn a missing callback into a zero-cost record.
Compare message IDs, cohort dates and categories, then investigate duplicates and late statuses. Preserve an exception list so the accounts team can distinguish an estimate from a billed amount. The website does not inspect an account invoice or resolve those exceptions for you.
Billing evidence states — illustrative, no live invoice
Scroll sideways to see every column →
| Request | Delivery evidence | Billing treatment |
|---|---|---|
| Accepted | Missing | Unresolved; inspect before retry |
| Accepted | Delivered | Evaluate effective conditions and reconcile invoice |
| Accepted | Failed | Reconcile failure with billing record |
| Unknown | Conflicting or unmatched | Investigate reference; no guessed amount |
Part 07
Prepare the inputs before committing a budget
The two website calculators share the same official dated schedule and marginal arithmetic. Enter delivered quantities, remaining Service allowance, prior paid tier counts and confirmed free-entry exclusions. They estimate Meta delivery charges without Whats91 markup; neither inspects an invoice nor takes payment.
Bring category counts, intended market, original billing currency, pricing period, exclusions and the written platform scope. Ask for separate setup, renewal and invoice/tax treatment. If any material input is missing, retain an unavailable total and resolve that line before buying.
- Choose the relevant period and account billing currency.
- Separate delivered category counts from accepted or unresolved traffic.
- Confirm each allowance/tier and preserve its supporting conditions.
- Obtain written platform/setup/renewal terms and applicable invoice treatment.
- Reconcile the resulting estimate with actual delivery and billing records.
Turn your confirmed inputs into an estimate
The planner estimates Meta messaging charges; confirm platform, setup and invoice treatment separately.
Pricing and message-volume plannerFurther reading
Questions
Frequently asked questions
Which pricing period does this calculator use?
Effective 1 October 2026; original INR billing card, per delivered message. This schedule is not the price for messages delivered before 1 October 2026. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.
How are message categories and tiers counted?
Utility and Authentication use separate marginal volume tiers by recipient market and category, aggregated across messaging accounts owned by the same business portfolio. Authentication international shares Authentication volume accrual. Only the deliveries within a tier receive that tier’s rate; free-entry deliveries do not advance paid tiers. Tiers reset monthly in the account timezone. Marketing and Service have no volume tiers.
Does an accepted API request prove a charge?
No. An accepted request is not delivery or a final billing record. Reconcile delivered and failed statuses with the applicable rate card and invoice. Missing delivery or pricing evidence leaves billing unresolved, rather than proving a zero charge.
Are service replies or messages in a window always free?
From 1 October 2026, delivered Service replies are charged at the recipient market’s Service rate after the monthly 1,000 free Service deliveries per business phone number. This allowance is shared across recipient markets and 1:1/group deliveries, counts each delivered group recipient, resets monthly and does not roll over. Service messages require an open 24-hour customer-service window, opened or reset by a customer message. Incoming customer messages are not charged. From 1 October 2026, delivered Utility templates are charged even inside the 24-hour customer-service window, unless an eligible free-entry window exempts the delivery. The customer-service window controls messaging permission; it does not make all replies free. Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
What needs to be separate in my budget?
Separate Meta delivery charges, the listed Whats91 plan subscription, one-time monthly-billing setup, integrations and taxes. The listed platform/setup amounts have 18% GST added. Confirm Meta billing currency, any integration quote, renewal and trial conditions, invoice treatment and input-tax-credit eligibility separately.
Does Whats91 add a markup to Meta messaging charges?
Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.
When does Authentication international apply?
Authentication international applies only to listed recipient markets when Meta has established business eligibility, the primary business location is in another country, and the applicable market/account start date and notice period have been met. Selecting a recipient market or reaching a calculator volume does not establish eligibility. Same-country authentication uses the domestic rate. N/A means no international rate is listed, not a zero charge.
Share this guide
If copying is unavailable, select the article link below.
Next reads
Continue reading

WhatsApp API
WhatsApp Cloud API: Setup, Delivery and Billing Guide
Plan a WhatsApp Cloud API setup with account checks, delivery reconciliation, billing conditions and a measured pilot before connecting business workflows.
Read guide →
WhatsApp API
WhatsApp Web Sessions and Official API Migration: A Planning Guide
Assess browser-session dependencies, standard and eligible hybrid paths, genuine onboarding information, backup, recovery and costs before migrating a number.
Read guide →