Overview
Integrate Phoenix Prediction into an operator product
Developer docs are for the team connecting Phoenix Prediction to an operator product.
The supported player integration is the hosted iframe. Your site owns identity, cashier, wallet ledger, page placement, and launch-token minting. Phoenix owns the prediction UI inside the frame.
Recommended Path
1. Integration checklist
Collect environment details, confirm the wallet contract, and validate the sandbox launch.
2. Sandbox and production
Understand how keys, origins, profiles, discovery configuration, and wallet settings are separated by environment.
3. Request signing
Sign backend-to-Phoenix requests with the operator Ed25519 key.
4. Launch tokens
Mint visitor and player JWTs with the correct operator and environment claims.
5. Wallet integration
Implement reserve, release, capture, credit, balance, and transaction status operations.
6. Iframe integration
Embed the hosted player experience and connect parent-page events.
What Your Product Owns
| Area | Operator responsibility |
|---|---|
| Player account | Login, registration, KYC, profile, account settings |
| Cashier | Deposits, withdrawals, wallet history, balance display |
| Token minting | Server-side Ed25519 signing for visitor and player launches |
| Parent page | Iframe placement, parent navigation, analytics, layout |
| Wallet ledger | Financial source of truth when funds move through your wallet |
What Phoenix Provides
| Area | Phoenix responsibility |
|---|---|
| Hosted iframe | Listing feed, market detail, order ticket, portfolio, comments |
| Operator environments | Sandbox/production separation, profile loading, environment-scoped config |
| Trading system | Binary market order entry, order state, positions, settlement state |
| Admin tools | Iframe profile configuration, listing and market operation, resolution workflows |
| Wallet operations | Signed reserve, release, capture, credit, balance, and transaction status calls |