Skip to content
Genesis Ark

05 / RFQ and OTC

Available

Request quotes from every dealer at once and keep the evidence

Qubit's RFQ hub sends one request to the liquidity providers you choose, shows their quotes side by side against the consolidated lit market and executes against the one you pick. Every quote, including the ones you did not take, is stored for best-execution review.

Layer
Add-on
Works on its own
No
Interfaces
FIX, provider REST and WebSocket
Fig. 1. Quotes from several providers ranked against the lit-market cost of the same size. Illustrative composition with sample data.

01 / The problem

Block trades still run on chat windows

Many crypto block trades are still negotiated in chat: a trader asks three dealers for a price, copies the replies into a spreadsheet and hits one before it expires. Quotes that were not taken are lost, so nobody can later show that the trade was done at the best price available. Booking and settlement happen afterward, by hand.

02 / What it does

What the RFQ hub handles

  1. 01

    One request, many dealers

    Send a request for quote to a chosen set of liquidity providers in one action, one-way (buy or sell) or two-way.

  2. 02

    Side-by-side quotes

    Quotes arrive in one panel with price, size, time remaining and the difference to the lit-market price for the same size.

  3. 03

    Lit-market reference

    Every quote is compared with the cost of filling the same size on the consolidated order book, after fees, so you know when the screen is cheaper.

  4. 04

    Streaming quotes

    For providers that stream, keep a live executable price instead of a one-time quote.

  5. 05

    One-click execution

    Accept a quote and Qubit sends the acceptance, records the trade, books the position and creates the settlement obligation.

  6. 06

    Complete quote history

    Every request, quote, expiry, rejection and acceptance is stored with timestamps, for best execution and audit.

  7. 07

    Desk as dealer

    OTC desks can also answer client RFQs with prices from the client pricing engine, and hedge the result automatically.

03 / How it works

An RFQ from request to settlement

Fig. 2. The stages below, in order. Each one writes to the audit trail.
  1. 01

    Request

    The trader enters instrument, side or two-way, quantity in base or quote currency and the providers to ask.

  2. 02

    Quote

    Providers respond with firm or indicative prices and a validity window. Qubit shows them ranked, with the lit-market comparison.

  3. 03

    Decide

    The trader accepts a quote before it expires, or lets the request lapse. Pre-trade risk checks credit and limits against the counterparty before the acceptance is sent.

  4. 04

    Book

    The accepted trade becomes a filled order in the OMS and a position in the ledger.

  5. 05

    Settle

    Post-trade records the settlement obligation with the counterparty, nets it with other trades if agreed, and tracks it until both legs settle.

04 / Specifics

Technical specifics

Request types

One-way buy, one-way sell, two-way; quantity in base or quote currency; spot pairs. Baskets and multi-leg requests.

Quote attributes

Provider, price, quantity, firm or indicative, quote ID, validity time, and last-look disclosure where the provider supplies it.

FIX messages

QuoteRequest (35=R), Quote (35=S), QuoteCancel (35=Z), QuoteRequestReject (35=AG), QuoteResponse (35=AJ) and ExecutionReport (35=8) for the resulting trade. Providers that use REST or WebSocket are connected through their own adapters.

Counterparty controls

Per-provider credit limits, per-provider maximum trade size, allowed instruments per provider, and pre-funding checks where settlement is pre-funded.

Records kept per RFQ

Requester, providers asked, every quote with timestamps, the lit-market reference at decision time, the decision and its reason if entered.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Liquidity providers in each request
  • Per-provider credit limit
  • Per-provider maximum trade size
  • Allowed instruments per provider
  • Pre-funding checks where settlement is pre-funded
  • Automatic answers to client RFQs within limits you set

Logged to the audit trail

  • request · requester, instrument, side, quantity, providers asked
  • quote received · provider, price, size, firm or indicative, validity
  • quote expired, canceled or rejected
  • lit-market reference at decision time
  • acceptance · quote ID and reason if entered
  • trade booked and settlement obligation created

06 / Where it fits

Works on its own
No.
Needs the core
Yes. RFQ needs the core platform and your connections to liquidity providers, because accepted quotes become orders, fills, positions and settlement obligations.
Who uses it
OTC desks, asset managers and funds trading blocks, brokers sourcing principal liquidity, banks executing for treasury or clients.

FAQ

Questions we get asked

  • Which liquidity providers can we connect?

    The providers you have agreements with. Qubit connects to them with your credentials. Available provider adapters are listed on the Integrations page, and new ones are added the same way as venue adapters.

  • Does Qubit act as the counterparty?

    No. Qubit never takes the other side of a trade. You trade with your liquidity providers under your own agreements, and Qubit records and manages the workflow.

  • Can our own clients send RFQs to our desk?

    Yes. Clients can request quotes over the API or FIX, and your desk answers with prices from the client pricing engine, manually or automatically within limits you set.

  • How does this help with best execution?

    For every RFQ you keep all the quotes received, their timing and the lit-market cost of the same trade. TCA and reporting turn that into a best-execution record per trade and over time.

Move block trading out of chat and into the record

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