Skip to content
Genesis Ark

06 / Client pricing and hedging

Available

Price every client on your terms, and hedge the flow automatically

Qubit's pricing engine builds client prices from the consolidated book, adds the spread, markup and skew you set for each client tier and instrument, and streams them over API or FIX. When a client trades, auto-hedging offsets the position on your venues, back to back or after internal netting.

Layer
Standalone · Add-on
Works on its own
In part
Interfaces
WebSocket, REST, FIX
Fig. 1. One source price streamed to three client tiers with different spreads. Illustrative composition with sample data.

01 / The problem

Your clients need a price you can honor

A broker's client sees one price and expects to trade on it. Behind that price sits the real cost of filling the trade on the market at that size, plus the margin the broker needs to earn. Most firms build this with a fixed markup on one venue's mid. It is too wide when markets are calm, too thin when they move, and leaves the desk holding whatever risk the clients created until someone hedges it by hand.

02 / What it does

What the module handles

  1. 01

    Executable source prices

    Client prices start from the price to fill the requested size on the consolidated book, not from a mid that cannot be traded at size.

  2. 02

    Spreads and markups per tier

    Set spread or markup in basis points or as a fixed amount, per client tier, instrument and size band.

  3. 03

    Size ladders

    Quote different prices for different sizes, so a large order is priced on the depth it will actually take.

  4. 04

    Inventory skew

    Shift the bid and offer when the desk's position builds up on one side, to attract offsetting flow.

  5. 05

    Local currency pricing

    Price in local currencies, such as INR, by combining a crypto pair with an FX rate you supply.

  6. 06

    Quote validity and throttling

    Each price carries a validity time, and stops streaming when the source market is stale or too volatile.

  7. 07

    Auto-hedging

    Offset client trades on your venues automatically, by trade, by net position threshold or within an inventory band.

  8. 08

    Hedge P&L

    See the spread earned on client trades against the cost of hedging them, per client tier and instrument.

Fig. 2. Each stage writes to the audit trail.

03 / How it works

From market price to hedged client trade

  1. 01

    Source

    The engine reads the consolidated book and computes the cost to fill each size band on each side.

  2. 02

    Price

    It applies the tier's spread, markup and size ladder, the inventory skew and any FX conversion, then streams the result.

  3. 03

    Trade

    A client accepts a price over API, FIX or your front end. Pre-trade risk checks the client's limits and the price's validity. The trade is booked to the client account and to the desk's position.

  4. 04

    Net

    Client trades in opposite directions offset internally, if internal netting is enabled.

  5. 05

    Hedge

    When the net position crosses its threshold, or immediately in back-to-back mode, Qubit sends a hedge order through the smart order router.

  6. 06

    Account

    Client trade, hedge fills and the spread earned are linked and reported.

04 / Specifics

Technical specifics

Price sources

Consolidated book VWAP to size, best bid and offer, mid or a composite reference price; per instrument, with venue selection.

Pricing parameters

Spread (bps or absolute), markup per side, minimum spread, size bands and their prices, skew per unit of inventory, maximum skew, quote validity time, maximum source staleness.

Client tiers

Each client account maps to a pricing tier. Tier overrides are possible per client and instrument.

Hedging modes

Back to back (hedge every client trade as it happens), threshold (hedge when the net position passes a limit), band (keep inventory inside a set range) and manual (flag for the desk to hedge).

Hedge execution

Through the smart order router or a chosen algorithm, with per-hedge limits and venue selection.

Distribution

WebSocket streaming, REST quote requests and FIX (QuoteRequest 35=R and Quote 35=S, or MarketDataSnapshotFullRefresh 35=W for streaming).

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Spread, markup and minimum spread per tier, instrument and size band
  • Size ladders and their prices
  • Skew per unit of inventory and maximum skew
  • Quote validity time and maximum source staleness
  • Client tier per account, with overrides per client and instrument
  • Hedging mode, thresholds, per-hedge limits and venues

Logged to the audit trail

  • price published · tier, parameters that produced it
  • client trade · account, price, validity check
  • internal netting of opposite client trades
  • hedge order sent · mode, size, route
  • price withdrawn · stale or volatile source
  • parameter change · old and new values, user

06 / Where it fits

Works on its own
The pricing engine works on its own with the market data module: it streams prices but does not book trades or hedge.
Needs the core
Auto-hedging needs the core platform and the pricing engine, because it acts on booked client trades and live positions.
Who uses it
Brokers and neobanks offering crypto to their clients, OTC desks quoting principal prices, exchanges running a broker or convert service, fintechs launching a white-label brokerage.

FAQ

Questions we get asked

  • Does Qubit set the spreads?

    No. You set every spread, markup and tier. Qubit applies them consistently and records which parameters produced each price.

  • Can we run as agent rather than principal?

    Yes. In back-to-back mode every client trade is hedged immediately and the desk does not hold inventory. In threshold and band modes, the desk takes principal risk within the limits you set. Which model is permitted for your firm is a regulatory question for you and your counsel.

  • How are INR prices built?

    From a liquid crypto pair, such as BTC-USDT, combined with a USDT-INR or USD-INR rate from the FX source you choose. The spread and markup are applied to the final local currency price.

  • What happens if the market data feed goes stale?

    Prices built on stale data stop streaming and pending quotes are withdrawn until the source recovers. Clients receive a clear "price unavailable" status rather than an outdated price.

Quote your clients with prices you can stand behind

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.