Skip to main content

Delivery Options

Prediction Markets is available through three delivery paths. Standalone integration connects your platform to our APIs, and you embed the widget yourself. Bundled integration is available to operators already running SOFTSWISS Sportsbook. Aggregator integration is for a game aggregator that adds Prediction Markets to its catalog for the casinos on its platform.

What is SOFTSWISS Sportsbook?​

SOFTSWISS Sportsbook is a white-label sports betting platform that handles wallet infrastructure, session management, and widget embedding on behalf of operators. If you are already live on SOFTSWISS Sportsbook, the bundled path lets you enable Prediction Markets as a feature rather than a full integration.

If you are not on SOFTSWISS Sportsbook, the standalone path is the appropriate choice.

Comparison​

CriterionStandaloneBundledAggregator
Who integratesThe operatorThe operator, through SportsbookThe game aggregator, one time for every casino on its platform
Integration effortFull (3 wallet endpoints + HMAC + auth + widget)None (inherited from Sportsbook)Full (4 wallet endpoints + HMAC + launch call)
Wallet endpointsOperator implements deposit, withdraw, and rollbackHandled by the Sportsbook integrationAggregator implements balance, bet/win, finish, and rollback
AuthenticationOperator implements session flow and JWTInherited from Sportsbook sessionNo session endpoints — the launch call carries the player identity
Widget embeddingOperator embeds iFrameAlready embedded via SportsbookAggregator opens the launch URL that the platform returns
Who owns whatOperator owns all integration touchpointsSportsbook handles infrastructure; operator manages contentAggregator owns the wallet and the launch; each casino selects the game from the catalog
Time to go-liveDays, depending on wallet implementationHours — enable the feature, verify, go liveDays, depending on wallet implementation

Standalone​

The standalone path gives operators full control over the integration. You implement three wallet endpoints (deposit, withdraw, rollback) on your backend, configure HMAC-SHA256 signing for security, complete the authentication session flow so the widget can obtain a platform JWT, and embed the iFrame in your frontend.

This path is appropriate for operators who are not on SOFTSWISS Sportsbook and want direct integration with their own wallet and session infrastructure. The platform is designed to minimize surface area — three endpoints is all that stands between your wallet and live Prediction Markets.

The widget is fully customizable to match your platform branding — colors, typography, layout, and theme are configured during onboarding. Bettors see a native experience.

The tradeoff is implementation time. How long it takes depends primarily on the complexity of your wallet backend and how quickly you can expose and test the three endpoints.

Bundled​

The bundled path is available to operators already running SOFTSWISS Sportsbook. Wallet endpoints, authentication, and widget embedding are handled at the Sportsbook layer. From the operator's perspective, enabling Prediction Markets is a configuration step rather than an engineering project.

This path eliminates integration work but requires SOFTSWISS Sportsbook as a prerequisite. Operators on this path do not implement wallet endpoints or session flows directly — that infrastructure is already in place.

The tradeoff is dependency on the Sportsbook platform. Operators who want to integrate Prediction Markets independently of SOFTSWISS Sportsbook should use the standalone path.

Aggregator​

The aggregator path is for a game aggregator, and not for a single operator. Prediction Markets is one game in your catalog. Each casino on your platform selects the game, and your platform starts it for the player.

You integrate one time. You expose four wallet endpoints and sign each request. You then call the Launcher to start a session. Prediction Markets calls your wallet to debit each bet and to credit each win. Your casinos need no integration work.

This path has no session endpoint and no authentication endpoint. The launch call contains the player identity and the currency, so the player needs no second sign-in.

One difference from a casino game needs work in your wallet. A game round here is one bet on one market, and it stays open until the market resolves. That can take months, so your wallet holds many open rounds for one player and credits a win long after the player left the game.

The tradeoff is that your wallet becomes the single point of integration for every casino on your platform. A bet from any casino goes through the same four endpoints. Those endpoints must be idempotent, and they must report each business rejection with the correct code.


Ready to proceed? Choose your path:

For a non-technical summary, see the Integration Overview.