Every BSP quietly adds its own markup on top of every WhatsApp template message a business sends. Antraweb's 35,000+ TallyPrime customers just got a way around it — direct, transparent pricing, and the ability to send invoices, chase payments, and collect money without ever leaving WhatsApp.
Every business sending WhatsApp template messages through a BSP is paying two bills without necessarily realising it. One is WhatsApp's own conversation pricing. The other is invisible — a markup, quietly added on top of every message sent, that almost never gets broken out anywhere a customer can actually see it.
What a BSP actually is, and where the markup hides
A Business Solution Provider (BSP) is the standard route most businesses take to reach WhatsApp Business API — Meta doesn't sell direct access to most companies, so a BSP sits in between, handling onboarding, number provisioning and template approval on a business's behalf. It works. It's also where a cost most businesses never interrogate quietly gets added: WhatsApp gives every business a monthly allowance of conversation credit, and beyond that allowance, a BSP typically layers its own markup on top of every template message sent, scaling with volume, on top of whatever WhatsApp itself is already charging.
At low volume, that markup barely registers. At the volume a business with thousands of customers actually runs at — invoices, reminders, alerts, month after month — it becomes a real, recurring line item nobody budgeted for as its own cost.
Why Tally customers specifically needed a way around it
Tally itself had already opened the door to WhatsApp for its customers, through its own partnerships with BSPs. Antraweb Technologies — a major implementation partner for TallyPrime, serving more than 35,000 customers across India — wanted to offer its own Tally customer base the same capability, but on terms it could actually control: more price-optimised, without a BSP's markup baked invisibly into every message a Tally customer's business sends.
The direct route: what changes when there's no BSP in the middle
rePUSHTI had already built and deployed its own WhatsApp Business API infrastructure — originally for its own booking re-verification automation — and became an official Meta Tech Provider on the strength of it. That status means WhatsApp integration runs directly, with no BSP as a middleman. There's no markup layered onto template messages. A business pays a subscription, and whatever WhatsApp itself bills, transparently — nothing hidden in between.
A BSP's markup scales with every message a business sends. A direct integration doesn't have one to scale.
That's what Antraweb partnered with rePUSHTI for: a direct route onto WhatsApp Business API, for its Tally customer base, at rePUSHTI's transparent pricing instead of a BSP's marked-up rate.
What Antraweb's Tally customers can now do on WhatsApp
- Send invoices straight from Tally to a customer's WhatsApp — no separate export, no email that gets buried
- Send pending payment alerts to where a customer will actually see them, rather than an inbox they check once a week
- Collect payment directly inside WhatsApp — the same native, in-chat checkout rePUSHTI has already built, with no separate payment link and no in-app browser pulling the customer out of the conversation
Why this matters beyond one partnership
This isn't really a story about one accounting software and one implementation partner. It's what happens whenever the standard BSP model gets replaced with a direct one: the same invoices, reminders and in-chat collection become available to any business willing to move off a marked-up WhatsApp Business API connection and onto one that isn't. Tally and Antraweb happen to be first through that door together — 35,000+ businesses, all able to bill and collect on WhatsApp without paying a markup they were never shown in the first place.
This is live for Antraweb's Tally customers now.
