You might not be able to signup with us right now as we are currently experiencing a downtime of 15 mins on our product. Request you to bear with us.

Home
Right Chevron Icon
Blog
Right Chevron IconRight Chevron Icon
SMS Pumping Prevention with Network APIs | Message Central

SMS Pumping Prevention with Network APIs | Message Central

Sharjeel Ahmed

•

10
mins read

•

November 14, 2026

Phone receiving a stream of fake OTP messages that drain into a pile of coins, illustrating SMS pumping fraud

Key Takeways

  • SMS pumping (artificially inflated traffic, or AIT) only works when your app sends an SMS. Silent verification sends none.
  • Rate limits, CAPTCHAs and country blocks filter pumping traffic. Network APIs remove the thing being exploited.
  • Number Verification is the main defense. SIM Swap adds a risk signal before any OTP goes out.
  • Coverage is the catch: operators launch network APIs one country at a time. Message Central's Number Verification is live with 57 operators in 23 countries, including AT&T, T-Mobile and Verizon.
  • The pattern that works: risk pre-check, silent verification, then a gated OTP fallback.

TL;DR: The most reliable way to prevent SMS pumping is to stop sending SMS to users you can verify another way. Network APIs such as CAMARA Number Verification let the mobile operator confirm a phone number silently, without sending an OTP, so there is nothing for fraudsters to pump. Keep SMS as a guarded fallback for users on Wi-Fi or uncovered networks. Message Central's NumberVerify2 does all of this in one API call, with Number Verification live in 23 countries.

Losing money to fake OTPs? Test NumberVerify2 on your own phone number in minutes. Sign up free. No credit card, no sales call.

What is SMS pumping (artificially inflated traffic)?

SMS pumping is fraud in which bots trigger large numbers of SMS messages, usually OTPs, from your app to phone numbers controlled by the fraudster's partners, who earn a share of the termination fees. The industry calls it artificially inflated traffic (AIT). It's also known as SMS toll fraud or SMS traffic pumping, and it's a form of international revenue share fraud (IRSF). MITRE ATT&CK lists it as a named attack technique.

A typical attack works like this:

  1. The fraudster gets access to a range of phone numbers through a partner somewhere in the SMS delivery chain.
  2. Bots enter those numbers into your signup, login or password-reset forms.
  3. Your app sends an OTP to each number, and your SMS provider bills you for every message.
  4. The partner collects the termination fee and shares it with the fraudster. Nobody ever enters the code.

The losses are large. Juniper Research estimates that enterprise losses to AIT peaked at about $2.1 billion in 2023. In December 2022, Elon Musk said Twitter was losing about $60 million a year to fake 2FA SMS, and that 390 telcos were involved.

How to spot an SMS pumping attack

Pumping is easy to miss because the traffic looks like real signups. Watch for these signs:

  • OTP conversion drops for one country. Pumped codes are never entered, so the share of OTPs that get verified falls sharply.
  • Requests spike to unusual destinations, often countries where you have few real users.
  • Numbers arrive in sequences from the same prefix or number range.
  • Many OTP requests per session or device, with no completed verifications.
  • Your SMS bill jumps without a matching rise in active users.

If you see these, see our complete guide to SMS pumping for immediate containment steps.

Why rate limits and CAPTCHAs aren't enough

The usual defenses help, but each one still assumes that verification means sending an SMS:

  • Rate limits. Attackers spread requests across thousands of numbers and IP addresses, so each one stays under your limit.
  • Country blocking. It stops pumping to blocked countries, but it also blocks your real users there. Attackers move to destinations you still allow.
  • CAPTCHAs and bot detection. Solving services and human click farms get past them, and every challenge costs you some genuine signups.
  • Number risk scoring. It catches known bad ranges, but it's probabilistic, and new ranges appear constantly.

These layers are still worth having. But they all filter the traffic. None of them removes the thing being exploited.

The root cause: a revenue-share chain

SMS pumping exists because someone gets paid when your message is delivered. Ericsson's white paper on AIT traces the root cause to the long A2P supply chain and to some operator business models. These include revenue-sharing deals such as number-range leasing and white-label MVNOs that can be set up within weeks.

The scale reflects that. Infobip estimates that AIT makes up 5% to 40% of international A2P SMS traffic, depending on the region. Prelude's 2025 report analyzed 205 million authentication requests and flagged 11.83% as fraudulent. BICS, citing Mobilesquared, reports that AIT overtook grey routes as the top threat in international messaging in 2023.

You can't fix the telecom supply chain from your signup form. You can stop feeding it.

What are network APIs?

Network APIs are standard interfaces that let your app ask a mobile operator about a phone number or device in real time. They are defined by the CAMARA project, an open-source effort under the Linux Foundation, and offered across operators through the GSMA Open Gateway initiative. Two of them matter most for SMS pumping:

Network API What it checks How it helps against SMS pumping
Number Verification (silent authentication) The operator confirms that the SIM in the device making the request belongs to the phone number entered No OTP is sent. A bot on a server can't pass the check for a leased number range, because it isn't using that SIM.
SIM Swap Whether the number's SIM was changed recently Flags risky numbers before you send anything. It mainly protects against account takeover, and it's also a useful gate for the SMS fallback.

What is silent network authentication?

Silent network authentication (SNA) is phone verification without a code. Your app sends the verification request over the user's mobile data connection, and the operator confirms that the SIM behind that connection matches the phone number entered. The user doesn't type anything, and the check usually finishes in under a second. For a step-by-step walkthrough, see how silent number verification works.

How network APIs stop SMS pumping

A pumping attack depends on making your system send messages to numbers the attacker doesn't have to possess. Silent verification flips that: the check only passes when the request comes over mobile data from the device holding that SIM. Deutsche Telekom says its Number Verification API removes the toll-fraud exposure that comes with SMS and voice OTP. For every request that completes silently, the attacker earns nothing, because no SMS was ever sent.

SMS OTP WhatsApp OTP NumberVerify2 (silent)
Exposed to SMS pumping High Low: not delivered through the SMS termination chain None for checks completed silently
What the user does Waits for and types a code Opens WhatsApp and types a code Nothing
Proves the SIM is in the device No No Yes
Works on Wi-Fi Yes Yes No, needs mobile data
Coverage with Message Central 190+ countries Where WhatsApp is used 23 countries, 57 operators
See it on your own number. NumberVerify2 runs a silent possession check and a SIM-swap risk check in one API call, with WhatsApp and SMS fallback built in. See how NumberVerify2 works

How to reduce SMS pumping on your platform: silent first, SMS last

The safest design treats SMS as a fallback that has to earn the right to be sent. AWS and Vonage describe the same principle in their reference architecture: fraudulent attempts are blocked before a single OTP is sent.

  1. Pre-check the number. Validate the format, line type and number risk before anything else. Reject obvious junk for free.
  2. Try silent verification. If the user is on mobile data with a supported operator, call Number Verification. If it passes, the user is verified and no message is sent.
  3. Check risk signals. For sensitive actions such as password resets and payouts, call SIM Swap before you trust the number.
  4. Fall back to a non-SMS channel. Where WhatsApp is common, send a WhatsApp OTP next.
  5. Send SMS only as a gated last resort. Apply per-country allow-lists, velocity limits per destination prefix, and a risk score before any SMS goes out.
  6. Monitor OTP conversion by country. A sudden drop for one destination is the clearest early sign of an attack.

Most legitimate mobile users finish at step 2. Attack traffic, which can't pass step 2, gets pushed into the most tightly guarded part of the flow.

Building this yourself means separate contracts with operators or aggregators, plus your own fallback logic. With Message Central, steps 2 to 5 are one integration: NumberVerify2 tries the silent check first and falls back to WhatsApp OTP, then SMS OTP, automatically. It also reports which channel completed each verification, so you can track cost and conversion per channel.

Build this flow with one API. Create a free account, get your API keys and run your first silent verification today. Start free

Where network APIs fall short

Network APIs are a strong control, not a complete one. Plan for these gaps:

  • They need mobile data. Network-based verification runs over the mobile data network, not over Wi-Fi. Desktop users can hand off to their phone, for example with a QR code or deep link, but some users will still need a fallback.
  • Coverage is uneven. Operators launch these APIs one market at a time, so many providers can only offer a handful of countries. See where Message Central stands in the coverage table below.
  • The fallback is still a target. If attackers can force your flow into SMS, for example by appearing to be on Wi-Fi, they will. That's why steps 4 to 6 above matter.
  • They protect OTP flows only. Ericsson's white paper points out that network APIs disrupt the fraud chain for OTP use cases but can't solve AIT as a whole. Marketing or notification SMS triggered by user input needs its own controls.
  • They prove possession, not identity. Silent verification confirms that the right SIM is present, not who is holding the phone. High-risk actions still need step-up checks such as KYC.
  • Failed checks can cost money too. Some providers charge for rejected silent attempts as well as successful ones, so run the pre-check first.

Does silent verification cost less than SMS OTP?

The savings come from two places: pumped SMS you no longer pay for, and real users who finish verification instead of dropping off. Here's an illustrative month for an app with 100,000 verification requests:

Assumption Value Basis
Share of requests that are pumping traffic 12% Close to Prelude's 11.83%
SMS OTP to a real US user $0.0087 Message Central USA OTP pricing
SMS to a pumped international number $0.10 Upper range of the international rates on the same pricing page
Silent verification check $0.035 Assumed for this example; network API pricing varies by country and operator
Real users who can verify silently 70% Assumption
Pumped requests that still get an SMS after the gated fallback 10% Assumption
Monthly cost SMS-first Silent-first with NumberVerify2
Real users verified by SMS 88,000 × $0.0087 = $766 26,400 × $0.0087 = $230
Real users verified silently – 61,600 × $0.035 = $2,156
Pumped SMS paid for 12,000 × $0.10 = $1,200 1,200 × $0.10 = $120
Total $1,966 $2,506

Two things stand out:

  • Pumping losses drop by 90%, from $1,200 to $120 a month, and they stay low during an attack, when SMS-first costs spike.
  • At US SMS prices, the win comes from conversion. SMS is cheap in the US, so silent-first costs about $540 more a month in this example. If silent verification lifts completion by 15 points (our silent network authentication API guide works through this), that's about 9,200 more verified users a month. At $0.50 of value per user, that's about $4,600. In markets where SMS costs more than a silent check, silent-first is also cheaper outright.
Want these numbers for your own traffic? Share your monthly OTP volume and top countries, and our team will estimate your pumping exposure and what silent-first would cost you. Book a call with an expert

Network API coverage: where you can stop SMS pumping today

Coverage is the biggest practical problem with network APIs. Operators launch them one market at a time: three operators in Spain, three in Colombia, two in Uruguay. A provider connected to only a few of these can protect a small slice of a global user base, and everyone else falls back to SMS.

Message Central's Number Verification is live in 23 countries with 57 operators, and SIM Swap in 19 countries. That includes all three major US carriers (AT&T, T-Mobile and Verizon), all three major operators in Canada, Germany and Japan, and the main operators in Brazil, Indonesia and India.

Country Number Verification (live operators) SIM Swap
Americas
Argentina Claro, Movistar, Personal Live
Brazil Telefónica, TIM, Vivo Live
Canada Bell, Rogers, Telus Live
Chile Entel Coming soon
Paraguay Claro, Personal, Tigo Live
Peru Coming soon Live (Entel)
United States AT&T, T-Mobile, Verizon Live
Europe
Austria Magenta Live
France Bouygues, Orange Live
Germany Deutsche Telekom, O2 Telefónica, Vodafone Live
Greece Cosmote, Vodafone Live
Italy TIM Live
Netherlands KPN, Odido, Vodafone Live
Spain MasOrange, Movistar, Vodafone Live
United Kingdom Vodafone Live
Asia-Pacific
Australia Optus, Telstra Live
India Jio, Airtel (Vi coming soon) Live
Indonesia Indosat, Telkomsel, XLSmart Live
Japan KDDI, SoftBank, NTT Docomo Live
Malaysia Maxis, CelcomDigi, U Mobile, Tune Talk, TM Coming soon
Philippines Smart, Globe Coming soon
Singapore Singtel, M1, StarHub Coming soon
Taiwan Taiwan Mobile, FET, Chunghwa Telecom Live
Thailand AIS, True-DTAC Coming soon

Beyond these two APIs, KYC Match is live in 10 countries and Device Swap in 4. Where silent verification isn't available yet, the same NumberVerify2 call falls back to WhatsApp or SMS OTP, so your integration doesn't change as coverage grows.

Don't see your market, or need a specific operator? Coverage is expanding every quarter. Talk to an expert about your markets

Stop paying for OTPs nobody reads

SMS pumping is a bill you keep paying for as long as SMS is your default. NumberVerify2 makes silent verification the default in 23 countries and keeps WhatsApp and SMS as guarded fallbacks, all through one API and one bill.

  • Start free: create an account, get API keys and test NumberVerify2 on your own number. Sign up free
  • Talk to an expert: get a coverage check for your markets and a pumping cost estimate. Book a call
Need to verify identity as well as the phone number? Pair NumberVerify2 with eKYC Now for document and ID checks in the same account.

FAQ

What is SMS pumping? SMS pumping is fraud in which bots trigger OTP messages from your app to number ranges controlled by the fraudster's partners, who share the termination fees. You pay for every message, and no real user receives it.

How do I prevent SMS pumping? Verify users silently with a network API such as Number Verification wherever possible, so no SMS is sent. Use WhatsApp OTP as the next fallback, and send SMS only after country allow-lists, velocity limits and risk checks.

Is SMS pumping the same as AIT, SMS toll fraud or IRSF? Mostly. AIT (artificially inflated traffic) is the broader industry term, and SMS toll fraud means the same thing. SMS pumping is a form of international revenue share fraud (IRSF) applied to SMS.

Does silent network authentication stop SMS pumping? For every user it verifies, yes: no SMS is sent, so there is nothing to pump. Users who can't be verified silently fall back to OTP, and that fallback still needs rate limits and risk checks.

What is a network API? A network API lets an app ask a mobile operator about a phone number or device, for example whether a SIM matches a number or was recently swapped. Most are standardized by CAMARA and offered through GSMA Open Gateway.

What is CAMARA? CAMARA is an open-source project under the Linux Foundation that defines standard network APIs, such as Number Verification and SIM Swap. GSMA Open Gateway is the operator initiative that makes those APIs available across networks.

Do network APIs work on Wi-Fi? No. Network-based Number Verification needs the request to travel over mobile data. On Wi-Fi, apps either hand off to mobile data or fall back to another channel. NumberVerify2 handles that fallback automatically.

Which countries does Message Central cover? Number Verification is live in 23 countries and SIM Swap in 19, including the US, Canada, Brazil, most of Western Europe, India, Indonesia and Japan. See the coverage table above.

Will network APIs replace SMS OTP? Not soon. Coverage gaps and Wi-Fi users mean SMS remains a necessary fallback. The goal is to make SMS the exception, not the default.

How do I try NumberVerify2? Create a free account, generate API keys and run a test verification on your own phone number.

Ready to Get Started?

Build an effective communication funnel with Message Central.