Tap Markets — External Wallet Integration

Full integration reference for the Tap Markets product, hosted iFrame model.

In this setup Tradesmarter provides the iFrame URL (e.g. https://s11.taptrading.com for staging, production URL provided separately). You embed it from any of your parent domains. Your side hosts the wallet API; TS calls into it for every gameplay event.

Roles

• External Wallet Provider (you) — host the user identity and the wallet. Expose 4 HTTPS endpoints TS calls into. Hold the funds; reserve on open, release on close.
• Tradesmarter (TS) — host the Tap Markets iFrame at the URL TS provisions for you. Call your wallet API for /authenticate, /getbalance, /opentrade, /closetrade. Run the matching engine and settlement.

TS never sees or touches your users' money. The wallet is yours; TS is stateless from a funds perspective and relies on you as the system of record.

How Tap Markets works (game model)

Tap is a short-form prediction game. The player sees a price chart with a grid of cells overlaid on top. Each cell represents:

• A time window (tStart → tEnd, typically 2 / 4 / 8 seconds wide depending on the size the player picked).
• A price band (pMin → pMax, the height of the cell — set adaptively by TS's engine).
• A payout multiplier displayed on the cell at the moment the player taps.

The player taps a cell to commit a stake. If the live price touches that cell's price band during its time window, the player wins; otherwise they lose. Winning closes the trade ~80 ms after the touch event.

This makes Tap a high-frequency settlement workload — much more bursty on /closetrade than Options games. Dimension your wallet API accordingly.

High-level architecture

The iFrame is third-party to your parent page in this setup. The launch flow bootstraps the session via a one-time URL token (no cookies needed for session continuity in the iFrame itself — see "Session inside the iFrame" below).