Sports Betting App Development Company: Sportsbook and Fantasy Apps for Licensed Operators and B2B Suppliers

Updated September 2026 · Written and maintained by the Progression Agency strategy team

A sports betting app development company designs and builds the wagering apps, player account systems and integrations that licensed sportsbooks, fantasy operators and B2B suppliers put in front of customers: odds and bet placement, wallets and payments, identity and age checks, geolocation, responsible-gaming tools and the back office that regulators audit. Progression Agency does that work as a development partner; the operator holds the gaming license, and Progression holds no gaming license of any kind. Progression Agency is based in New York City and builds for operators and suppliers across the United States and worldwide.

What does a sports betting app development company build?

It builds the software a licensed operator or supplier needs to take a lawful wager on a phone and settle it correctly: the player app, the platform services behind it and the integrations that connect both to data, payments and compliance vendors. Which parts are custom and which are licensed from a platform provider is the first decision in every project.

Player-facing sportsbook apps

Native or cross-platform apps for iOS and Android, plus a web version: sport and market navigation, the bet slip, in-play betting, account and cashier screens, responsible-gaming tools, promotions and notifications. Sports betting mobile app development is mostly about speed and clarity, because prices move while the player is deciding.

Fantasy, pick’em and free-to-play apps

Contest lobbies, drafts, live scoring, leaderboards and prize distribution for daily fantasy and season-long formats, and free-to-play predictor games that operators, teams and media brands use to build an audience before any money is involved.

Operator back office

Customer management, identity review queues, payment reconciliation, responsible-gaming case management, promotions management, risk dashboards and the reports regulators ask for. It is the least visible part of a sportsbook and the easiest to underestimate.

B2B components for suppliers

Odds display widgets, bet builders, data APIs, player account modules and adapters that let a supplier’s product plug into several operators’ platforms. Sports betting software development for suppliers is judged by how cleanly it integrates and how easily it passes testing.

How much of sports betting happens in the app?

In New Jersey, nearly all of it. From January through August 2026, online sportsbooks produced $657.9 million of the state’s $671.4 million in sports wagering gross revenue, about 98 percent, according to the Division of Gaming Enforcement’s August 2026 revenue release.

Retail counters are a small and shrinking share

The same release puts revenue from sportsbook lounges at $13.4 million for the first eight months of 2026, down 23.2 percent on the same period of 2025, while online sportsbook revenue fell 4.8 percent. In August alone, online books produced $59.7 million and lounges $1.7 million.

Revenue follows the sports calendar

The Division attributed August’s 25.0 percent year-over-year drop in sports wagering revenue mainly to a later start to the fall calendar for certain sports, including college football, and to a lower overall win percentage. Releases, promotions and capacity plans are scheduled around that same calendar.

New York’s volume, in the Comptroller’s figures

New York’s State Comptroller reports that more than $91.2 billion in mobile sports bets were placed from the January 2022 launch through the end of state fiscal year 2026, and that the average wager in 2025 was $42 (release of September 16, 2026). A very large number of small wagers is the load the app, the wallet and every vendor behind them must carry.

What that means for the product

The phone is the sportsbook, not a channel for it. Registration, location checks, deposits, the bet slip and withdrawals all happen in the app, so crash rates, verification pass rates and speed on a weak connection are revenue metrics. Where an operator also runs retail counters or kiosks, we design them to share the same accounts and ledger, and our product design work starts from the phone screen.

Can I create a betting app?

You can build the software; only a licensed operator can take real-money bets through it. Anyone planning a betting app has three lawful routes to market, and the route decides the build.

The operator holds the license, not the developer

Apple’s App Store Review Guidelines say apps in highly regulated fields, gambling among them, should be submitted by the legal entity that provides the service rather than by an individual developer, and that real-money gaming apps need the necessary licensing and permissions where they are used. The finished app is therefore published under the operator’s developer account. Progression Agency holds no gaming license, does not operate a sportsbook and never accepts wagers.

Suppliers and vendors have obligations too

States regulate the businesses around the operator. New Jersey requires companies that provide payment processing touching patron accounts, customer identity, age verification or geolocation verification for internet and mobile gaming to be licensed as ancillary casino service industry enterprises under N.J.A.C. 13:69J-1.2. Michigan requires certain vendors to register with its Gaming Control Board before providing goods or services to an operator or supplier. If a state requires a development vendor like us to register, that registration is in place before work starts in that state.

Questions to settle before commissioning a build

A development partner can only scope accurately once these are answered, and most of them are commercial rather than technical.

• Who holds the license in each target state, and who will publish the app?
• Which platform provider, if any, supplies the betting engine and trading tools?
• Which states come first, and which technical standard does each one apply?
• Which identity, geolocation and payment vendors are already approved in those states?
• Is the first release real-money, fantasy, or free-to-play?
• Who inside the business signs off on compliance before each release?

Can a betting app work without ID?

Not one that follows the rules licensed sportsbooks work under. GLI-33 requires identity verification before a player can place a wager, authenticating at least legal name, physical address and age, and checking exclusion lists; the account only becomes active once those checks pass. An app that promises betting without ID checks is advertising that it skips them.

White-label, turnkey or custom: which sportsbook model fits?

For most operators we recommend a licensed platform with a custom product on top; a fully custom platform pays off only for a business that wants to own pricing, risk and certification itself. The model sets the budget, the timeline and the approvals you carry.

White-label sportsbooks

A white-label sportsbook runs on the provider’s platform, trading team and usually its front end, with the operator’s brand, marketing and customer relationship on top. It is usually the quickest route to market and the least differentiated one: the provider’s roadmap becomes yours, and leaving later means migrating players, balances and history.

A turnkey platform with your own front end

The operator licenses the betting engine, trading tools and player account core from a certified platform supplier, and commissions its own apps, bet slip, promotions and back-office tools through the platform’s APIs. Our sportsbook software development work is designed around this model: the certified core stays with the supplier, and the product players see is yours.

A fully custom platform

The business builds its own betting engine, pricing and risk tools, player account management and back office, and takes the whole system through lab testing in each state. It offers full control of product and data, with the longest timeline and the widest certification scope. A sportsbook software development company quoting this scope should be able to show how its backlog maps to GLI-33 or each state’s standard.

Hybrid: buy the core, build what differentiates

A hybrid roadmap starts turnkey and replaces components over time, such as a custom bet builder, a promotions engine or a separate fantasy product sharing the same wallet. Each replacement goes through the same testing and change approval as the original. The architecture question behind it is covered in our comparison of monoliths and microservices.

Odds, data feeds and settlement

A sportsbook is only as good as its data: prices, event status, results, and in some states the official league data used to settle in-play and prop bets. Integrations with data and odds providers are among the most demanding parts of the build.

Pre-match and in-play prices

Prices come from the operator’s trading platform or a licensed odds provider and stream to the app as they change. GLI-33 expects the player to see current odds and prices for available markets, and to be asked to confirm a wager again when the price changes before acceptance, unless they have opted in to auto-accept where the regulator allows it.

Official league data in Illinois

Illinois treats a tier 1 wager as one decided solely by the final score or outcome and placed before the event starts; everything else is tier 2. Under 230 ILCS 45/25-25, licensees may use any data source for tier 1 wagers, but within 30 days of a sports governing body notifying the Board, tier 2 wagers on its events must be settled with official league data, unless the league cannot supply a feed for that type of wager or cannot supply it on commercially reasonable terms. The settlement service has to know, per league and per state, which feed it may use.

Approved events and house rules

States approve what can be bet on. Iowa’s Racing and Gaming Commission publishes a list of approved sports wagers; any offering not on it needs Commission approval first, and each operator’s house rules on payouts, the definition of an official contest and the source of results information must be approved too. The app’s market catalog is therefore configured per state, never globally.

Latency, suspensions and resettlement

In-play markets suspend in seconds, so the app subscribes to price streams, shows suspensions instantly, places bets through idempotent requests that cannot double-submit, and handles resettlement when a result is corrected. Every change is logged for the audit trail the lab and regulator will ask for.

How fast does in-play betting need to be?

Fast enough that the price on screen is still the price when the player taps, and honest when it is not. GLI-33 expects the published rules to warn in-play bettors that connection speeds and broadcast latency can leave them behind players with fresher information, and allows a delay to be built into the registered time of an in-play wager to prevent past-post bets.

Acceptance delays are a control, not a defect

GLI-33 defines a past-post wager as one made after the result is accepted or after the chosen participant has gained a material advantage, such as a score, and its section A.2.3 asks the operator’s internal controls to describe how such wagers are prevented. Where an acceptance delay is used, the app shows a clear pending state and then confirms, rejects or re-prices the wager; it never leaves the player guessing.

Auto-accept has to be the player’s choice

Under GLI-33 section 4.3.3, a system may auto-accept price changes only where the regulator allows it, only after the player opts in manually, never by default, with every option explained and an opt-out available at any time. The standard’s own examples are accepting only higher prices, or lower ones as well. The setting belongs on the bet slip, where the player can see it.

Suspensions leave an audit trail

When wagering on a market stops mid-event, GLI-33 A.6.3 calls for an audit-log entry with the date, time and reason. We treat a suspension as an event pushed to every device at once: the selection is disabled, the bet slip explains why, and the log records whether a trader or an automated rule triggered it.

Micro-markets need approval first

Pitch-by-pitch, point-by-point and shot-by-shot markets are where latency matters most, and where approvals are narrowest. Iowa’s approved wagers list, for one, does not approve pitch-by-pitch baseball markets, point-by-point markets in tennis, table tennis, volleyball or badminton, or shot-by-shot golf markets, and approves in-game wagering only for wager types its offerings table already lists.

Losing the data feed, and live video that lags

Where the regulator requires it, GLI-33 A.6.2 has the operator log any loss of the statistics or line feed with its time, duration, nature and impact, and keep that record for 90 days or as the regulator directs. Our builds suspend affected markets automatically rather than trading on stale prices. Live video reaches the app by a different route from the data and can drift behind it, so the bet slip trusts the feed, not the picture; playback uses the same components as our video streaming apps.

How are bets graded and settled?

Automatically, from confirmed results, under house rules the regulator has approved. The grading engine applies those rules market by market, credits winners, and keeps every correction visible to the player and to the auditor.

Rules first, code second

GLI-33 A.5.1 requires comprehensive wagering rules approved by the regulator, time-stamped whenever they change, and applied as they stood when each wager was accepted. Section A.5.2 lists what the rules must cover, including ties and dead heats, canceled or withdrawn events, parlays with a canceled leg, whether odds lock at placement, and how payouts are rounded. The settlement service reads the same versioned rule set the player sees.

Confirming the result

Before winners are declared, GLI-33 A.6.6 calls for a policy to confirm results from qualified and approved sources, unless an external feed automates it; a fallback for when that feed is unavailable; and a procedure for changed results. Where a state requires official league data, as Illinois does for tier 2 wagers once a league asks, confirmation checks that source.

Voids need a reason, and operator voids need approval

Under GLI-33 A.6.4, a wager can only be changed by voiding or canceling it under the operator’s published cancellation policy. An operator-initiated cancellation must give the player a reason, such as a past-post wager, and an operator may not void or cancel any wager without the regulator’s prior approval. Voids therefore run through an approval workflow in the back office, not a delete button.

Corrections and resettlement

Statistics get corrected after games end. GLI-33 section 4.4.1 requires any change of results to be made available to players, and section 2.8.8 lists changes to event or market results among the significant events the system logs. Resettlement reverses the original credit, applies the corrected grade and writes both entries to the ledger, so the player’s statement still reconciles.

No after-the-fact deductions in Iowa

Iowa’s approved wagers list rules out the so-called Tattersalls Rule 4 and any equivalent post-wager deduction in individual or futures wagering, with a narrow baseball exception for “action” markets offered alongside “listed” ones when a starting pitcher changes. Settlement logic that travels across states switches rules like this per jurisdiction.

How do parlay and same-game parlay engines work?

A parlay engine combines selections into one wager, prices the combination and settles it leg by leg under published rules. Same-game parlays add a pricing problem, because legs from one game are correlated, so the price has to come from a model that accounts for that, typically the trading platform’s or a specialist pricing supplier’s, not from multiplying the legs together.

What the player has to see

GLI-33 section 4.3.2 requires each selection to be identified, groupings such as parlays to be shown as groupings, and a chance to review and confirm before the wager is submitted. On a phone, that means a bet slip listing every leg, the combined price and the potential payout above the confirm button.

Why same-game legs cannot simply be multiplied

A standard parlay multiplies independent prices. Outcomes within one game are not independent: a quarterback’s passing yards and his team’s points tend to rise together, so multiplying their prices would misprice the combination. Pricing correlated legs is a modeling job for the trading side; the app’s job is the request-for-price flow, the bet slip and clear handling of legs that cannot be combined.

When a leg is voided

GLI-33 A.5.2 requires the published rules to say what happens when a parlay leg is canceled or withdrawn and how fixed odds may be adjusted as a result, for example by dropping the voided leg and settling the rest as a smaller parlay. Whatever rule the operator publishes and the regulator approves, the engine applies it exactly and shows the adjusted price in the player’s history.

Which legs a state allows

A parlay can only combine markets the state has approved. Iowa, for example, excludes player props on individual athletes in a college game involving an Iowa college team, prohibits player props for athletes from Iowa colleges outright, and does not authorize speculative matchups such as a Super Bowl point spread set before the participants are known. The engine checks each leg against the state’s catalog before it asks for a price.

How does cash-out work in a betting app?

Cash-out lets a player settle a wager early for an amount the book offers before the event ends. GLI-33 frames it as a redemption for an adjusted payout before the event concludes, available only where the operator offers it and the regulator allows it.

Where the offer comes from

The cash-out value is a live price on the wager’s remaining risk, calculated by the trading platform and refreshed as the event moves. The app only displays it; the calculation stays on the server, where it can be logged and audited.

Accepting a number that keeps moving

The flow mirrors the bet slip: the player sees an amount, confirms it, and receives either that amount or a clear message that the value changed, with a new offer. The request carries an idempotency key, so a double tap on a weak connection never cashes out twice, and offers suspend whenever the market does.

Partial and automatic cash-out

Some books let players cash out part of a stake, or set a value at which cash-out happens automatically. Each is a separate feature to scope, test and, where the state requires it, describe in the approved rules, and each sits behind its own per-state switch.

Records a regulator can follow

Every accepted offer is a settlement event: the original wager, the amount paid and the time go to the ledger and into the player’s transaction history, which GLI-33 section 2.5.7 requires to hold enough detail for players to reconcile it against their own records.

• The offer is priced on the server by the trading platform, never in the app.
• One accepted offer per wager, enforced by an idempotency key.
• Offers suspend with the market and return when it reopens.
• Partial and automatic cash-out ship behind separate per-state switches.
• Every accepted offer is written to the ledger and the account statement.

What trading and risk tools does a sportsbook back office need?

Tools to see liability as it builds, to limit or refuse wagers, to suspend markets in one action, and to flag betting that looks wrong. GLI-33 asks operators to document automated and manual risk management, and to monitor for suspicious wagers and unusual swings in volume or prices.

Liability by market and outcome

The core trading view shows what the book pays on each outcome of each market and how that is changing. GLI-33’s operator liability report (section 2.9.3) covers money held for players, wagers on future events and winnings owed but unpaid; the trading view is the live version of the same numbers, built on our dashboard stack.

Stake limits, including limits a regulator sets

Operators reserve the right in their published rules to refuse or limit wagers (GLI-33 A.5.2(o)), and some regulators cap stakes themselves. Iowa caps wagers at $1,000 on Korean Baseball Organization games, $500 on leagues such as the Professional Bowlers Association and Professional Bull Riders, and $250 on the Indoor Football League, and makes the sportsbook responsible for setting in-game limits that stay within those caps. Limits therefore live in configuration by state, league, market and player.

Integrity alerts

Alerts cover the three areas GLI-33 A.8.1 names: suspicious wagers that may indicate cheating or manipulation, irregular patterns that suggest collusion or automated betting software, and unusual swings in volume or price. Each alert records who reviewed it, what was done and whether it was reported, and to whom, under the state’s rules.

Large wagers, large wins and money-laundering signals

GLI-33 section 2.8.8 treats single or aggregate large wagers and wins above a value the regulator sets as significant events, and A.8.2 asks for monitoring of accounts opened and closed within short periods and of deposits withdrawn without wagering. Thresholds are configuration, set per state, and alerts land in the same case queue the compliance team already works from.

Wallet, payments and withdrawals

The cashier is where regulation, fraud control and customer patience meet. It has to accept the payment methods the state and the processors allow, keep every cent traceable, and pay out without friction once the checks are done.

Why in-app purchase is off the table

Apple’s Guideline 5.3.3 says apps may not use in-app purchase to buy credit or currency for real money gaming of any kind, and Google Play’s real-money gambling policy says a gambling app must be free to download and must not use Google Play In-app Billing. Deposits and withdrawals run through the operator’s own processors instead.

Processors, licensing and funds

Processors that touch patron accounts are licensed businesses in states such as New Jersey, so the processor list is set by the operator and its compliance team, state by state. GLI-33 expects every transaction to be confirmed or denied, funds to be unavailable for wagering until they are received or authorized, and payouts to reach the player, typically in an account in the player’s own name.

Card data and PCI DSS

The PCI Data Security Standard applies to any business that stores, processes or transmits cardholder data. The cheapest compliance is not to touch card numbers at all: the app uses the processor’s tokenized fields, and the platform stores only tokens and references.

Withdrawals, limits and reconciliation

Withdrawals are checked against identity, anti-money-laundering and bonus-terms flags before release. Deposit limits set by the player are enforced in the wallet itself, and a daily reconciliation matches the ledger to processor settlements so discrepancies surface before a regulator finds them.

How are player funds protected?

By keeping players’ money apart from the operator’s, making every movement traceable, and never letting money move between players. GLI-33 A.4.2 describes player funds held in trust in a special-purpose segregated account controlled by an entity that is not the operator and has at least one independent director, with procedures that keep the funds from being commingled or claimed by the operator’s creditors. Each state’s rules set the exact arrangement.

Reserves the operator holds

GLI-33 A.4.1 adds processes for adequate cash reserves, as the regulator determines, including segregated accounts for player balances and operating funds for unclaimed and potential winning wagers. The platform supplies the numbers: balances held, wagers on future events and winnings owed but unpaid.

A ledger, not a balance field

Every deposit, wager, win, bonus, adjustment and withdrawal is an immutable ledger entry with its own ID, and balances are derived from those entries. GLI-33 section 2.5.7 requires a player’s transaction history to carry unique transaction IDs and enough detail to reconcile against their own records; a double-entry ledger, the pattern our payments engineering uses, makes that a query rather than a project.

Money never moves between players

GLI-33 section 2.5.6 rules out transfers between two player accounts and keeps deposits unavailable for wagering until they are received or authorized. Send-to-a-friend features and shared balances are out of scope, whatever the growth plan says.

Excluded, inactive and unclaimed balances

An excluded player can still withdraw cleared funds unless the reason for the exclusion prohibits it (GLI-33 A.3.8). Inactive accounts that hold money need protection from unauthorized access and a procedure for unclaimed funds, including returning them to the player where possible (A.3.9).

KYC, AML, age and identity checks

Before a first wager, the app has to know who the player is, that they are old enough and that they are not excluded; afterwards it has to watch for money laundering. These checks decide how smooth onboarding feels, so they are designed as carefully as the bet slip.

Identity and age at registration

GLI-33 section 2.5 allows third-party identity services where the regulator permits them, requires one active account per player unless authorized otherwise, and activates the account only after age and identity verification pass, exclusion lists are checked and the player accepts the terms and privacy policy.

Authentication and inactivity

GLI-33 requires re-authentication after 30 minutes of inactivity, or a period the regulator sets, and allows a simpler method such as biometrics or a PIN, with full authentication again at least once every 30 days. Forgotten credentials are reset through multi-factor authentication. Michigan’s regulator has issued a separate memo on identity verification and strong authentication (November 2024) and one on protecting personal information and data breach notification.

Anti-money laundering

Casinos covered by the Bank Secrecy Act run a written compliance program that includes procedures to determine and verify a person’s name, address and Social Security number (31 CFR 1021.210), file reports on currency transactions of more than $10,000 (1021.311) and report suspicious transactions involving $5,000 or more within 30 calendar days of detection (1021.320). How these rules apply to a particular online sportsbook is a question for the operator’s compliance team and counsel; the app’s job is to capture the data and surface the alerts they need.

Prohibited participants

GLI-33’s operational appendix bars athletes, coaches, referees, team owners and employees, league officials, sports agents and union staff, and people in their households, from wagering on events in their own sport. Registration and wager placement both check the player against the operator’s prohibited-participant lists.

Geolocation compliance

A licensed app may accept a wager only from a person inside a permitted area, so every bet is preceded by a location check that has to be accurate and hard to fool. Players only notice it when it fails.

Why the location check exists

The federal Wire Act prohibits people in the betting business from using wire communications to transmit sports bets across state lines, with a safe harbor for betting information sent between places where the betting is legal. The Unlawful Internet Gambling Enforcement Act’s intrastate exception depends on state rules with age and location verification. State laws say it directly: Illinois licensees may only accept a wager from a person physically located in the state. Apple requires real-money gaming apps to be geo-restricted, and Google Play requires them to block areas the license does not cover.

What the check has to catch

GLI-33 section 2.7 asks for detection of fake location apps, virtual machines and remote desktop programs before each wager, checks for known VPN and proxy services, blocking of rooted or jailbroken devices, protection against man-in-the-middle attacks, and monitoring for wagers from one account at locations too far apart to travel between in the time recorded.

State specifications and testing

Michigan’s Gaming Control Board publishes technical bulletins that include geofencing specifications and geofencing testing requirements, alongside bulletins on server and equipment location, communication standards, data logging and software approval. New Jersey licenses geolocation verification providers as ancillary businesses. The geolocation vendor is therefore chosen from providers the operator’s states already accept.

Designing for the border

Players near a state line fail checks they do not understand. The app explains what happened, offers a retry, links to a help article and never blocks browsing, only wagering. Keeping content readable while guarding the wager is also what keeps the operator’s site visible in search, which our SEO work for licensed casinos and sportsbooks depends on.

Responsible-gaming tools built into the product

Responsible-gaming features are product requirements, not a settings page: limits the system enforces, exclusions it checks, and alerts that reach a trained person. New Jersey, for one, specifies the triggers as well as the tools.

New Jersey’s Division of Gaming Enforcement, in its Responsible Gaming Best Practices, requires each provider to appoint a Responsible Gaming Lead with dedicated staff and to run minimum automated triggers. They include total deposits over a set amount in 24 hours (the Division recommends $10,000) and over 90 days (it recommends $100,000), a visit to the self-exclusion page that was not completed, a second cool-off request within a set period (it recommends 45 days), three requests to raise a deposit or loss limit within 24 hours, repeated withdrawal cancellations, turnover above a set amount over 90 days (it recommends $1,000,000) and a 50% rise in time on site compared with the previous two weeks. Alerts lead to a phased intervention: a message, then a video tutorial, then direct contact from a responsible-gaming professional where warranted.

What can a betting app send players, and when?

Service messages about a player’s own account can go out whenever they are needed; marketing needs consent, an easy way out and a check against exclusion lists before every send. Responsible-gaming messages are a third category, and state rules require them in advertising as well as in the product.

Transactional or marketing?

Deposit receipts, withdrawal updates, verification requests, security alerts and settled-bet notices are transactional. Under the FTC’s CAN-SPAM compliance guide, transactional or relationship email is exempt from most of the Act’s provisions, though it may not carry false or misleading routing information. A message that promotes an offer is commercial and follows the full rules.

Commercial email

The same guide requires a valid physical postal address, an opt-out that keeps working for at least 30 days after sending, and opt-outs honored within 10 business days, and it puts penalties at up to $53,088 for each email in violation. Our email programs suppress opted-out and excluded players centrally, so no campaign tool can get around the list.

Texts and calls

In Campbell-Ewald Co. v. Gomez (2016), the Supreme Court treated it as undisputed that a text message to a cell phone is a call under the Telephone Consumer Protection Act. The FCC’s rule at 47 CFR 64.1200 requires prior express written consent for marketing calls made with an autodialer or a prerecorded voice, bars telephone solicitations before 8 a.m. or after 9 p.m. at the recipient’s location, and allows no more than 10 business days to honor a revocation of consent. Our SMS programs for betting brands are built around those rules.

Excluded players are suppressed everywhere

GLI-33 A.3.8 says advertising and marketing material must not specifically target excluded players, and New York’s rules bar misleading embedded keywords or similar methods used to attract people under the wagering age, self-excluded players, or people who are or may be problem gamblers. Suppression lists sync from the player account system, and from the state’s self-exclusion list where one is shared, before every send.

Responsible-gaming messages

New York’s rules require each advertisement to state a problem gambling hotline, and one approved message reads “Gambling Problem? Call (877-8-HOPENY) or text HOPENY (467369)” (9 NYCRR 5325.6(b)). Its sports wagering rules also require licensee websites with betting content to remind visitors of the legal wagering age (9 NYCRR 5329.37(f)). In the product, GLI-33 A.3.7 requires advance notice of operator-imposed limits and lets a player loosen a self-imposed limit only after 24 hours’ notice, or as the regulator requires.

What is betting app promotion, and how does a bonus engine work?

Betting app promotion covers the offers an operator uses to win and keep players, such as bonus bets, deposit matches, odds boosts and loyalty rewards, plus the software that decides who qualifies, tracks each award and pays it out. In a licensed app every offer is also a regulated disclosure, so the engine and the wording are built together.

Offer types the engine has to support

Bonus bets awarded after a qualifying wager, deposit matches with wagering requirements, odds and profit boosts on selected markets, parlay insurance, referral rewards and loyalty points. Each is a rule set (eligibility, qualifying action, award, restrictions and expiry) that the operator configures without an app release.

Eligibility is a state question

Promotion rules differ by state, so eligibility checks where the player is verified to be, as well as account status, prior use and exclusion status. GLI-33 section 2.5.8 adds that loyalty awards must be equally available to every player who reaches the qualifying level, and that point redemptions are secure transactions the system records.

Bonus money in the ledger

Promotional credit is tracked apart from cash. For each promotion, GLI-33 section 2.8.6 requires its start and end, current balance, and totals issued, redeemed, expired and adjusted under a unique ID; section 2.5.7 puts bonus credits added or removed on the player’s statement; and section 2.8.8 logs any change to promotion parameters as a significant event.

Wording the regulator will read

New York shows how specific this gets. Its rules require material terms and limitations to be disclosed clearly and conspicuously, and the amount a patron must wager from their own funds to appear in the same font size and style as the bonus amount itself (9 NYCRR 5329.37(c)). Our promotion screens render the terms from the same record the engine enforces, so the offer and its fine print cannot drift apart.

Offers and responsible gaming

In our builds the promotions engine reads the same responsible-gaming status as the wallet, so offers pause for players on a cool-off, under review or at a self-set limit, and excluded players never see them.

How does affiliate tracking work for a licensed sportsbook?

It ties each referred player to the affiliate that sent them, from the first click through registration, verification and first deposit, and calculates commission from the operator’s own records. In regulated states the affiliate itself is licensed or registered, and attribution has to respect app store privacy rules.

From click to first deposit

A tracking link carries a click ID to the landing page and through the app install; the ID is stored with the new account at registration and confirmed at identity verification and first deposit, the milestones a commission plan can pay on. Server-to-server postbacks report each milestone to the affiliate platform, so attribution does not depend on a browser cookie surviving an app install.

The affiliate needs its own approval

Michigan’s rules show the pattern. Its license classifications list affiliate marketers paid a share of customer revenue among the suppliers that must hold a sports betting supplier license (R 432.722(3)(f)), while affiliate marketers without a revenue-share agreement register as vendors instead (R 432.729(2)(a)). The platform records each affiliate’s deal type and whether its approval is current in each state.

Consent and App Tracking Transparency

On iOS, linking data from your app with data from other companies’ apps or websites for advertising measurement counts as tracking under Apple’s App Tracking Transparency rules and needs the user’s permission; Apple points advertisers to AdAttributionKit for privacy-preserving attribution. We design attribution with the operator’s privacy team: what is measured, which identifiers reach the affiliate platform, and when the permission prompt is required.

Commission reports that match the ledger

Revenue-share commissions are calculated from the operator’s own revenue, so affiliate reports come from the same ledger as the regulatory revenue report rather than a separate marketing database, and disputed conversions are traced through the click, account and deposit IDs. Our marketing analytics team builds the reporting layer.

Approved offers only

Affiliates publish the operator’s offers, so the affiliate portal serves approved creative and current terms straight from the promotions engine. New York’s rule against misleading embedded keywords aimed at minors, self-excluded players or problem gamblers names affiliate marketing partners alongside licensees and sports pool vendors (9 NYCRR 5329.37(b)(3)).

App store rules: Apple Guideline 5.3 and the Google Play real-money gambling policy

Both stores accept real-money betting apps, on conditions: the publisher is the licensed business, the app is free and geo-restricted, and money never moves through the store’s own billing.

Apple App Store Review Guideline 5.3

Guideline 5.3.4 requires real money gaming apps (sports betting, poker, casino games, horse racing) and lotteries to have the necessary licensing and permissions in the locations where the app is used, to be geo-restricted to those locations and to be free on the App Store, and it bars illegal gambling aids such as card counters. Guideline 5.3.3 rules out in-app purchase for real money gaming credit, and 5.1.1(ix) asks that gambling apps be submitted by the legal entity providing the service.

Google Play’s real-money gambling policy

Google Play requires the developer to complete its application process for gambling apps and to be an approved governmental operator or a registered, licensed operator; the app must block areas its license does not cover, prevent under-age use, be free to download, avoid Google Play In-app Billing and carry an Adults Only rating or the IARC equivalent. Daily fantasy sports apps qualify if they are distributed only in the United States, or if they meet the gambling-app requirements elsewhere.

Preparing for review

We prepare review notes that explain the license and the geo-restriction, test accounts that work from a permitted location, and the license documents a reviewer may ask for, so review questions can be answered the same day.

Testing to GLI-33 and state technical standards

Before launch, an independent lab tests the system against the standard each state adopts, often GLI-33 for event wagering or the state’s own technical rules. We build to the standard from the first sprint, so testing confirms the work instead of discovering it.

What GLI-33 covers

GLI-33, Standards for Event Wagering Systems, version 1.1 (revised May 14, 2019), covers system requirements such as clocks, control programs, wagering management, player account management, location requirements for remote wagering, record keeping and reporting; wagering devices, including remote devices such as phones; event wagering rules for displays, wager placement, results and payment; and operational audits of internal controls and technical security. GLI describes it as a compliance guideline rather than a prescriptive set every system must meet. Operators and suppliers supply documentation and a production-equivalent test environment, and GLI issues a certificate of compliance after testing.

State technical standards

States adopt standards in different ways. North Carolina’s Lottery Commission lists GLI-33 v1.1 among its technical manuals and bulletins, which have the same force and effect as its rules manual once adopted. Michigan publishes its own technical bulletins. The compliance map we write in discovery lists, for each target state, which standard applies and which state bulletins add to it.

Change management after launch

Launch is the start of the release cycle, not the end. GLI-33’s security appendix covers change management and periodic security testing, and Michigan has bulletins on software approval and modifications and on release notes. The delivery pipeline therefore produces versioned builds, release notes and approval records for every change a regulator may review.

How do you load-test a sportsbook for peak events?

By rehearsing the busiest moments before they arrive: kickoff surges, in-play bursts and settlement waves, run against a production-like environment and against every vendor in the wagering path. New York’s Comptroller notes that betting activity rises from October to March with the World Series, the Super Bowl and the NCAA’s March Madness tournament, so the test calendar follows the sports calendar.

What a peak looks like

In New York, bettors placed $2.5 billion in bets during the World Cup, June 11 to July 19, 2026, excluding NBA Finals week, and more than $1 billion in mobile sports bets in the first two weeks of June, according to the Comptroller’s September 2026 release. Totals like these are built from many small wagers, and each one needs a location check, a balance check and a price confirmation.

Test the vendors, not only your servers

Geolocation, identity, payment and odds providers all sit in the path of a wager, each with its own rate limits and failure modes. Load plans include agreed test windows with each vendor, or realistic stubs where a vendor cannot take test traffic, and measure what happens to wagering when one of them slows down.

Fail without losing a wager

GLI-33 section B.3.5 requires enough redundancy that a single failed component does not stop the system or lose critical data, and that linked components neither lose nor duplicate transactions when one restarts, resynchronizing immediately afterward. Failover drills run inside the load tests to prove it, on the cloud infrastructure the platform will actually use.

Performance monitoring is an obligation

GLI-33 section B.2.1 asks for procedures to monitor and adjust resource use, keep a performance log and compile performance reports, and to investigate malfunctions, including filing an incident report with the regulator and voiding or canceling wagers if a full recovery is not possible. Dashboards and alert thresholds are part of the certified operation, set before launch.

What reports does a sportsbook platform produce for regulators?

Revenue, liability, future-event and significant-event reports, on demand and for daily, month-to-date, year-to-date and life-to-date periods, plus whatever each state adds. GLI-33 section 2.9 lists the data they need, and each report must name the operator, the interval and when it was generated, and say “No Activity” when there is nothing to show.

Revenue by event and market

For each event and each market in it: start and end times, total wagers, winnings paid, wagers voided or canceled, commissions or fees, identifiers and status (GLI-33 2.9.2). These are the figures state tax returns are built from; New Jersey’s Division of Gaming Enforcement, for example, posts the monthly sports wagering tax returns online.

Liability and future events

Liability reports show money held for players, wagers on future events and winnings owed but unpaid (2.9.3). Future-events reports split the gaming day’s wagers by when they were placed and when the event occurs, and list the day’s voids and cancellations (2.9.4).

Significant events and alterations

Every significant event or alteration is reported with its time, the component, the user who made or authorized it, the reason and the values before and after (2.9.5). Section 2.8.8’s list of significant events runs from failed logins and program errors to result changes, promotion changes and large transactions.

How long records are kept

GLI-33 A.2.2 sets a default of five years for the information the system maintains, unless the regulator specifies otherwise, and A.4.4 keeps complaint correspondence for five years too. Section 2.8.1 also requires a way to export data for analysis and audit, such as CSV or XLS, so storage, backups and export formats are designed for that horizon.

Which taxes and tax forms does the platform have to calculate?

The federal excise tax on wagers, the federal occupational tax, Form W-2G reporting and withholding on large wins, and each state’s tax on gaming revenue. The operator’s tax team owns the filings; the platform has to produce exact numbers for each one. What follows summarizes the rules we build to and is not tax advice.

Federal excise tax on wagers

Under 26 U.S.C. 4401, a wager authorized under the law of the state where it is accepted is taxed at 0.25 percent of the amount wagered, against 2 percent for other wagers, and the person in the business of accepting wagers pays it. The tax runs on the amount wagered rather than on revenue, so the platform reports handle by period.

The occupational tax

Section 4411 adds a special tax of $500 a year on each person liable for the wagering tax or receiving wagers on its behalf, reduced to $50 where the only liability is for state-authorized wagers. It is a fixed yearly amount and needs no per-wager calculation.

Form W-2G and federal withholding

The IRS’s January 2026 instructions for Forms W-2G and 5754 call for a W-2G for gambling winnings that meet the reporting threshold, $2,000 for payments in 2026 and adjusted for inflation each year after 2025, when the winnings are at least 300 times the wager. Federal income tax is withheld at 24 percent when winnings minus the wager exceed $5,000 and the winnings are at least 300 times the wager. GLI-33 A.4.3 expects the operator to identify taxable wins and complete the paperwork before paying amounts above a jurisdiction’s limit.

State taxes on gaming revenue

States tax sports wagering revenue at their own rates and on their own schedules. New Jersey’s August 2026 release, for example, lists a 19.75 percent gross revenue tax on online sports wagering by casinos and racetracks and 8.5 percent on sportsbook lounges. The revenue report is built per state, with each state’s definition of taxable revenue, including its treatment of promotional credits, set in configuration rather than code.

Fantasy sports app development

Fantasy sports software development shares a lot with a sportsbook (accounts, payments, location and age checks) but the product logic is different: contests, drafts, scoring and prize distribution rather than prices and settlement.

Daily fantasy sports software development

Contest creation and entry management, salary-cap and pick’em drafting, live scoring from statistics feeds, late-swap rules, prize distribution and contest history. The scoring engine and the stats feed carry the same weight here that the odds feed carries in a sportsbook, and fantasy sports app development services are judged by whether scores update correctly on a busy Sunday.

State registration and taxes

Fantasy contests are regulated separately from sports betting in several states. New York requires interactive fantasy sports operators to register with its Gaming Commission and pay 15 percent of in-state gross revenue plus an additional 0.5 percent, capped at $50,000 a year. Pennsylvania’s Gaming Control Board regulates fantasy sport games, and Michigan’s Gaming Control Board runs internet gaming and fantasy contest licensing. The build follows each state’s contest rules.

Store and advertising rules for fantasy

Google Play accepts daily fantasy apps distributed only in the United States, and Meta’s advertising standards list fantasy sports among the online gambling and gaming categories that need authorization before ads can run. A fantasy product plans for both before launch day.

What a fantasy sports app development company should deliver

A contest engine that is auditable, identity and location checks where the state requires them, responsible-play limits, payment integrations, and an admin console that lets the operator create, pause and settle contests without a developer, whether the work comes from a fantasy sports software development company or an in-house team.

Cricket betting app development for US-licensed books

Cricket betting app development for the US market means adding cricket competitions and markets to a licensed sportsbook where a state has approved them, not building a cricket-only product outside the license.

Is there a cricket betting app for the USA?

Licensed US sportsbooks can offer cricket where the state approves it. Iowa’s list of approved sports wagers, updated September 10, 2026, includes first-tier ICC events, Test matches, One Day Internationals, Twenty20 internationals and the Twenty20 World Cup, the Indian Premier League, The Hundred, Major League Cricket and the Big Bash League. Each state keeps its own list, so the catalog is configured state by state.

What cricket adds to the build

Multi-day Test matches, rain interruptions and revised targets, abandoned or shortened games and over-by-over markets all need settlement rules. Iowa requires each operator’s house rules, including the definition of an official contest and the results source, to be approved, so cricket settlement logic is written from rules the regulator has seen.

What about India?

India’s Parliament passed the Promotion and Regulation of Online Gaming Bill on 21 August 2025. The government’s own summary says it bans online money games, whether based on chance, skill or both, prohibits their advertising and bars banks and payment systems from processing their transactions, while promoting e-sports and online social games. We do not build real-money betting or fantasy apps for the Indian market; our cricket betting app development company work is for states and countries where the operator is licensed.

Horse racing betting software development

Horse racing betting software development starts from a different model. The Interstate Horseracing Act of 1978 defines pari-mutuel wagering as a system in which wagers on a horserace go into a pool conducted by a person licensed or permitted under state law, and participants wager with each other, not against the operator; the same Act governs interstate wagers on races.

What pari-mutuel changes in the software

Odds are not set by a trader; they move with the pool until betting closes, and payouts are dividends calculated from the final pool. GLI-33 asks for up-to-date pool odds and total investments to be shown (section 4.2.2), for the published rules to state the dividend formula (A.5.2(m)), and for rules and expected payouts for exotic wagers such as the perfecta, trifecta and quinella (A.5.2(q)).

Interstate wagers need three consents

Under 15 U.S.C. 3004, an off-track betting system may accept an interstate off-track wager only with the consent of the host racing association, the host racing commission and the off-track racing commission, and the host association generally needs a written agreement with the horsemen’s group. The Act’s definitions include pari-mutuel wagers placed by telephone or other electronic media where lawful in each state involved (15 U.S.C. 3002).

Where racing sits under federal gambling law

The Unlawful Internet Gambling Enforcement Act excludes activity allowed under the Interstate Horseracing Act from its definition of unlawful internet gambling (31 U.S.C. 5362(10)(D)(i)). State law still decides who may take the wager and which regulator licenses them.

What the build includes

Integration with the pool operator’s totalizator for odds, pools and dividends; race cards, scratches and changes; exotic wager builders; official results and order of finish; and account wagering with the same identity, location, payment and responsible-gaming controls as a sportsbook.

Architecture, stack and integrations

When a sportsbook app is a front end on a licensed platform, architecture decisions are about integration quality, speed under load and auditability, not about reinventing the betting engine.

Native, React Native or Flutter

Native Swift and Kotlin give the most control over performance and device features; React Native and Flutter share code across platforms. The deciding question is often whether the geolocation and identity vendors’ SDKs support the framework you pick. Our iOS and Android teams work in both models.

Real-time prices and bet placement

Price updates stream over persistent connections, the bet slip holds the price it showed the player, and placement requests carry idempotency keys so a retry on a weak connection never places the same bet twice.

Data, logging and reporting

Append-only event logs, a reporting warehouse and scheduled regulator exports, with servers placed where each state’s rules on server and equipment location allow. Back-office dashboards sit on the same data model.

Security and operations

Infrastructure as code, secrets management, protection against denial-of-service attacks, disaster recovery drills and scheduled security testing, run by our DevOps and security teams.

How much does sports betting app development cost?

Our published planning ranges put a focused MVP at $40,000-$100,000, a full business app at $100,000-$250,000 and complex regulated products at $150,000-$400,000 or more; a single integration runs $15,000-$40,000. A quote follows a written scope.

The ranges come from our mobile app development, integration and app development cost pages. Cricket betting app development cost follows the same logic: adding cricket competitions and a cricket data feed to an existing sportsbook is scoped like an integration, while a cricket-first product is scoped like a full app. The number of states, platforms and integrations, custom trading tools and extra certification rounds push a quote up; building on a licensed platform and phasing the scope bring it down.

How long does a sportsbook build take?

A front end on a licensed platform is planned in months, a custom platform takes much longer, and lab testing and store review add their own time at the end. The sequence below is typical for a front end with integrations.

What you receive at handover

Everything needed to run, audit and change the product without us, delivered into accounts you already own.

• Source code in your repositories, with build and deployment scripts.
• Architecture and data-flow diagrams, including every third-party integration.
• The state compliance map, updated to what was actually built and tested.
• Runbooks for incidents, location-check failures and payment outages.
• Release notes and approval records for every version submitted.
• Test evidence prepared for the lab, and the lab’s findings with their fixes.

How should a sportsbook sequence a multi-state launch?

Launch first where the license path, platform approval and vendor registrations are clearest, start approvals for the next states in parallel, and keep one codebase with each state’s rules in configuration. Each new state then becomes a compliance and configuration project, not a new build.

Order states by the path to approval

The first state is usually the one where the operator’s license or market-access agreement, the platform supplier’s approval and the vendors’ registrations are already in place or closest. Market size matters, but a state that cannot approve you this year cannot earn anything this year.

One codebase, configured per state

Approved markets, stake caps, helpline wording, age reminders, promotion rules, tax definitions, location boundaries and server placement all differ by state. They live in a jurisdiction configuration that the app, wallet, promotions engine and reports all read, versioned and approved like code.

Approvals in parallel, launches staggered

Lab work, regulator review, vendor registrations and store updates for the next state begin while the current one stabilizes. Where the next state applies the same standard, much of the test evidence carries over and the state-specific additions are tested on top; the lab and the regulator decide how much.

Partners set dates as much as code does

Online sportsbooks often launch through a land-based licensee or a license category the state defines; New Jersey’s revenue releases, for example, report online sports wagering by casinos, racetracks and their partners. Launch dates depend on those agreements as much as on software.

After go-live in each state

Soft-launch with limited marketing, watch location-check pass rates, verification drop-off and payment success for that state, then open the promotions calendar. The runbook for the next state is updated with what the last one taught.

What happens after launch?

The product moves into a regulated release cycle with round-the-clock operations: complaints taken at any hour, incidents reported to the regulator, continuity plans rehearsed and every change approved before it ships. We can run that alongside the operator’s team or hand it over completely.

Complaints and disputes

Players must be able to log a complaint 24/7 and take it to the regulator if the operator cannot resolve it, and the operator keeps the correspondence for five years unless the regulator sets another period (GLI-33 A.4.4). The help center, complaint queue and regulator escalation path are product features with owners and service targets, often run from a custom CRM.

Incidents

GLI-33 section B.2.1 asks for procedures to monitor, investigate and resolve security incidents and malfunctions, including an incident report to the regulator with the date, time and reason for a malfunction and when the system was restored. The on-call rotation, paging rules and report template are agreed before launch.

Continuity and recovery

The business continuity and disaster recovery plan covers a recovery site physically separated from production, guides for re-establishing wagering there, and how data loss is minimized or documented if replication is asynchronous (GLI-33 B.3.9). We rehearse it on a schedule, not only after an outage.

Security testing on a schedule

GLI-33’s appendix section B.9 covers periodic technical security testing, vulnerability assessments, penetration testing, information security management system audits and cloud service audits. They go on the release calendar next to feature work, with findings tracked to closure.

Measuring the live product

Weekly reviews track the numbers that move revenue and compliance together: registration-to-verification conversion, location-check pass rate by state, deposit success by method, bet rejections by reason, settlement exceptions, cash-out use and complaint volume. Growth work on top of that sits with our app marketing team.

How do you choose a betting software development company?

Look for evidence that the team has built to regulated standards, can name the rules in your states, and hands everything over at the end. The same questions work for any sports betting software development company or betting app development company on your list.

Red flags to walk away from

Any of these ends the conversation, whoever is offering the build.

• An offer to publish the app under the developer’s own store account.
• A promise that the app can take bets without identity checks or location checks.
• A plan to launch in a state before the operator’s license or platform approval is in place.
• Deposits through Apple or Google in-app purchase.
• No answer when asked which technical standard the build targets.
• Code and infrastructure held in the developer’s accounts after handover.

AI answers: how operators and suppliers find a development partner

Operators, suppliers and founders now ask ChatGPT, Claude, Perplexity, Gemini and Copilot for shortlists of sportsbook developers, and the answers lean on pages that state capabilities, standards and limits in plain text.

How buyers phrase the question

“Which companies build sportsbook apps for US-licensed operators?”, “Who can integrate a geolocation SDK and identity checks into a fantasy app?”, “sports betting app development company that knows GLI-33”. Assistants draw on developer service pages, technical write-ups, directories and comparison articles, and they can only repeat what those pages actually say.

What buyers type into search

Classic search still carries measurable demand. Fantasy phrases lead: “fantasy sports app development company” draws about 260 US searches a month and “fantasy sports app development” about 140, where advertisers bid $14.57 a click, while “sports betting app development company” draws about 90 and “cricket betting app development” about 70 (Ubersuggest, September 2026). Smaller phrases such as “horse racing betting software development” and “sportsbook software development company” register about 40 each.

What gets a developer named and linked

Pages that name the standards (GLI-33, Guideline 5.3), the integrations and the states; technical articles that explain how a problem was solved; real, permitted case studies; and company facts that match across the web. Vague claims about being “compliant” give an assistant nothing to cite.

The same logic for the operator’s own app

Players ask assistants whether an app is legal in their state and how withdrawals work. An operator whose help center states its license, its checks and its processing times in text gives assistants an accurate answer to repeat. For AI Overviews, Google says a page needs to be indexed and eligible for a snippet; OpenAI’s OAI-SearchBot and PerplexityBot need to be allowed to crawl.

Related services

A sportsbook build touches most of our engineering practice, and the launch touches marketing.

• Mobile app development: our wider iOS, Android and cross-platform practice.
• Payments and fintech engineering: wallets, ledgers and payment integrations beyond gaming.
• Custom APIs and integrations: odds feeds, identity vendors, payments and partner connections.
• SEO for licensed casinos and sportsbooks: getting the finished app and site found.
• Sports marketing: tickets, sponsorship and fan growth for teams and venues.
• Stock trading app development: another regulated, real-time build.
• Cloud app development: the infrastructure a multi-state platform runs on.
• Backend development: services, queues and data models behind the app.
• React Native and Flutter builds for shared codebases.
• DevOps and security hardening for regulated releases.
• Back-office dashboards for trading, payments and responsible gaming.
• App development cost guide: the planning ranges behind the pricing table.

Frequently asked questions