Multi-casino support
Separate operator identity, credentials, limits, fees, compliance rules and financial reporting.
GAMING & REGULATED iGAMING
Separate the casino product from the payment infrastructure without hiding the use case.
Nexus can provide the account, funding, payout and ledger layer for approved gaming operators while the connected casino focuses on player experience and game operations.
CONNECTED CASINO
The casino does not need to become the card-integration layer.
A player can authenticate through a common account experience, open the Nexus payment window from the casino and complete approved funding or payout actions through Nexus and its external providers.
- Casino initiates Nexus funding or payout intent
- Nexus preserves the originating operator identity
- Provider-hosted payment experience handles credentials
- Nexus ledger confirms usable player value
- Gaming credit can remain an internal ledger allocation
RIFT / Casino APay with Nexus
↓Aurelian AccountFunding / payout interface
↓Approved providersCards · Bank · Stablecoins
↓Nexus ledgerPlayer value + operator attribution
TRANSPARENT TO PARTNERS
iGaming remains an approved downstream use case.
Technical separation does not change the duty to disclose relevant merchant activity to regulated partners. Nexus is designed to make the approved model auditable, not to disguise the economic purpose of a transaction.
Central player account
A user can hold value centrally and allocate it across approved services without external money movement for each internal action.
B2B fee model
Nexus fees can be charged to the responsible operator rather than reducing the end-user funding or approved payout amount.