Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Industry ProvidersProvider profile

Finery Markets: liquidity aggregation, broker workflows and institutional crypto software

Finery Markets supplies software for institutional crypto execution, liquidity distribution and post-trade operations. Its master-account model gives brokers control over client limits and markups, while counterparties maintain their own trading and settlement relationships.

By FXBrokers.ai ResearchOperating status: ActivePublished Sources checked

Services & customers

Sections ↑

Finery Markets gives institutions a shared software layer for sourcing crypto liquidity, distributing prices and administering the resulting positions. A broker can consume liquidity from several counterparties, add client-specific pricing and distribute it through its own accounts. The business began in 2019, with its first live trade recorded in the fourth quarter. Its customers include brokers, banks, payment businesses and market makers.[2]

Platforms & products01

Product roles

Product roles
ProductPrincipal use
FM MarketplaceConnect institutional liquidity takers and makers through a common interface and API.Source 9
FM Liquidity MatchA master account manages sub-account balances, positions, limits and markups; the operator can source outside liquidity and internalise client flows.Source 3
FM White LabelA branded client interface for an institution’s crypto trading business.Source 5
FM PulseCompare effective spreads using pair, trade size and expected volume; liquidity providers can examine wallet share.Source 6
FM SpaceA gated network for discovering liquidity, banking, custody and other infrastructure partners.Source 7

The master-account structure has a practical settlement consequence: the master deals separately with each external liquidity provider, while its clients settle with the master. An OTC desk can therefore aggregate several sources without requiring every end client to establish those external relationships. Sub-accounts can have up to ten authorised users with different rights.[4]

Specifications02

Execution methods

Execution methods
MethodMechanism
Firm order bookLiquidity providers submit firm orders without a last-look approval stage.Source 8
AggregationOrders from connected providers appear in one book ordered by price and time; completed trades identify the actual counterparty.Source 9
Quote StreamsIndicative liquidity is routed to an external LP for execution. Last look and rejection remain possible.Source 10
RFQA taker requests a quote and selects a maker; execution is on the maker’s external platform, with last-look acceptance or rejection.Source 17
Pending limit ordersGTC instructions remain until filled or cancelled. Risk checks apply to execution rather than initial placement.Source 25
Aggressive-order delayMarket/Limit IOC and FOK orders have a 100 ms latency floor under the documented design.Source 11

Quote Streams’ Best Price Available mode compares the size-weighted price of each stream with the aggregated firm book. It routes the full order to the selected source rather than assuming a displayed quote is already a completed trade. Risk checks reserve the relevant limit while awaiting the LP’s response; the LP can apply its own checks.[10]

Platforms & integrations

Sections ↑

The published connectivity stack includes FIX 4.4, WebSocket and REST alongside the graphical interface. Quote-stream bridges can connect on a customer’s behalf; this involves granting the bridge provider API access, so the integration reaches trading functions rather than merely displaying prices.[3][10]

Specifications03

API behaviour that affects production integration

API behaviour that affects production integration
InterfaceDocumented behaviour
RESTSigned JSON POST calls use a key/secret pair, HMAC SHA384, a timestamp and a nonce. Production and test endpoints are separate.Source 12
Retry handlingNonces are unique in a rolling two-minute window. Retrying the same request with the same nonce prevents a second processing; duplicate copies receive an invalid-nonce error. New requests require increasing nonces.Source 12
WebSocket feedsA subscription starts with a snapshot followed by incremental changes. The documented idle timeout is 80 seconds, with at most 100 connections per IP.Source 13
Cancel on disconnectWhen enabled, cancellation applies to orders placed through the lost connection; other connections’ orders are not swept up by that event.Source 13

User permissions separate viewing, trading, limit management, settlement operations, API-key management, user administration and sub-account administration. View mode is the default. An employee who needs a password or two-factor reset is removed and re-added under the published procedure. These controls matter because a settlement operator can commit transaction records while a trader can submit and cancel orders.[14]

Pricing & commercial terms

Sections ↑
Pricing & charges04

Published software usage rates

Published software usage rates
Calendar-month qualifying turnover, USD equivalentTaker / eligible master rate
Below USD 50 million0.03% / 3 bpsSource 15
USD 50 million to below USD 200 million0.02% / 2 bpsSource 15
USD 200 million or more0.01% / 1 bpSource 15
Pricing & charges05

Other published charges

Other published charges
ItemBasis
Maker usage0.01% of USD-equivalent turnover.Source 15
Interdealer transactionsMaker: 0.01%; taker: no usage fee.Source 15
White labelUSD 10,000 per month.Source 15
Overnight tool10% of applicable user rollover-fee revenue.Source 15
Onboarding / monthly minimumAmounts depend on the user’s market configuration.Source 15

The calculation methodology includes markups in turnover. Within the master aggregation model, a trade between the master and its own sub-account, or between its sub-accounts, counts once. Trades where the master supplies another master or taker as maker do not qualify toward the master’s tier. The methodology also provides for API-integration and project-based consultancy charges.[16]

The monthly minimum remains payable without actual usage. Onboarding is a non-refundable upfront charge, with amounts specified for the agreed configuration. The white-label page advertises freedom from fixed-term obligations and costly multi-year commitments; a specific cancellation notice or exit-service price was not established from the public material.[16][5]

Where authenticated website fee conditions conflict with the public tariff, the operating rules give the authenticated conditions precedence.[17]

Implementation & delivery

Sections ↑

Onboarding starts with legal company details, acceptance of the software terms and trading preferences. Finery’s introductions use the customer’s banking arrangements and desired pairs. The chosen LP then performs its own business and compliance checks. It may enable view-only prices before trading approval; after KYB, the parties set their limits. A test account for API setup is offered during account creation, with integration charged separately.[18]

Finery describes its hosted infrastructure as AWS-based and advertises 99.99% uptime, together with SOC 2 Type 1 and Type 2 examinations. These are product claims; the public material reviewed does not establish a contractual service-credit schedule.[5]

Process06

Credit and settlement controls

Credit and settlement controls
ControlOperating effect
Bilateral limitThe smaller limit set by the two counterparties applies. Different limit currencies are translated at current prices.Source 19
Exposure calculationUses the greater absolute long or short reachable-position total; deposits and uncommitted settlements can consume the limit.Source 19
Collateral thresholdsThe LP/master can define initial, restricted-trading and maintenance levels. Initial margin constrains settlement withdrawals; maintenance can give the provider a right to liquidate.Source 19
ReplenishmentSettling the obligation and withdrawing the assets restores capacity; increasing the limit changes how much liquidity is accessible.Source 19
External paymentSend the wire or blockchain transfer, then record its reference or transaction hash in the settlement messenger. Creating the message does not itself move funds.Source 20
Asset requestA request left incomplete by the counterparty expires after seven calendar days. Committed status records that receipt has been validated.Source 20

Settlement automation can connect to Fireblocks, another crypto custodian or a bank with a suitable transfer API. The integration passes instructions and transaction data; the custodian or bank performs the transfer. Finery’s Fireblocks route supports auto-commit based on blockchain-verified transaction status.[21]

The Fireblocks option appears only when both counterparties have completed the integration and the asset/network is supported. Creating the settlement in Finery generates a transfer request in the customer’s Fireblocks workspace. The customer still funds it and completes any workspace approval policy. Blockchain confirmation updates the transaction to Committed and recalculates both parties’ open positions.[24]

Support & contacts

Sections ↑

Normal software availability is 24/7, subject to maintenance. During a system failure, the rules cancel open orders regardless of time in force, but orders already filled remain filled even if confirmation has not arrived.[17]

Official contact routes

Technical supportEmail
[email protected]Source 10

Scope API, quote-stream and bridge assistance.

General enquiriesEmail
[email protected]Source 7

Scope Company and product enquiries.

Product documentationWebsite
https://faq.finerymarkets.com/Source 26

Scope Operating guides and API reference.

Permissions & service scope

Sections ↑

The legal imprint names Finery Markets (BVI) Limited, registration 2079689. It describes an institutional, non-custodial SaaS supplier: customers operate their own environments, with the financial relationships held between counterparties. Software access is restricted to eligible institutions, with additional UK professional-client and eligible-counterparty conditions.[1]

The operating rules require a separate bilateral trading agreement before transactions. That agreement prevails in a conflict. Masters are responsible for their sub-accounts’ due diligence and AML procedures; Finery supplies records and tools, while the parties retain responsibility for delivery, clearing and settlement.[17]

Operator & evidence

Sections ↑

Finery’s published history identifies Ilia Drozdov as a co-founder in 2019 and Konstantin Shulga as CEO and co-founder, joining in 2021. The company records a USD 5.5 million seed round in the fourth quarter of 2022 and the white-label launch in the second quarter of 2023. This development explains the expansion from a common liquidity interface into software that other institutions use for their own client businesses.[2]

Operator
Finery Markets (BVI) Limited
Service scope
Institutional crypto trading software, liquidity aggregation, master/sub-account operations and analytics; counterparties supply credit and settle externally.
Customer types
Brokers; Prime brokers; Liquidity providers; OTC desks; Banks; Payment providers; Asset managers
Delivery
SaaS; Hosted; API
Pricing publication
Public and quoted pricing
Platforms
FM Marketplace; FM Liquidity Match; FM White Label; FM Pulse; FM Space
Integrations
FIX 4.4; REST API; WebSocket API; Fireblocks settlement integration
Implementation
Software access and counterparty onboarding are separate. The documented process includes LP KYB, reciprocal limits and an optional paid API sandbox integration.
Support
Technical support is available at [email protected]; general enquiries at [email protected]. No contractual response-time schedule was established.
Permissions and regulatory scope
The BVI imprint identifies a software vendor, not a broker, exchange, custodian or settlement counterparty. It restricts access to eligible institutional users; customer permissions and bilateral contracts determine financial-service scope.

Provider metadata checked 20 Oct 2026Source 2Source 1Source 3Source 6Source 9Source 5Source 15Source 18Source 10Source 7Source 21

Additional Information

Sections ↑
Specifications07

Records, recovery and integration resources

Records, recovery and integration resources
TopicPractical detail
ReportingDaily and monthly PDF/CSV reports cover trades, settlements and position snapshots. GUI History exports allow date selection, filenames and optional column headers.Source 22
API reconciliationdealHistory, settlementHistory and settlementTransactionHistory expose records for integration. The settlement-history endpoint defaults to and caps each response at 250 records, with date/ID filters.Source 23Source 22
Stopping a relationshipDisabling counterparty trading leaves settlement available, and applicable overnight charges continue until the outstanding exposure is resolved.Source 19
Data after exitThe privacy policy retains personal information during the relationship and afterwards as necessary or legally required; it gives no fixed universal deletion deadline.Source 17
Implementation examplesThe quick-start guide links official REST/WebSocket examples and a separate instruction repository for AI coding assistants. The documented link concerns integration development.Source 26

FM Pulse adds a different view from the executable book: takers can compare spread estimates for a selected pair, size and volume, while LPs can assess wallet share and compare their pricing with other sources. These analytics complement the counterparty and trade records; they are not a guarantee that a particular future order will fill at the displayed estimate.[6]

Follow the evidence

Sources & further reading

  1. Legal imprint Finery Markets · Accessed 20 Oct 2026
  2. Company background Finery Markets · Accessed 20 Oct 2026
  3. FM Liquidity Match Finery Markets · Accessed 20 Oct 2026
  4. Liquidity Match operating guide Finery Markets · Accessed 20 Oct 2026
  5. FM White Label Finery Markets · Accessed 20 Oct 2026
  6. FM Pulse analytics Finery Markets · Accessed 20 Oct 2026
  7. FM Space network Finery Markets · Accessed 20 Oct 2026
  8. Firm Order Book Finery Markets · Accessed 20 Oct 2026
  9. Aggregated Order Book Finery Markets · Accessed 20 Oct 2026
  10. Quote Streams Finery Markets · Accessed 20 Oct 2026
  11. Taker latency floor Finery Markets · Accessed 20 Oct 2026
  12. REST API authentication Finery Markets · Accessed 20 Oct 2026
  13. WebSocket API and disconnects Finery Markets · Accessed 20 Oct 2026
  14. User and API roles Finery Markets · Accessed 20 Oct 2026
  15. Tariff policy, effective 10 January 2025 Finery Markets · Accessed 20 Oct 2026
  16. Fee calculation methodology, amended December 2023 Finery Markets · Accessed 20 Oct 2026
  17. Operating rules and privacy policy Finery Markets · Accessed 20 Oct 2026
  18. Counterparty onboarding Finery Markets · Accessed 20 Oct 2026
  19. Risk limits Finery Markets · Accessed 20 Oct 2026
  20. Settlement messenger Finery Markets · Accessed 20 Oct 2026
  21. Settlement automation Finery Markets · Accessed 20 Oct 2026
  22. Reports and exports Finery Markets · Accessed 20 Oct 2026
  23. Settlement history API Finery Markets · Accessed 20 Oct 2026
  24. Fireblocks settlement workflow Finery Markets · Accessed 20 Oct 2026
  25. Pending limit orders Finery Markets · Accessed 20 Oct 2026
  26. Integration examples Finery Markets · Accessed 20 Oct 2026

This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.

Report an error or submit an update