By VeliTech

VeliHorizon

The VeliTech core system for player accounts, wallets and operational administration.

The offering

What VeliHorizon does

VeliHorizon brings account administration, balances and operational history into the core platform. Its documented architecture exposes interfaces that allow other services to consume data or extend the system.

Assess the ledger and the account model before comparing dashboard features. Follow a multi-currency deposit, promotion and withdrawal, checking the audit record at each step. Request the treatment of delayed events and account restrictions, and establish which extensions your own engineers may maintain. A migration plan should explain how old balances and histories can be reconciled after launch.

Who should explore it?

Operators choosing the central account layer for casino or betting.

  • Manage player accounts
  • Coordinate wallet and promotional balances

Documented capabilities

  • Player records
  • Multiple wallets
  • Operational history
  • Extension interfaces

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Product role
Core iGaming and player account system.Source
Wallet scope
Multiple wallets per player and multiple currencies.Source
Extension interfaces
REST APIs and Kafka events are described.Source
Account operations
Gameplay history, risk controls and transaction support.Source

Delivery & commercial details

Delivery & integration
API-driven core platform with modular services.Source
Pricing
Request a proposal covering setup, recurring charges, minimum commitments and optional services.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Can a player have more than one wallet?

Yes. Multiple wallets per player are included in the product description.

Source
Can operators extend the platform?

The technical section describes custom services consuming its interfaces and events.

Source