Predictu
Platform Overview

Platform Architecture

Predictu is designed as a modular, multi-tenant platform where each casino operator gets a fully isolated integration backed by shared infrastructure. This page provides a high-level overview of how the system components work together — from the player-facing trading experience to the backend engines that power pricing, risk, and settlement.

How It Fits Together

The architecture follows a straightforward pattern that casino operators will recognize from sportsbook and game provider integrations:

1
Your casino site embeds the Predictu trading widget into your existing front-end. Players interact with prediction markets without ever leaving your site.
2
The trading widget communicates with your casino shell through a lightweight, event-driven messaging bridge. Your site tells the widget who the player is and what their balance is. The widget sends back trade notifications and balance updates.
3
Behind the widget, the Predictu backend handles everything — sourcing live markets, calculating spread-adjusted prices, enforcing risk limits, executing trades, and settling resolved markets.
4
For every balance-affecting event, Predictu sends a secure, signed server-to-server callback to your backend. Your wallet system processes the debit or credit and confirms the transaction. This ensures you maintain full control over player funds at all times.

Multi-Tenancy and Operator Isolation

Every operator on the Predictu platform is completely isolated from every other operator. This is enforced at the database level — not just in application logic. When you integrate with Predictu, your players, trades, positions, revenue, and configuration are invisible to all other operators on the platform.

This isolation means:

  • Your data is yours. No other operator can ever see your players, their trading activity, or your revenue figures.
  • Your configuration is independent. Your branding, risk settings, market preferences, and wallet integration are entirely separate from other operators.
  • Your risk is contained. Exposure limits and circuit breakers are scoped to your integration. Another operator's activity cannot affect your risk profile.
Isolation by design, not by accident. Operator isolation is enforced through database-level security policies. Even in the unlikely event of an application bug, the database itself prevents cross-operator data leakage.

Platform Components

The Trading Widget

The player-facing trading experience is delivered as an embeddable widget that renders inside your casino site. It includes a complete prediction market interface: market discovery and browsing, detailed event pages with live pricing, a trading ticket for placing trades, portfolio and position tracking, and a watchlist.

When embedded in your site, the widget automatically adapts to your brand by loading your configured colors, logos, and styling. Navigation elements that would be redundant within your casino shell are hidden, so the widget feels like a native section of your site rather than a third-party embed.

The Communication Bridge

The widget communicates with your casino site through a structured, event-driven messaging protocol. This bridge serves two purposes: your site authenticates the player and provides their balance to the widget, and the widget sends real-time notifications back to your site when trades execute, balances change, or the player navigates within the trading experience.

For security, the bridge validates the origin of every message against your registered domain whitelist. Messages from unrecognized origins are silently ignored.

Server-to-Server Wallet Callbacks

Every operation that affects a player's balance triggers a cryptographically signed callback from the Predictu backend to your server. This covers the full trading lifecycle — bet placement, payouts, sell proceeds, refunds, and balance checks. Each callback includes a unique identifier for idempotency, ensuring safe retry behavior if a delivery fails.

This architecture means Predictu never holds player funds. Your existing wallet infrastructure remains the single source of truth for all player balances. Predictu simply tells your system what happened, and your system decides how to process it.

The Trading Engine

The trading engine is the core of the platform. It handles the full lifecycle of every prediction market trade:

  • Market sourcing — live prediction markets are sourced from leading market data providers, filtered for quality and tradeability, and made available to your players.
  • Pricing — dynamic spread-based pricing ensures a house edge on every trade. Spreads adjust automatically based on market conditions, providing sustainable margins without manual tuning.
  • Risk assessment — before every trade is executed, it passes through multiple layers of risk controls that check trade limits, market exposure, category concentration, global exposure, and system-level circuit breakers.
  • Execution — trades are executed atomically. If any step fails — pricing, wallet callback, position update — the entire operation rolls back cleanly, ensuring data consistency.
  • Settlement — when a market resolves, the system automatically identifies all affected positions, calculates payouts, credits winners through your wallet callbacks, and records a complete audit trail.

Player Intelligence

The platform continuously analyzes player behavior to identify betting patterns and classify players by sophistication. This classification drives automated risk adjustments — players identified as highly skilled may receive tighter limits and wider spreads, protecting your margins without requiring manual intervention.

Importantly, this classification is entirely invisible to players. There are no notifications, no visible restrictions, and no indication that anything has changed. The experience remains seamless while your exposure to sharp action is quietly managed.

The Operator Dashboard

Your self-service command center for managing every aspect of your integration. From the dashboard, you can:

  • Customize your brand with a visual editor and live preview
  • Configure your wallet integration and test callbacks
  • Monitor revenue, player activity, and trading volume
  • Review risk events and exposure levels
  • Manage market availability and per-market settings
  • View invoicing summaries and settlement reports

How Data Flows

Understanding the data flow helps clarify the responsibilities of each system:

1
Player opens your casino site. Your front-end loads the Predictu widget and sends the player's identity and current balance through the communication bridge.
2
Player browses and selects a market. The widget displays live prediction markets with real-time pricing. The player picks an event and selects an outcome to trade.
3
Player places a trade. The trading engine validates the trade against all risk controls, calculates the spread-adjusted price, and sends a callback to your backend to debit the player's balance.
4
Your backend processes the debit. Your wallet system verifies the player has sufficient funds, processes the debit, and confirms the transaction back to Predictu.
5
Trade is confirmed. The widget updates to show the new position, sends a trade notification through the communication bridge to your site, and the player's portfolio reflects the trade immediately.
6
Market resolves. When the event outcome is determined, the settlement engine automatically processes all positions. Winners receive payouts via callbacks to your backend. The full settlement is recorded for audit and reconciliation.

Security

Security is layered across every part of the platform:

  • Operator isolation — database-level policies ensure complete data separation between operators.
  • Origin validation — the communication bridge only accepts messages from your registered domains.
  • Signed callbacks — every server-to-server callback is cryptographically signed, allowing your backend to verify authenticity and detect tampering.
  • Idempotent operations — every callback includes a unique identifier so your system can safely handle retries without processing the same operation twice.
  • Encrypted credentials — all sensitive integration credentials are encrypted at rest.
Your backend validates every callback. While Predictu signs every callback for authenticity, we recommend that operators always verify the signature on their end before processing any balance-affecting operation. Our documentation and reference implementation show you exactly how.