Aggregation

One layer in front of four floors

Virtual Circuit is a casino game aggregator. It is not a casino. Operators, platforms, and other aggregators connect once. Behind that connection sit four studio floors. In front of it sits the caller's own lobby and the caller's own wallet. Players never open an account on this site.

An aggregation layer exists so a platform does not keep a separate project for every studio. Catalog records, launch requests, session identifiers, and wallet calls share one shape. Market rules still differ. A floor can be allowed in one territory and dark in another. The layer records that split. It does not invent a second casino to hide it.

What the layer coordinates

Catalog data arrives from each floor's own source and is mapped into one record: title, art, stake bounds, and the return that belongs to a market. The operator's lobby asks for a record. The layer answers. It does not redraw the lobby, and it does not host a playable cabinet.

A launch request names the game, the market, and the player session that already exists on the operator side. The layer opens the session against the floor that owns the game. If that floor is not allowed in the market, the launch stops. There is no fallback game and no sample round.

Wallet traffic uses the callback contract. A stake, a result, a refusal, and a retry of the same round id all travel to the operator's URL. The layer does not hold the player balance. A refusal is a normal answer. A timeout is not treated as a win or a loss.

Content updates are new records and changed bounds, not a new integration. When a floor adds a title that can take a per-market return, the record appears in the catalog. A title that cannot take that return is not listed. The catalog stays short for that reason.

What the layer does not do

It does not register players. It does not pay players. It does not run promotions inside a lobby, because it does not own the lobby. It does not offer a public game to try. A test round is a wallet call on the operator's callback, fired by the desk after the URL and the currency list are in. It is not a demo on this website.

Commercial terms, certification, and which titles a territory will accept still sit with the project. Aggregation does not erase those differences. It keeps them on one market list instead of four unrelated projects.

From the first call to production

The desk opens on two details: the callback URL and the settlement currencies. Territories and allowed floors are the coverage map. Keys are issued when a test round on that URL returns a clean accept or a clean refusal, and the same round id does not debit twice. Production is a later switch. A $500 balance marks the project as allowed to take live stakes. Later bills spend that balance. None of those steps is a player-facing casino.

Platforms that already aggregate for others can sit in front of Virtual Circuit the same way an operator does. They keep their own clients. They receive one catalog and one callback shape. They do not receive a branded casino, and they do not send their clients to this domain to play.

Reporting stays at the project level. The layer can say which market, which floor, and which round id moved a stake. It cannot say who the player is, because it never received a player account. If the operator wants a player-level report, that report is built in the operator's own wallet, from the round ids the callback already returned.

A content update does not reopen the desk. New records appear for markets that already allow the floor. A market that excludes the floor does not suddenly include the new title. Changing that permission is a coverage change, written by the operator, not a side effect of a catalog refresh.

Authentication of the project is the key issued by the desk. Each call carries that key. A call with a retired key is refused before a wallet round starts. Rotating a key does not move balances, because the layer holds none. The operator updates the key on the platform side and the next launch uses it. Old round ids remain valid for retries that are still open. New rounds take the new key.

The layer's job ends at that boundary. It can prove which project asked for a game, which market allowed the floor, and which round id the wallet answered. It cannot prove a player's identity, and it does not try. That proof stays in the caller's own account system, next to the lobby the caller already runs.