Compare
The iframe includes the betslip. The feed does not.
Casino operators usually want the sportsbook iframe because the betslip, the cash-out control and the bet history inside it are already built. A native betslip is a product build, not a skin.
Iframe book
Supplier UI, supplier trading, your wallet and your player session.
Own betslip
Your UI and your acceptance. You consume fixtures, prices and results.
A skin on the iframe is not a native betslip
Theming the hosted sportsbook changes colour and logo. It does not move bet acceptance into your codebase. If you need a betslip that matches a native app control by control, you are on the feed path described under sports data, and you should budget a trading operation.
Wallet behaviour still has to be right on the iframe path. A bet is a reservation until it settles or cashes out. That is less strange than a lay liability and more strange than a slot spin.
Theming the frame does not move acceptance into your code
Colour, logo and a host name on the iframe are still the supplier's betslip. Cash-out, bet history and the accept or reject decision stay in that product. If a native app needs every control to be yours, you are building a betslip on a feed, and you need traders, a suspension rule and a settlement engine. Budget that as a product, not as a skinning task.
The wallet path is shared in one important way: a bet reserves funds until it settles, voids or cashes out. That reservation is stranger than a slot debit and simpler than a lay liability. Test it on the iframe before you promise a later native slip. A second ledger 'for sport' is the mistake the later project then has to unwind.
What each route actually includes
| Iframe sportsbook | Your own betslip | |
|---|---|---|
| Betslip UI | Supplied and updated by them | Built and maintained by you |
| Accept or reject | Their trading rules | Your rules, on their prices |
| Cash-out | Their control, if the product has one | Yours, if you implement one |
| What you still build | Wallet reservation, session, and the launch | All of that, plus the slip and settlement |
| A theme change | Colour and logo | Not a shortcut to their acceptance logic |
Keep one wallet contract if you might rebuild the slip
Operators often start in the iframe and replace the client later. That second project stays a client and a trading change only if the reservation, the cash-out credit and the void already post the same way. A sport-only balance makes the rebuild a ledger migration.
Which route matches the sports product you are building
The frame is a launch decision and the betslip is a product decision. Teams that treat them as one choice usually buy twice.
| Situation | Iframe book | Own betslip | Decide with |
|---|---|---|---|
| Casino brand adding sport before a season starts | Fits | A project that misses the season | The launch date against a build estimate |
| Book with two traders and an app team | Possible for extra markets | Fits | Which product accepts the bet on each competition |
| Group wanting one visual language across casino and sport | Theme the frame, accept the difference | Fits eventually | How much of the slip is brand and how much is logic |
| Operator needing cash-out on day one | Check the product includes it | Build it, and price the work | Whether cash-out is named in that contract |
| Small team with no risk function | Fits | Not yet | Who pulls a price when a goal lands |
Two exits, and only one of them is cheap
The iframe exit is a data question. Before the contract, ask what happens to open bets at termination, whether bet history is exportable and in what format, and whether settled bets stay visible to the player afterwards. A frame that shows history only while the contract runs leaves your support team explaining bets the platform can no longer display.
The own-betslip exit is a staffing question. A feed without traders produces a coupon that accepts a price nobody would have offered, and those losses surface over a weekend rather than in a launch review. If the plan is to start on the frame and rebuild later, keep the wallet contract stable so the rebuild is a client change rather than a second ledger.
FAQ
Questions operators ask
Can we start with the iframe and rebuild the betslip later?
Yes. Many do. Keep the wallet contract stable so the second project is a client and a trading change, not a second ledger.
Does a deep link into the iframe bypass our stake limits?
It must not. Enforce the limit in the wallet when the bet is reserved. Hiding the sports tile on the homepage does not stop a bookmark that opens the frame.
Is cash-out in the iframe the same as a casino rollback?
No. A cash-out, once accepted, settles the bet at the offered price. A rollback returns a stake because the round failed. Store them under different codes so history does not call a paid cash-out a refund.
Can we start on the iframe and keep our own stake limits?
The limit has to be enforced where the bet is reserved, which is your wallet. A setting inside the frame is a courtesy rather than a control, and a deep link bypasses anything the homepage hides. Test a limit through a bookmark, not through the menu.
How long does an own betslip take compared with the iframe?
Longer than a theme and shorter than a book, and it depends on who prices the markets. The engineering is a slip, a settlement path and a history screen. The part that usually slips is the trading decision behind each acceptance, so scope that before comparing the two routes on development time.
Keep reading
Related pages
- Product · SportsbookSportsbookAdd pre-match, in-play, esports and virtual sport as a wallet iframe, or take the odds feed and build a betslip your traders run.Read
- Product · Sports dataSports dataFixtures, pre-match and live odds, scores and results for operators who build their own sportsbook front end and settle bets themselves.Read
- CompareHosted book vs feedA hosted sportsbook draws the coupon and settles the bets. An odds feed only hands you fixtures and prices to work with.Read
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.