×
Have questions or ready to talk to a Vonage expert?
Robot Chat Icon
Device Type: 
Skip to Main Content Skip to Main Content

Toll Fraud Prevention: How To Protect Your SMS and Voice Traffic From IRSF and SMS Pumping

This article was published on November 18, 2026

Toll fraud prevention is the practice of blocking fraudulent traffic to premium-rate numbers before you are billed for it. International Revenue Share Fraud (IRSF), artificially inflated traffic (AIT), and SMS pumping all exploit your verification flows, and pre-send decisioning stops them across SMS and voice.

Security team monitoring networks in a control room
Adam Weir headshot
By Adam Weir Product Expert, Fraud Solutions

Key takeaways

What is toll fraud, and why toll fraud prevention starts with the bill

Toll fraud is any scheme that routes your SMS or voice traffic to premium-rate numbers controlled by a fraudster so that every message or call generates revenue for them at your expense. The mechanism is simple: The fraudster owns or leases premium-rate number ranges in obscure jurisdictions, engineers ways to push your traffic to those numbers, and collects a revenue share on the inflated bill.

The underlying money engine is International Revenue Share Fraud (IRSF). IRSF is the revenue-sharing arrangement that pays out a cut of premium-rate charges to whoever drove the traffic. That is why toll fraud prevention has to begin with a cost mindset: The first person to notice an IRSF attack is often the CFO staring at an unexplained spike in messaging or voice spend.

The scale is not marginal. Telecom fraud losses reached $41 billion in 2025. IRSF and toll fraud are consistently among the largest categories inside that total, because they turn ordinary verification traffic into a payout channel.

Have you seen unexplained increases in SMS or voice spend? Do you already use prefix rules to block high-risk countries? If either answer gives you pause, you likely have live toll fraud exposure.

How an IRSF scheme works, step by step

International Revenue Share Fraud is best understood as a supply chain. Each step looks legal on its own, which is what makes IRSF fraud so durable.

  • Step one. The fraudster controls a range of premium-rate numbers, often in jurisdictions where oversight is thin and payout terms are generous.
  • Step two. They manufacture demand toward those numbers. Bots trigger one-time-passcode (OTP) requests against your sign-up or login flow, abuse click-to-call buttons, or spin up fake account-creation attempts at volume.
  • Step three. Carriers bill your traffic at premium rates. Because the messages or calls look like ordinary verification traffic, they clear your systems without question.
  • Step four. The carrier returns a share of those premium charges to the fraud-controlled range. The fraudster is paid, and you absorb the loss.

A substantial share of OTP requests at exposed businesses can be fraudulent in some flows. That is the raw material IRSF operators feed on, and it is why verification-heavy businesses are the primary targets.

The toll fraud, AIT, and SMS pumping family: one architecture, different surfaces

Toll fraud, artificially inflated traffic, and SMS pumping are frequently used interchangeably, but precision matters when you are choosing a defense. They share an architecture and a profit motive, yet the attack surfaces differ.

Attack type 

What it is 

Primary surface 

What it exploits 

Toll fraud 

Any fraud that routes traffic to premium-rate numbers

SMS and voice

Verification and calling flows

IRSF (international revenue share fraud) 

The revenue-sharing mechanism that pays fraudsters 

SMS and voice 

Premium-rate number ranges 

AIT (artificially inflated traffic) 

Bots deliberately driving OTP volume 

SMS-heavy OTP flows

Automated verification requests 

SMS pumping

The SMS-specific variant of AIT

SMS OTP and A2P 

Sign-up, login, and free-trial flows 

Voice fraud

Toll fraud on the calling side 

Voice 

Click-to-call and IVR abuse 

The takeaway for SMS fraud protection: The defenses use shared building blocks (prefix rules, IRSF datasets, sequential dialing intelligence), but you tune them to the surface under attack. A team fighting SMS pumping, and a team fighting voice fraud are running the same playbook against different doors.

Phishing volume compounds the problem. 71% of surveyed organizations experienced at least one successful phishing attack, and the same automation that powers phishing at scale also powers artificially inflated traffic against your OTP endpoints.

Pre-send fraud decisioning: the core of modern toll fraud prevention

The single biggest lever in toll fraud prevention is when you make the decision. There are two models.

Post-send blocking stops traffic at the wire, but the message is already transmitted. You have accepted the cost and, in many cases, already incurred it. Post-send cleanup is reactive by definition.

Pre-send fraud decisioning blocks the destination before you commit the message. Nothing is billed, nothing is sent, and the fraud never converts into a payout.

Fraud Defender delivers this through configuration, not a per-message API call your application makes. You set the rules and thresholds once, and Fraud Defender enforces them automatically at the network level for every message and call that follows:

  • Traffic Rules block or allow traffic by product (SMS or voice) and destination prefix, a specific number range, or an entire country, with a reason attached for your audit trail.
  • AIT Protection sets a protection level, high, standard, or none, per country for SMS traffic.
  • SMS Burst Protection sets an absolute volume threshold per destination country. Cross it, and the burst is blocked automatically.
  • Custom Fraud Alerts watch a metric, such as verification conversion rate, over a defined interval, and when it crosses your threshold, an Alert Action can automatically apply a network block.

Sample request to create a Traffic Rule that blocks a known fraudulent prefix:

POST https://api.nexmo.com/v1/fraud-defender/rules

Authorization: Basic <base64(key:secret)>

Content-Type: application/json

{

  "product": "sms",

  "prefix": "234",

  "reason": "Known IRSF fraud number range", 

  "action": "block"

}

Why pre-send wins: No commitment means no cost when a request is blocked, and enforcement at the network level means the check is invisible to legitimate users. You get Fraud Defender-grade protection without adding friction to good customers or writing per-message integration code

Fraud Defender Standard vs. Advanced vs. Premium

If your traffic runs through Vonage, Fraud Defender is already inside your reach. Here is how the tiers compare for SMS fraud protection and voice coverage.

Capability

Standard

Advanced

Premium 

Coverage 

Integrated for Vonage traffic 

Included with the Verify API at no extra cost

Enterprise add-on 

SMS pumping protection

Yes

Yes

Yes

AIT detection

No

Yes

Yes

SMS burst protection 

Baseline 

Yes

Yes

Geo permissions and prefix rules

Yes

Yes

Yes

Custom alerting 

Standard 

Standard

Custom alerts 

Best for 

Teams starting structured toll fraud detection

Teams running Verify who want fuller AIT and burst coverage 

Enterprises needing custom controls and alerting 

The practical upgrade path: Standard gives you the foundation of prefix rules and AIT detection. Advanced adds SMS burst protection and geo permissions and comes bundled with the Verify API at no additional cost, which is why most verification-led teams should be on it. Premium layers on custom alerts for enterprises with dedicated fraud operations.

The proof is public: Fraud Defender has saved Vonage customers more than $3 million in total cumulative cost savings, with 35.7 billion fraudulent AIT messages sent industry-wide last year costing brands $1.16 billion and 4.8% of global messaging now fraudulent.

Voice toll fraud and how sequential dialing intelligence defends it

Voice fraud follows the same IRSF economics as SMS, but the surfaces are different. On the calling side, toll fraud typically shows up as click-to-call abuse (a fraudster drives calls to premium ranges through a call button) and IVR exploitation (looping or manipulating an interactive voice response flow to rack up premium-rate minutes).

The defense pairs two mechanisms. Prefix rules block or gate calling to high-risk countries and specific ranges before the call connects. Sequential dialing detection, Vonage's internal intelligence, spots the machine-gun dialing patterns typical of voice toll fraud by scoring attack size, recurrence, and age against continuously updated traffic-pumping data. Together they mean voice toll fraud prevention is not an afterthought bolted onto an SMS product, it is a first-class part of the same decision.

If you run any click-to-call, IVR, or programmable calling on the Voice API, treat voice as a live toll fraud surface and apply prefix rules plus sequential dialing from day one.

Compliance, accountability, and your 90-day toll fraud prevention roadmap

Regulators and carriers are increasingly holding enterprises accountable for the fraud that flowsthrough their delivery, not just the fraud that targets their own accounts. That shifts the burden from reactive cleanup after an inflated bill to demonstrable, pre-send controls you can evidence in an audit.

The direction of travel is clear: move from post-send reaction to pre-send decisioning, keep an auditable record of every configured rule and alert.

What to deploy in the next 90 days:

  • Days 1 to 30. Turn on Traffic Rules to block high-risk countries, and if you run the Verify API, confirm Fraud Defender Advanced is active (it is included at no extra cost). Add sequential dialing coverage on any Voice API traffic.
  • Days 31 to 60. Set custom Traffic Rules for your known-good and known-bad ranges, configure AIT Protection levels by country, and baseline your detection rate and blocked-message volume.
  • Days 61 to 90. Review your blocked-traffic volume and detection rate, then tighten AIT Protection levels and SMS Burst Protection thresholds by country.

Your next steps:

Toll fraud prevention FAQs

Select to expand or collapse this FAQ answer.

Toll fraud is any scheme that routes your SMS or voice traffic to premium-rate numbers a fraudster controls, so every message or call generates revenue for them and an inflated bill for you. It is a top category inside the $41 billion telecom fraud loss total for 2025. 

Select to expand or collapse this FAQ answer.

IRSF, or International Revenue Share Fraud, is the revenue-sharing mechanism behind toll fraud. A fraudster controls premium-rate number ranges, drives your traffic to them, and collects a share of the premium charges the carrier bills you. 

Select to expand or collapse this FAQ answer.

Toll fraud is the umbrella term for premium-rate number fraud. Artificially inflated traffic (AIT) is bots deliberately driving OTP volume, and SMS pumping is the SMS-specific variant of AIT. They share an architecture; the attack surface is what differs. 

Select to expand or collapse this FAQ answer.

At industry scale, telecom fraud losses topped $41 billion in 2025. Fraud Defender has saved Vonage customers more than $3 million in documented cumulative savings, a real counterweight to that industry-wide exposure. 

Select to expand or collapse this FAQ answer.

Fraud Defender enforces pre-send protection through configuration rather than a per-message API call. You set Traffic Rules, AIT Protection levels, SMS Burst Protection thresholds, and Custom Fraud Alerts once, and Fraud Defender applies them automatically at the network level for every message and call that follows.

Deskphone with Vonage logo
Outside the US: Local Numbers