A2P monetization is how a mobile operator gets paid for all of the business (A2P) SMS that ends on its network. BroadNet runs it for operators as one stack: firewall, commercial engine and aggregator settlement.
Firewall, commercial engine, and settlement — running as one stack.
Operators rarely capture all of the A2P SMS revenue legitimately due to them. The rest leaks via grey routes, SIM boxes, and unmonitored aggregator traffic. BroadNet's A2P monetization stack — firewall plus commercial engine plus aggregator settlement — identifies the leaked traffic and converts it to billable A2P. The recoverable share is measured on your own traffic, in mirror mode, before anything is enforced.
We also send A2P traffic. It passes your firewall under the same rules as every other sender, and your team owns the verdicts.How the firewall treats our traffic ↓
Measured in mirror mode firstGSMA IR.71 alignedInline · sub-ms decision
Where the A2P revenue goes — and how it comes back
commercial flow
MODE
Mirror
measure first
OUTPUT
Billed
grey → A2P
AUDIT
Ledger
per message
Neutrality and governance
We also send A2P traffic. Here is how your firewall treats it.
BroadNet sells enterprise messaging and the firewalls that filter it, so an operator's first question is a fair one: what does the firewall do to BroadNet's own traffic? The answer is built into how every deployment runs.
“The fact that the same vendor sells our enterprise customers their CPaaS is why the numbers actually match the reports.”
BroadNet's own enterprise traffic reaches your subscribers through the same firewall and the same rules as every other aggregator and sender. There is no vendor exemption.
You own the ruleset and the verdicts
Your fraud and revenue-assurance teams own the rules. Every change is version-controlled and needs a second approver (maker-checker), and false-positive whitelists are operator-controlled. Every verdict is your network's decision, and the data stays yours.
Audits and disputes run on records
Every decision is logged with the rule that fired and exports as CSV, JSON or PDF for partner disputes and regulator inquiries. A dispute about BroadNet traffic is settled against the same records as any other.
Aligned with GSMA FS.11
Rule categories follow GSMA FS.11 and FS.19, so your team and your regulator review the firewall against a published industry framework, not a vendor's private taxonomy.
Capabilities
One stack. Three places revenue leaks.
Detection, commercial conversion, and settlement run side-by-side, sharing the same traffic ledger. No bolt-on integrations, no double-count.
Leakage analytics
Identify which sender IDs, aggregators, and countries are driving leakage. Quantify the recoverable revenue per route, per month, per partner.
Per routePer partnerPer country
Aggregator agreements
Standard commercial templates to convert grey-route aggregators to officially-billed A2P. Co-negotiation with BroadNet's commercial team.
MSA templatesCo-negotiationBilateral pricing
Settlement integration
Automated CDR generation and invoicing per aggregator. Native integration with Comfone, MACH, and other settlement clearing houses.
CDR exportComfone / MACHAuto-invoice
Commercial engine
Per-sender, per-country, per-time-of-day pricing. Quarantine grey-route traffic and re-offer at the commercial A2P rate.
Per-senderQuarantineRe-offer
Executive dashboards
Monthly run-rate by route, leakage residue, partner scorecards — exportable for board reviews and regulator submissions.
Monthly run-ratePartner scorecardBoard export
Audit trail
Every classification decision, every quarantine action, every settlement line — logged with operator ID, timestamp, and rule version.
Per-message logTamper-evidentRegulator-ready
Outcomes
What changes once the firewall and commercial engine are live.
Results depend on each network's traffic mix, so we do not publish a benchmark figure. The assessment measures your own grey-route volume in mirror mode first, and the business case is built from that measurement.
Measured before enforcement
Mirror
Mirror mode sizes grey-route volume on your own traffic before anything is blocked
Grey A2P converted
Billed
Unauthorised A2P re-offered to senders as billed traffic, on your terms
Fraud stopped at the edge
Blocked
Smishing and spoofed senders stopped before they reach the SMSC
One traffic ledger
Ledger
Every classification and settlement line in one audit trail
How the commercials work
Revenue share, license, or hybrid — priced against your own recovery curve.
The mechanics are the same in every model: leakage analytics quantify the recoverable revenue per route, grey-route aggregators are converted to billed A2P agreements, and settlement reconciles against your existing billing. What changes is who carries the upfront cost and how the recovered margin is split. All structures below are typical industry arrangements, described as illustrations — commercial terms are set per engagement, after the leakage audit.
Model A
Managed revenue share
No upfront license. BroadNet deploys the firewall and commercial engine, and the fee is a share of newly recovered A2P revenue — stepped down as volumes mature. The common starting point when the leakage baseline is still unknown.
Fits: first deployment, unproven baseline, capex-constrained budgets.
Model B
Annual license + support
A fixed platform license with support and rule-pack updates, once the recovery curve is predictable. Operators typically convert to this after the first year, when keeping the full recovered margin beats sharing it.
Fits: mature deployments, operators with in-house firewall desks.
Model C
Hybrid
A smaller license base plus a reduced share on recovered volume. Splits the incentive: BroadNet stays motivated to keep conversion coverage widening while the operator caps the total cost of the program.
Fits: multi-opco groups standardising terms across markets.
Interactive estimate
How much A2P revenue is your network leaking?
Move the sliders to your network's shape and your own assumptions. The model prices the grey-route gap at your own effective rate — it is your estimate, not a BroadNet benchmark.
2M
SIMs on your network (or your MVNO base)
4
OTPs, alerts, notifications terminating per SIM
$0.035
Blended per-message termination rate you bill today
20%
Traffic arriving over SIM boxes, SS7 bypass or unmonitored aggregator binds
50%
How much of the identified grey traffic you expect to bring onto billed routes
Estimated annual A2P volume
96,000,000
messages / year at these inputs
Estimated annual grey-route leakage
$672K
A2P value arriving over unbilled routes at your grey-share estimate
Recoverable revenue at your assumption
$336K
the grey-route value you expect to convert to billed A2P
How to read this
Grey share and conversion are your own inputs. BroadNet does not publish a benchmark for either — the operator assessment measures your actual grey-route volume in mirror mode.
Leakage is priced at your current effective rate.
Estimate from your inputs only — not a BroadNet benchmark or a promised outcome.
A 30-minute working session with the engineers who deploy this gear at Tier-1 operators. Bring your traffic map, your last quarter’s A2P P&L, and the route you’re worried about — we will tell you where the leak is.
