XTB Institutional: liquidity, white-label platforms and the X Open Hub transition

XTB Institutional is the group’s business-to-business liquidity and technology operation, formerly X Open Hub. The June 2026 announcement describes a consolidation of branding rather than a new counterparty: existing legal entities, agreements and service arrangements were to remain unchanged. This profile concerns the institutional service, not the separately documented retail XTB account.[1]

For a brokerage, those components answer different questions. A platform can present an instrument without fixing the credit terms on which the brokerage can hedge it. Conversely, a liquidity agreement can support an existing front end without requiring the broker to replace its client portal. The relevant comparison is therefore the complete execution chain: client platform, order gateway, liquidity account and the records returned for reconciliation.

The legacy liquidity page continues to describe FIX/API access and integration with MT4/MT5 through bridges or gateways, naming examples such as PrimeXM and Match-Trade. These are advertised connection routes, not confirmation that every version, instrument and account is enabled by default. A migration must align contract sizes, symbol names, precision, sessions and order-status handling.[3]

A useful acceptance test compares the same trade across the gateway, liquidity account and broker ledger. An accepted network message is not necessarily an executed order; reconnecting must not create a second instruction. This is an implementation requirement derived from the separation of command and streaming channels, not a claim that a specific customer integration was tested.[5]

The public liquidity offer advertises no OTC volume commission and no minimum deposit, but that is not a zero-cost proposition. Spreads, overnight financing and the agreed commercial schedule remain relevant. The page’s average-spread examples lack a sufficiently clear observation period for a like-for-like execution-cost calculation, so they are not reproduced as executable prices.[3]

The interest page displays annual rates of up to 3.60% for USD, 1.20% for EUR, 3.65% for GBP and 3.20% for PLN. It uses eligible free funds at midnight CET/CEST, a daily rate divided by 365, and payment within ten working days of the following month. Signed participation, positive balances/free funds and individually agreed turnover conditions apply. These are variable published rates, not guaranteed APYs. At an assumed unchanged 3.60% rate, USD 100,000 eligible for one day produces about USD 9.86 before tax; this arithmetic does not establish eligibility.[9]

The published application identifies XTB S.A., registration 0000217580, as the contracting liquidity provider. It requires corporate/KYC documentation and acceptance by XTB; submission alone does not conclude the agreement. The application also contains eligible-counterparty classification. Those conditions should not be replaced with retail-account opening assumptions.[6]

Implementation should preserve two separate approval tracks: commercial/legal acceptance and technical readiness. The latter includes test credentials, instrument mapping, connection recovery, reconciled opening balances and a documented escalation route. Moving customer-facing software first and resolving the hedge account later creates an avoidable period in which the broker’s displayed product and executable product may differ.

The legal-information page groups the agreement, risk and cost documents, execution material and complaint procedures. The document set contains older underlying dates. A file still linked today is useful evidence of what the provider publishes, but its availability is not proof that an old appendix is the negotiated version for a new customer.[7]

The claims procedure asks for the client identity, account number, event time, detailed description and requested remedy. It states a response within 30 days of filing, with reasons and an expected response date if delayed, capped at 90 days from receipt. It also permits postal and in-person filing at XTB S.A., Prosta 67, Warsaw. These are this published institutional procedure’s clocks, not an assumed ombudsman eligibility rule.[11]

The division’s public group description refers to permissions held across XTB entities. Those licences should not be collapsed into one global institutional authorisation. The signed counterparty, service, client classification and jurisdiction determine the applicable terms. No current regulator-by-regulator permission inventory was independently established for this profile.[2]

A particular scope trap appears in the linked execution policy: the 19 January 2024 text expressly addresses retail and professional clients, whereas the liquidity application contains eligible-counterparty classification. This does not demonstrate that the two documents conflict; it means the reader must establish which provisions apply to the institutional contract rather than transplant retail best-execution or protection language.[12]

The name change is documented by a dated group announcement and the current institutional website, while several detailed product and contact resources remain on xopenhub.pro. The old name is therefore retained as an alias, not counted as a second provider. The announcement’s continuity statement does not by itself amend a customer’s particular contract or remove the need to verify any new bank or support instructions.[1]

Operator

XTB S.A. for the published liquidity agreement

Service scope

Institutional liquidity and hosted trading technology, with separate attention to connection methods, pricing scope, onboarding, complaint routes and the continuity of the former X Open Hub business.

Customer types

Banks; Regulated brokers; Selected fintech businesses

Delivery

Hosted; API

Pricing publication

Public and quoted pricing

Platforms

xStation; xAPI

Implementation

Institutional acceptance and technical integration are separate steps.

Support

Current sales and legacy support routes are documented; contractual response commitments require confirmation.

Permissions and regulatory scope

The published agreement names XTB S.A.; permissions must be matched to the actual service, entity and client category.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12

The public liquidity terms allow ordinary termination on at least three months’ written notice. They also contain default/close-out provisions and preserve accrued rights and obligations. Ending the commercial relationship is consequently different from merely disabling a bridge. A departure plan needs positions, collateral, final financing and statement reconciliation to be addressed under the actual signed version.[6]

For procurement, the important unresolved items are the account-specific instrument schedule, full technology charges, collateral and margin arrangements, negotiated support service levels, and the legal treatment of an outage or disputed fill. These are not filled with assumed market conventions. Public documentation supports the service map above; it does not establish a completed onboarding, executed trade or tested failover.