Source-aware field guide · 20 answers
Liquidity Provider Selection
RFP and testing answers for comparing liquidity counterparties, executable pricing, capacity, credit, disclosures and operating support.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
RFP and testing answers for comparing liquidity counterparties, executable pricing, capacity, credit, disclosures and operating support. It is written for broker founders, dealing teams, risk managers, procurement leads and implementation engineers. The collection supports due diligence and testing; it does not rank providers or claim that a named relationship delivers tier-one liquidity, best execution or guaranteed fills. Use it to turn a sales conversation into a responsibility map, evidence request and acceptance plan that named reviewers can approve.
Each answer supports one operating decision: Which legal counterparty offers which executable service under what credit, pricing, order-handling, support and reporting terms, and what test proves it? Provider eligibility, protections and obligations vary by entity, product and jurisdiction, so registrations and contracts require independent verification. Work from the actual entity, instruments, client locations, counterparties and deployment design because the same label can describe materially different services.
The primary reference set is Global Foreign Exchange Committee — FX Global Code; Global Foreign Exchange Committee — Disclosure Cover Sheets; FCA — Financial Services Register; CFTC — Check Registration and Disciplinary History. These sources define standards, regulatory expectations or official operating concepts; they do not endorse FxTrusts or prove a feature in any deployment. Recheck the current source, signed order form, technical specification, permissions and test record before a production, trading or compliance decision.
How to Write a Liquidity Provider RFP
A liquidity provider RFP describes the buyer entity, products, jurisdictions, expected flow, protocols, credit model, reporting, support and evidence needed for comparison.
- Use it to
- Issue the same scenarios, datasets, assumptions and response format to every candidate so commercial and technical differences remain visible.
- Check the boundary
- A generic price request encourages incomparable proposals and leaves material order-handling terms undisclosed until implementation.
How to Verify a Liquidity Provider Legal Entity
Liquidity provider entity verification establishes the exact contracting company, registered details, permissions where applicable, ownership, dispute forum and service location.
- Use it to
- Match the proposal and contract to current official registers, legal documents, bank instructions and authorized signatories.
- Check the boundary
- A group brand, website logo or affiliate registration should not be attributed to the contracting entity without evidence.
How to Scope Liquidity Instruments and Sessions
Instrument scope defines symbols, contract specifications, trading sessions, holidays, price precision, order sizes and execution availability for the intended client offering.
- Use it to
- Request a machine-readable instrument schedule and reconcile it with the platform, risk, reporting and market-data configuration.
- Check the boundary
- A symbol shown in a feed may be indicative, temporarily unavailable or governed by different execution and financing terms.
How to Evaluate Liquidity Credit and Collateral
Liquidity credit and collateral terms determine prefunding, margin, netting, thresholds, calls, eligible currencies, close-out rights and capacity available to the broker.
- Use it to
- Model normal and stressed requirements by product and settlement cycle, including concentration and intraday changes.
- Check the boundary
- Attractive spreads do not compensate for a credit structure the broker cannot fund, monitor or reconcile safely.
How to Compare Executable Liquidity Prices
Executable price comparison measures actual accepted orders against contemporaneous quotes for matched symbol, direction, size, time and order instruction.
- Use it to
- Run controlled test sets and retain source ticks, order messages, acknowledgements, fills, rejects and fee-adjusted results.
- Check the boundary
- Displayed top-of-book prices may not be available for the requested size or remain valid when the order arrives.
How to Normalize Liquidity Provider Spreads
Spread normalization places provider quotes on the same symbol convention, precision, timestamp, session, size and fee basis before comparison.
- Use it to
- Separate raw bid-ask spread, broker markup, commission, swap, conversion and any per-million charge in the analysis.
- Check the boundary
- Comparing average displayed spreads from different periods or volume assumptions can produce a misleading ranking.
How to Test Liquidity Depth and Capacity
Liquidity depth testing evaluates executable quantity and price impact across levels, products, sessions and market conditions relevant to expected order flow.
- Use it to
- Submit approved test sizes and measure partial fills, weighted price, rejects, recovery and behavior near configured limits.
- Check the boundary
- A depth snapshot does not guarantee the same capacity remains available or belongs exclusively to the testing broker.
How to Review Liquidity Provider Last-Look Disclosures
A last-look review identifies whether and how a provider accepts, rejects or reprices requests after receiving them, including timing, criteria and disclosures.
- Use it to
- Compare published disclosures, bilateral terms and observed outcomes for matched requests while preserving enough data to investigate patterns.
- Check the boundary
- A low rejection rate alone cannot explain hold time, asymmetry, stale requests or the treatment of different flow categories.
How to Analyze Liquidity Provider Rejections
Rejection analysis classifies rejected requests by provider code, local validation, symbol, size, price age, session, limit and connectivity state.
- Use it to
- Normalize reason codes and investigate clusters with complete request, quote, response and configuration evidence.
- Check the boundary
- Treating every reject as lack of liquidity can hide invalid requests, credit limits, stale prices or integration defects.
How to Measure Liquidity Provider Slippage
Provider slippage compares an agreed reference price with the completed fill using a documented timestamp, direction, quantity and treatment of partial executions.
- Use it to
- Report positive and negative outcomes by product, size, session and volatility with fees and rejected orders shown separately.
- Check the boundary
- A single average can mask asymmetric outcomes, survivorship bias or reference prices the order could not actually access.
How to Measure Liquidity Connection Latency
Liquidity latency measurement separates quote receipt, local processing, network transit, provider acknowledgement and execution-report timing using synchronized clocks.
- Use it to
- Define measurement points and percentiles, then test from the intended hosting locations under realistic load and message patterns.
- Check the boundary
- A ping time or vendor headline cannot represent application processing, queueing, price age or complete order round trips.
How to Compare Liquidity Provider Protocols
Protocol comparison covers session rules, dictionaries, order types, market data, identifiers, limits, recovery, certification and support for each provider endpoint.
- Use it to
- Obtain provider-specific specifications and certify required normal, boundary, error and reconnect workflows before production acceptance.
- Check the boundary
- Calling both connections FIX does not mean they use the same version, messages, fields, semantics or operational procedures.
How to Calculate Total Liquidity Provider Cost
Total liquidity cost combines spread, commission, financing, data, connectivity, minimums, credit, conversion, rejects and operational overhead for the expected flow.
- Use it to
- Model representative products, sizes, holding periods and volumes under normal and stressed assumptions rather than one headline fee.
- Check the boundary
- A zero-commission or raw-spread description can omit minimum monthly charges, markups, swaps and infrastructure expenses.
Which Liquidity Contract Terms Need Review?
Liquidity contract review covers entity roles, products, order handling, pricing, credit, collateral, settlement, data use, suspension, liability, disputes and termination.
- Use it to
- Reconcile legal terms with the technical specification and operating model, then obtain qualified advice for the relevant entities.
- Check the boundary
- Technical test success does not cure inconsistent contractual rights, undefined discretion or unsuitable collateral obligations.
How to Review Liquidity Provider Disclosures
Provider disclosure review examines capacity, principal or agency role, order handling, last look, pre-hedging, markups, data use, conflicts and platform practices.
- Use it to
- Use standardized disclosure materials as a starting point for bilateral questions tied to the proposed relationship and flow.
- Check the boundary
- A completed disclosure cover sheet supports comparison but does not replace detailed contracts, testing or buyer due diligence.
How to Run a Liquidity Provider Proof of Concept
A liquidity proof of concept tests agreed instruments, message flows, sizes, market conditions, failures, reports and support processes in a controlled environment.
- Use it to
- Predefine success measures, test data, duration, responsibilities, defect severity and the evidence required for a production decision.
- Check the boundary
- Demo results using simulated flow or a different entity and endpoint may not predict the contracted production service.
How to Test Liquidity Provider Disconnect Recovery
Disconnect recovery testing verifies session restoration, subscriptions, order state, missed messages, duplicate prevention and reconciliation after connectivity loss.
- Use it to
- Interrupt market-data and order sessions separately and together while orders are new, partly filled, cancelled and awaiting acknowledgement.
- Check the boundary
- A reconnected socket does not prove prices are fresh or that every pre-disconnect order reached a known final state.
How to Plan Multiple Liquidity Counterparties
A multiple-counterparty design defines eligibility, aggregation, routing, credit, failover, pricing, identifier and reconciliation rules for each connected provider.
- Use it to
- Test capacity loss, conflicting symbol terms, stale sources, partial fills and provider suspension without silently changing customer handling.
- Check the boundary
- Adding providers can increase resilience or choice while also multiplying integration, credit, monitoring and dispute complexity.
How to Monitor a Liquidity Provider After Launch
Post-launch provider monitoring tracks quote quality, executable outcomes, rejects, latency, incidents, credit use, reconciliations, disclosures and support against agreed expectations.
- Use it to
- Review trends by product, size and market condition with jointly understood definitions and documented remediation decisions.
- Check the boundary
- Good aggregate uptime can coexist with stale symbols, asymmetric execution or repeated failures during the periods that matter most.
How to Exit or Replace a Liquidity Provider
A liquidity provider exit plan addresses open exposure, collateral, settlements, records, credentials, market data, client effects and cutover to approved alternatives.
- Use it to
- Set notice, migration, parallel-test, reconciliation and revocation steps before termination pressure makes them difficult to coordinate.
- Check the boundary
- Closing connectivity before positions, cash and message histories are reconciled can leave unresolved financial and operational obligations.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.