Most WhatsApp BSPs in India bundle Meta's per-message charges into opaque tiered plans. The brand never sees what Meta charged versus what the BSP marked up. RichAutomate publishes both and lets you choose: pay Meta directly with your own card and pay us a transparent ₹0.10/msg platform fee (Client Pay), or hand off Meta billing entirely and pay us an inclusive ₹1.20/marketing message in INR with GST (SaaS Pay). This guide is the complete 2026 breakdown — when each model wins, the per-message math at three volume tiers, and the agency setup that uses both at once.
The Two Billing Models, Side by Side
| Aspect | Client Pay | SaaS Pay |
|---|---|---|
| Who pays Meta | You — your own Meta credit card on your WABA | RichAutomate — we hold the Meta billing relationship |
| Marketing message rate (India 2026) | ₹0.8631 to Meta + ₹0.10 platform fee = ₹0.9631 | ₹1.20 inclusive |
| Utility message rate | ₹0.115 to Meta + ₹0.10 platform fee = ₹0.215 | ₹0.30 inclusive |
| Authentication message rate | ₹0.115 to Meta + ₹0.10 platform fee = ₹0.215 | ₹0.30 inclusive |
| Service / free-window messages | ₹0 to Meta + ₹0.10 platform fee = ₹0.10 | ₹0 to RichAutomate |
| Meta credit card needed | Yes — you add it to your WABA | No — we manage Meta billing |
| Invoice format | Two invoices: Meta (USD/INR) + RichAutomate (INR + GST) | One invoice from RichAutomate (INR + GST) |
| FX risk on Meta charges | Yours — Meta bills in your account currency | None — we absorb FX, you pay flat INR |
| Wallet top-up needed | No — Meta auto-charges your card | Yes — top up INR wallet on RichAutomate |
| Quality rating ownership | Yours (your WABA, your card) | Yours (your WABA, our card on it) |
| Lowest unit cost | Yes — pure pass-through with flat fee | No — but predictable INR pricing |
| Best for | High-volume D2C, agencies billing clients separately, finance teams that want pass-through accounting | SMB and mid-market brands that want one INR invoice, no Meta card management, no FX risk |
Per-Message Cost Math at Three Volume Tiers
Tier 1: 50,000 messages / month
Mix: 30k marketing, 15k utility, 5k authentication. India 2026 rates.
| Client Pay | SaaS Pay | |
|---|---|---|
| Marketing (30,000 × rate) | 30,000 × ₹0.9631 = ₹28,893 | 30,000 × ₹1.20 = ₹36,000 |
| Utility (15,000 × rate) | 15,000 × ₹0.215 = ₹3,225 | 15,000 × ₹0.30 = ₹4,500 |
| Authentication (5,000 × rate) | 5,000 × ₹0.215 = ₹1,075 | 5,000 × ₹0.30 = ₹1,500 |
| Total | ₹33,193 | ₹42,000 |
| Effective per-message | ₹0.664 | ₹0.840 |
At this tier, Client Pay saves ~₹8,800/month (21% lower). SaaS Pay buys you no Meta card management and a single GST invoice — worth it for many SMBs but not for agencies billing clients.
Tier 2: 200,000 messages / month
| Client Pay | SaaS Pay | |
|---|---|---|
| Marketing (120,000) | ₹1,15,572 | ₹1,44,000 |
| Utility (60,000) | ₹12,900 | ₹18,000 |
| Authentication (20,000) | ₹4,300 | ₹6,000 |
| Total | ₹1,32,772 | ₹1,68,000 |
| Effective per-message | ₹0.664 | ₹0.840 |
Same ratio — savings scale linearly. ₹35k/month saved on Client Pay at this tier.
Tier 3: 1,000,000 messages / month
| Client Pay | SaaS Pay | |
|---|---|---|
| Marketing (600,000) | ₹5,77,860 | ₹7,20,000 |
| Utility (300,000) | ₹64,500 | ₹90,000 |
| Authentication (100,000) | ₹21,500 | ₹30,000 |
| Total | ₹6,63,860 | ₹8,40,000 |
| Annual saving (Client Pay) | ₹21.13 lakh / year | |
When Client Pay Wins
- You ship more than 100k messages a month. Above that volume, the ₹0.10 platform fee is a rounding error vs the ₹0.20–₹0.40 markup baked into SaaS Pay.
- You are an agency billing each client separately. Each client has their own WABA + Meta card. RichAutomate bills the agency a flat platform fee. Cleaner accounting, simpler client invoicing.
- Your finance team requires pass-through Meta charges for FBT / capex/opex separation, or you reimburse Meta charges from a marketing budget different from your platform vendor budget.
- You are USD-comfortable. Meta bills in account currency; some Indian businesses prefer this for reconciliation against international ad spend.
When SaaS Pay Wins
- You are SMB or mid-market with no dedicated finance ops. One INR invoice, GST handled, no Meta card to monitor, no FX risk.
- You don't want to add a credit card to your Meta WABA. Some brands have policy reasons (corporate card limits, founder-only credit cards) that make Meta direct billing painful.
- You want a single platform vendor relationship — predictable monthly cost, no surprise Meta charges if a campaign over-sends, no separate Meta invoice reconciliation.
- You ship under 50,000 messages / month. The per-message savings on Client Pay don't justify the operational overhead of two billing relationships.
The Agency Setup That Uses Both at Once
RichAutomate is multi-tenant. The same agency dashboard can run:
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
- Client A on Client Pay — A holds their own WABA + Meta card. Agency adds value via campaigns, flows, shared inbox. Agency bills Client A a service fee. RichAutomate bills the agency ₹0.10/msg.
- Client B on SaaS Pay — B doesn't want a Meta card. Agency holds B's wallet on RichAutomate, top-ups it monthly, bills B a single inclusive rate per message + service fee. RichAutomate bills the agency the inclusive rate.
- Client C on Hybrid — Client C does utility messages on SaaS Pay (predictable transactional volume) and marketing on Client Pay (high volume, FX-sensitive).
One agency dashboard, three billing configurations, each per-tenant. No other Indian BSP supports this.
Switching Costs and Migration
Both models are reversible. Switching from Client Pay to SaaS Pay or vice versa takes ~3 days, no message-sending downtime. Templates, flows, contacts, and quality rating stay with the WABA. Only the billing relationship changes.
- Open the billing-mode toggle in your tenant settings.
- If switching to SaaS Pay: top up your INR wallet, remove your Meta card, our team verifies the Meta billing handover.
- If switching to Client Pay: add your Meta card to the WABA, our team confirms detection, we drop the inclusive rate.
Rule of Thumb
Under 50k messages/month and SMB ops? Default to SaaS Pay. Above 100k messages/month or running an agency? Default to Client Pay. Between 50k and 100k? Run a 2-week pilot on each and let the actual unit cost decide.
Common Pitfalls When Choosing
- Comparing ₹1.20 (SaaS Pay marketing) to a competitor's ₹0.95 (their inclusive rate) without checking what their rate includes. Many competitor rates exclude template approval fees, conversation overage, or hard-cap your monthly volume. Read the fine print.
- Picking Client Pay without budgeting Meta auto-charges. Meta charges your card automatically — set up alerts and a billing-cap so a runaway flow doesn't spend ₹2L overnight.
- Picking SaaS Pay then complaining about per-message cost at 500k+ msgs/mo. SaaS Pay is designed for predictability, not pure unit-cost minimisation. If unit cost matters most, switch to Client Pay.
- Not capturing the FX risk on Client Pay. Meta bills in your WABA currency. INR-billed accounts are fine; USD-billed accounts (some legacy WABAs) need monthly INR-to-USD reconciliation.
- Forgetting the GST input credit. SaaS Pay invoice gives you full input credit at 18% GST against your INR billing. Client Pay's Meta invoice may be cross-border and ineligible for input credit.
Why Two Models Exist
Most BSPs in India started as resellers — they hold a Meta line of credit, mark up per-message rates, and bill clients inclusive. That's SaaS Pay only. RichAutomate built dual billing because the Indian market splits cleanly into two needs: SMB brands that want simplicity (SaaS Pay) and high-volume agencies/D2C brands that want pass-through accounting (Client Pay). One shape doesn't fit both.
Try both on RichAutomate.
14-day free trial covers both Client Pay and SaaS Pay configurations. Switch between them per tenant. ₹0 setup, no Meta card required to start (you can add it later if you choose Client Pay).