At a glance
Retail betting software development at a glance
Capermint builds retail betting software for casino and racetrack sportsbooks, betting shop chains, kiosk networks and online operators adding a retail channel: SSBT kiosk software, cashier POS, odds screens, agent apps, shop back office and a wallet shared with online. Turnkey or white-label launches take 6–10 weeks and custom platforms 14–24 weeks; modules start at $10K, turnkey stacks at $35K.
| Item | Detail |
|---|---|
| Delivery models | Turnkey, white-label or custom retail stack, engaged as a fixed-scope project, a dedicated team (monthly) or co-development with your engineers |
| Timeline | Turnkey or white-label launch in 6–10 weeks; custom platform in 14–24 weeks; single modules and multi-market programs are scheduled at scoping. Hardware, module count and lab-testing scope move the date |
| Typical price (USD) | $10K–$40K for a single module; turnkey or white-label $35K–$120K; custom $60K–$180K; multi-vertical or multi-market omnichannel $200K–$500K+ |
| Core modules | SSBT kiosk software, cashier and over-the-counter POS, ticket printing and redemption, odds and TV screen CMS, agent POS app, shop and franchise back office, cash and float reconciliation, shared wallet, KYC/AML, reporting |
| Tech stack | Electron.js, C#/.NET (WPF) or Android AOSP kiosk mode on terminals; Kotlin or React Native agent apps; Node.js, Java or Go with WebSocket; PostgreSQL, Redis; AWS, GCP or Azure |
| Hardware | Windows and Android terminals; thermal ticket printers such as Epson, Star or BIXOLON; bill acceptors and dispensers such as JCM or CPI; EMV/NFC card readers; barcode/QR scanners; odds screens, mobile and web |
| Compliance and testing | Built to the technical rules of the target jurisdiction and documented for independent testing by accredited labs such as GLI, iTech Labs or BMM; the operator holds the license and obtains certification |
| Markets | United States and Canada, plus UK/EU, Latin America, Africa, Asia-Pacific and other regulated markets; free-to-play and social formats only for India |
| Studio | Founded 2014 in Ahmedabad, India; Capermint-reported 650+ customers worldwide and over 200 specialists; Clutch 4.9/5 from 13 reviews |
Venues
What each retail venue needs
Retail betting covers very different floors. Phase one is scoped around the venues you open first.
| Venue | Typical modules | What shapes the build |
|---|---|---|
| Casino or racetrack sportsbook | Cashier POS linked to cage cashiering, SSBTs, odds and TV screen CMS, large-payout workflow, back office | Where retail sportsbooks may operate is set by state or provincial rules; payouts follow the ID, tax and AML records your jurisdiction requires |
| Betting shop or shop chain | Cashier POS, SSBTs, odds screens, shift and float reconciliation, franchise back office | Role-based access per location and per-shop reporting for head office |
| Bar, lounge or stadium kiosks | SSBT software, remote fleet management, QR bet slips built on mobile, cash or card acceptance | Only where your license and the state or province allow kiosks in that venue type |
| Agent networks | Android agent POS app, mobile-money payments, commission reporting, offline queueing where the regulator allows it | Common in Africa and Latin America |
| Online sportsbook adding retail | Middleware to your sportsbook engine and PAM, shared wallet, QR bet-slip handoff, retail reporting | Retail and online bets settle in the same system |
Cost and timeline
Retail betting software cost and timeline
Typical USD ranges by scope. Terminal hardware, odds data, KYC and payment services, licenses, lab testing and hosting are extra.
| Tier | Scope | Typical price | Timeline |
|---|---|---|---|
| Single module or MVP | One component on your existing sportsbook or PAM: cashier POS, agent app, odds-screen system or SSBT front end, with one payment method and printer and scanner integration | $10K–$40K | Set at scoping; depends on the module and hardware |
| Turnkey or white-label retail stack | Pre-built SSBT, cashier, odds screens and shop back office, branded and configured for your market, odds feed and payment rails | $35K–$120K | 6–10 weeks to launch; heavier market customization adds time |
| Custom retail sportsbook platform | Operator-owned SSBT, cashier, back office, wallet, KYC/AML and reporting built to your spec and hardware, with full source code | $60K–$180K | 14–24 weeks |
| Multi-vertical or multi-market omnichannel platform | Retail and online on one wallet with sportsbook plus casino, virtual sports or other verticals, several brands or jurisdictions, franchise hierarchy, migration of a legacy terminal fleet | $200K–$500K+ | Phased rollout; longer than a single-vertical build, set at scoping |
Final quotes follow a scoping call that confirms your venues, terminal hardware, sportsbook platform and launch date; you get an itemized estimate before any commitment. For budgeting, read how to start a sportsbook and compare white label vs turnkey vs custom models.
Running online betting as well? See sportsbook software development, horse racing betting app development and iGaming platform development, or hire sportsbook API integration engineers to extend your own team.
Delivery
How we deliver a retail betting build
Brief, NDA and scoping
Confirm venues (casino or racetrack sportsbook, shops, bar or stadium kiosks, agents), target jurisdictions and license status, sportsbook engine or PAM, odds feed, terminal hardware and opening date.
Itemized estimate and delivery model
Map scope to turnkey, white-label or custom, set team shape and milestones, and return an itemized estimate and timeline before any commitment.
Architecture, hardware and compliance mapping
Fix terminal targets and peripherals, cash and payment flows, ticket states and API contracts, and map each jurisdiction rule (limits, ID checks, audit logs, reporting) to a system control. UX wireframes for kiosk, cashier and back office.
Core engineering in parallel workstreams
Build SSBT software, cashier POS, back office, wallet, odds-screen CMS and integrations in milestone-gated sprints, with demos on your target hardware.
Peak-load, failover and security testing
Load-test above expected event-day peaks, test network loss and printer or cash-device faults, run security testing and prepare documentation for independent lab testing.
Pilot venues and launch
Go live in a controlled group of venues, monitor terminals and cash reconciliation, train staff, then roll out to the wider network with over-the-air updates.
Handover and support
Hand over source code and documentation on custom builds, then continue with SLA support or a dedicated team for new markets and modules.
Markets and compliance
Markets and compliance for retail betting software
We schedule calls in US and Canadian business hours and build for operators in the UK and Europe, Latin America, Africa, Asia-Pacific and other regulated markets.
United States. Since the Supreme Court struck down PASPA in 2018, most states have legalized sports betting through state licensing. Each state decides where retail sportsbooks may operate (for example casinos, racetracks or other licensed venues) and sets rules for identity checks, payouts, responsible gaming and data. Technology suppliers may also need a state license or approval, and some regulators reference GLI-33, the GLI standard for event wagering systems, in their technical requirements.
Canada. Provinces have been able to offer single-event sports betting since August 2021. Ontario runs a regulated open iGaming market for online play (AGCO/iGaming Ontario); retail betting runs mainly through provincial lottery corporations and the casinos they authorize, and suppliers may need provincial registration, so the route differs by province.
UK, EU, Latin America, Africa and Asia-Pacific. We build to the technical requirements of the target license, such as UKGC rules in Great Britain, MGA rules in Malta or a South African provincial gambling board; licensing bodies elsewhere differ by country and sometimes by province or state. In India, the Promotion and Regulation of Online Gaming Act 2025 prohibits online money games, so for India we build free-to-play, social and e-sports formats.
Brazil: Provisional Measure 1.394/2026 prohibited fixed-odds betting, including sports betting and online games, across Brazil from 25 September 2026. Whether that stands depends on the Supreme Federal Court (STF), where the measure is being challenged, and on Congress, which must vote on it. General information, not legal advice.
Operators are responsible for licensing; we build to the technical requirements of the target jurisdiction and prepare the software for independent testing by accredited labs such as GLI, iTech Labs or BMM. This is not legal advice.
Proof
Who builds your retail betting software
Game and iGaming studio
Capermint Technologies was founded in 2014 in Ahmedabad, India, where its delivery studio is based. Capermint-reported: 650+ customers worldwide and over 200 specialists across game design, engineering, backend and QA.
4.9/5 from 13 reviews
Independent Clutch rating.
iGaming work you can review
Browse the iGaming portfolio, and see selected clients and products on our clients page.
FAQ
Retail betting software FAQs
How much does retail betting software cost?
Typical ranges run from $10K–$40K for a single module such as a cashier POS or agent app, $35K–$120K for a turnkey or white-label retail stack, $60K–$180K for a custom retail sportsbook platform and $200K–$500K+ for a multi-vertical or multi-market omnichannel platform. The main cost drivers are terminal hardware models, cash-handling and payment flows, target jurisdictions and integrations with your sportsbook, PAM and odds feed. Hardware, odds data, KYC services, lab testing and license fees are paid separately, and final quotes follow a scoping call.
Which modules does a retail sportsbook need at launch?
Most retail sportsbooks launch with SSBT kiosk software, a cashier POS for over-the-counter bets and payouts, ticket printing and redemption, odds screens and a back office for shifts, cash and reporting. Agent apps, a franchise portal, promotions and a wallet shared with online can follow in later phases. We size phase one around your venues and opening date so you do not pay for modules you will not use yet.
Can you add a retail channel to our existing online sportsbook or PAM?
Yes. We connect kiosks, cashier screens and odds displays to your existing sportsbook engine, odds feed and player account management through their APIs, so retail bets settle in the same system as online bets. Where a provider has no retail endpoints, we build a middleware layer for ticket states, cash transactions and shop reporting, and we confirm API access with the provider during scoping.
Can bettors build a bet slip on their phone and pay at a kiosk or cashier?
Yes. The bettor builds a slip in your app or on mobile web, gets a QR or barcode, and scans it at a terminal or the counter to pay and print the ticket. The same code lets them check a ticket and redeem winnings later. This shortens queues at busy windows such as NFL Sundays or a Saturday football kickoff.
How are betting terminals managed across many venues?
From one back office. Operators see each terminal's status, cash levels, printer paper and software version, push over-the-air updates in waves, change odds-screen content centrally, and lock or restart a unit remotely. Role-based access lets venue managers see only their own locations while head office sees the whole network.
How does the software handle cash, float and large payouts?
Every cashier shift and terminal has its own float ledger, so cash in, cash out, voids and payouts reconcile at shift close and variances are flagged for review. Payouts above limits you set can require supervisor approval, ID capture and the tax or AML records your jurisdiction requires. Bill acceptors, dispensers and ticket redemption all post to the same ledger.
How do you prepare kiosks for Super Bowl, March Madness or World Cup peaks?
We load-test above expected peak before launch and design terminals to keep working when parts of the network do not. Odds updates are pushed rather than polled, each terminal fails in isolation instead of taking the network down, and short outages are handled under the rules your regulator allows. A runbook covers market suspension, feed failover and printer or cash-device faults on event days.
Who is responsible for licensing and lab certification?
The operator. You hold the gaming license and apply for approvals, and in many US states and Canadian provinces technology suppliers may also need their own license or registration. We build the software to the technical rules of the target jurisdiction and prepare it, with documentation, for independent testing by accredited labs such as GLI, iTech Labs or BMM, for example against GLI-33 where your regulator applies it. The operator or game owner obtains the certification.
Can you build retail betting software for Canada?
Yes, built around the provincial model. Provinces have been able to offer single-event sports betting since August 2021. Ontario runs a regulated open iGaming market for online play, overseen by AGCO and iGaming Ontario, while retail betting runs mainly through provincial lottery corporations and the casinos they authorize, so approval routes for operators and suppliers differ by province. We build to the technical requirements of the province you target, including French-language interfaces where needed.
Do we own the source code of a retail betting build?
On custom builds, yes: full source code and IP transfer to you at the final milestone, with documentation and knowledge transfer. Turnkey and white-label launches use a pre-built core, and source-code ownership is an option on white-label that is agreed in the contract. Third-party components such as odds feeds, KYC services and device drivers stay under their own licenses, and we list each one in the proposal.
Scope your retail betting build
Share your venues, terminal hardware, sportsbook platform and launch date; we schedule calls in US and Canadian business hours and return an itemized scope, timeline and estimate.