Skip to content

iGaming · VCM

VCM for an iGaming site — batch rate ops, and a bid that flexes by currency and conditions.

Under NDA we extended the operator's currency manager: batch updates to FX, and a bid built per currency and condition — deposit, withdrawal, method, VIP — so the rate on the site is a rule, not a midnight paste.

iGaming operator · NDA NDA 2025 5 min read
iGaming operator · NDA case study
rate ops
Batch
bid
Variable
client
NDA

One mid for every corridor was a lie

The site showed a single mid. Deposits, withdrawals, crypto ramps and fiat rails do not share a spread. Finance pasted CSV at night. We made VCM the source of the published book.

Batch operations

Ops select a set of pairs, a book date, a source. Preview the delta. Apply. Roll back. No row-by-row clicking through 40 currencies when a feed moves.

  • Batch import and apply with a dry-run
  • Locks so two people cannot publish the same book
  • History: who published which bid, and from which feed

Bid by currency and conditions

The bid is not mid plus a constant. It is a function of the pair, the rail, the direction, the VIP tier, sometimes the amount band. EUR deposit is not USDT withdrawal. The cashier gets the bid the rule produced, not a guess.

NDA note

Brand names, pairs and spread figures are not disclosed. Engagement scope: VCM batch operations and condition-based bid on an iGaming site.

Technologies

  • TypeScript
  • Postgres
  • Redis
  • Go

Outcomes

  • Rates update in batches, with preview and rollback
  • Bid is composed per currency and condition, not one global mid
  • Cashiers and lobby read the same published book
All cases