Gambling and betting
Phone Intelligence for Betting and Gambling Operators
Bonus abuse is the most expensive fraud problem in online gambling, and the cheapest version of it runs on disposable phone numbers. A number-type lookup at registration catches VoIP and virtual numbers before the welcome offer is claimed. Telebase returns carrier, number type, active status and SIM swap detection in a single API call. Per-query pricing, no platform fee, no seat licence.
Bonus abuse starts with a phone number
The economics of bonus abuse are simple. A welcome offer worth £20 in free bets costs the operator £20 per account. A fraudster who opens 50 accounts claims £1,000. The limiting factor is phone numbers: each account needs a unique number to pass SMS verification.
Buying 50 SIM cards is slow and expensive. Spinning up 50 non-fixed VoIP numbers through a wholesale provider takes minutes and costs almost nothing. The numbers pass format validation. They receive the OTP. The accounts are created, the bonuses are claimed, and the operator pays out before anyone notices.
A number-type check at registration catches this at the point of entry. If the number is non-fixed VoIP, the sign-up is blocked or routed to a higher-friction path before the welcome offer is ever issued.
What phone intelligence catches
The fraud types that matter to a gambling operator map directly to the signals a phone lookup returns.
The numberType field identifies VoIP and virtual numbers. Non-fixed VoIP is the primary tool for creating multiple accounts. Screening it at registration is the single highest-value check for bonus abuse prevention. See blocking disposable numbers at sign-up for the implementation pattern.
Gnoming rings use real or stolen identities paired with cheap phone numbers to open accounts at scale. The identity documents may pass verification, but the phone numbers are typically VoIP or recently activated. Combining numberType with carrier catches the pattern: a UK identity paired with a number on a wholesale VoIP carrier is a strong signal, even when the documents look legitimate.
A customer's account is compromised when an attacker gains control of their phone number, intercepts the OTP, and resets the password. The most common method is SIM swapping: the attacker convinces the carrier to transfer the number to a new SIM. A SIM swap check before any OTP-gated action (password reset, withdrawal, payment method change) catches this before the takeover succeeds.
A player on the self-exclusion register who opens a new account needs a new phone number. If that number is VoIP or disposable, number-type screening catches it at the same point it catches bonus abuse. This is not a complete solution to self-exclusion enforcement, but it closes the cheapest route around it.
Signals returned per lookup
- Number type: mobile, landline, fixedVoip, nonFixedVoip, tollFree, voicemail. The primary signal for bonus abuse and multi-accounting.
- Carrier: the network operator serving the number. Cross-reference against the customer's stated country and identity.
- Country: the number's country of origin. A mismatch with the player's registered address is worth flagging.
- Active status: whether the number is currently live on the network. Inactive numbers at registration are a red flag.
- SIM swap: whether the SIM card behind the number was recently changed. Catches account takeover before OTP-gated actions like withdrawals and password resets. More on SIM swap detection.
Where it fits in the registration flow
The lookup runs after the player submits their phone number and before the OTP is sent. This is a passive check: the player does nothing and sees nothing. The API call takes milliseconds and does not add visible friction to the sign-up.
{
"phoneNumber": "+447700900000",
"numberType": "mobile",
"carrier": "Three",
"country": "GB",
"active": true,
"simSwap": false,
"simSwapAt": null,
"_meta": { "activeSource": "LINE_STATUS" }
}
This number is a live UK mobile on a recognised carrier. Low risk. Proceed to OTP.
{
"phoneNumber": "+447911123456",
"numberType": "nonFixedVoip",
"carrier": "Vonage",
"country": "GB",
"active": true,
"simSwap": false,
"simSwapAt": null,
"_meta": { "activeSource": "VALID" }
}
Non-fixed VoIP on a wholesale carrier. High risk for bonus abuse. Block or route to manual review before issuing the welcome offer.
UKGC context
The UK Gambling Commission's licence conditions require operators to have effective systems for preventing money laundering and detecting fraudulent activity. Phone intelligence is not a named regulatory requirement. It is an operational control that strengthens the systems the UKGC does require: customer identity verification, multi-accounting detection, and fraud prevention at onboarding.
The practical value is in the welcome-offer economics. Every bonus-abuse account that passes registration costs money directly. A number-type screen that catches even a fraction of VoIP-based multi-accounting pays for itself on the first day.
Germany: GGL-licensed operators
Germany's gambling regulation under the GGL (Gemeinsame Glücksspielbehörde der Länder) requires identity verification and responsible-gambling controls for all licensed operators. The same phone intelligence signals apply: number-type screening at registration to catch multi-accounting, carrier and country cross-checks against the player's identity, and SIM swap detection (when live) for account security.
German mobile numbers on recognised carriers (Telekom Deutschland, Vodafone, o2) are lower risk. Numbers resolving to wholesale VoIP providers warrant the same scrutiny as in the UK market. Telebase covers German numbers with the same lookup and response shape.
Pricing for high-volume operators
Gambling operators process high registration volumes, especially around major sporting events. Per-query pricing means cost scales linearly with registrations. There is no platform fee, no annual commitment and no seat licence.
Every account starts with 100 free queries. Standard pricing is $0.05 per lookup, with volume pricing available on request. A pre-OTP check that prevents one bonus-abuse account per day covers its own cost many times over.
See carrier lookup API pricing compared for a breakdown against alternative providers.
Getting started
Telebase is in private beta. Request early access, receive an API key, and integrate the lookup into your registration flow. The check runs before the OTP send, adds no visible friction, and returns structured JSON your fraud engine or AI agent can consume directly.
Request early access