Zodia Markets: institutional quotes, settlement and controlled payouts

The available-instruments endpoint is a useful distinction between a broad marketing catalogue and an account’s working market set. Its sample currency pairs illustrate the response format; they do not prove that each sample is live for every client. Neither a reserved settlement-date field nor an empty depth field should be interpreted as a futures product or order-book access. The enabled and active flags are the relevant operational checks.[3]

Order handling distinguishes success, failure, a pending outcome and an indeterminate outcome. An indeterminate order may already have traded, so the documented response is reconciliation with the desk rather than placing a replacement. The order channel supports an idempotency key to prevent duplicate execution when the same request is retried. That safeguard is useful for institutional automation but does not turn an uncertain response into a confirmed fill.[7]

Pricing is quote-only for this profile. The account-group specification links the applied spread, credit limit and permissions to the chosen group. A quotation for another account is therefore an unreliable cost comparison. No universal public commission table, monthly account fee or standard withdrawal tariff was established from the inspected current material.[4]

For an institutional conversion, the useful cost record is the amount paid, the asset quantity actually received and any separate charges. Zodia’s trade record includes the settlement and traded amounts, currencies, executed price and settlement date. It also distinguishes desk OTC activity from RFS activity. This allows a firm to compare its own execution records consistently; it does not supply an independent public spread benchmark.[5]

The payment-participant directory separates the client’s own entity from incoming senders and outgoing beneficiaries. The API can add accounts and wallets beneath an existing participant; creating a new sender or beneficiary requires the relationship manager. This is a meaningful constraint for businesses paying many counterparties: onboarding the business alone does not approve every future settlement destination. The portal also exposes the account-details and third-party-trading workflows.[9]

Withdrawal requests are not idempotent. After a timeout or ambiguous response, the documentation instructs the client to inspect the withdrawal list before resubmitting; submitting again with a fresh nonce can create another request. The initial balance check also precedes a stricter Operations check. The bank or blockchain leg and the internal approval leg therefore need separate tracking.[12]

Zodia’s current website describes money and digital assets as segregated in client accounts with independent banking and custodian partners. That is the provider’s custody description, not an independently tested insolvency opinion. An institutional mandate should identify the actual account holder, custodian, legal entitlement and settlement exposure in its agreement. The name Zodia Markets does not by itself establish a direct custody contract with the separately branded Zodia Custody business.[1]

Optional signed intent adds a signature over critical order parameters using the client’s RSA private key. Zodia presents it as protection against changes by intermediate systems and as evidence of the authorised order. Ordinary authenticated orders remain possible without it. This is an execution-control feature, so it should be evaluated separately from wallet custody, withdrawal authority and contractual loss allocation.[16]

Wallet approvals cannot be self-certified through the API: enabled, verified and whitelisted states are controlled by Zodia. A registration can be rejected after submission, and the relationship manager supplies the reason. The institution consequently needs an authorised operations workflow as well as a trading connection; possession of a trading credential alone does not create an approved payout destination.[11]

The API documentation assigns UK or AME execution according to incorporation, applicable requirements and agreement. The ADGM licence expressly excludes retail clients. An office location alone does not establish access for a company incorporated in that country.[18][21]

The API introduction directs prospective and existing institutions to sales, the relationship manager and API support. The public status page separately tracks E-Trader, OTC, Settlement and Customer Portal. That separation matters when prices work but a payout is delayed. Its October 2026 record includes scheduled RFS maintenance during which clients could not execute electronically; the advertised service window is not a promise of uninterrupted dealing.[2][19]

A current, publicly accessible contractual complaints timetable was not established in this review. The institution should obtain the procedure and escalation contact for its contracting entity during onboarding. An unresolved trade dispute needs the order reference, confirmation, value date and payment evidence; the existence of a regulator entry does not itself specify the dispute-resolution route.[18][17]

The FCA explains that UK registration under the money-laundering regime covers financial-crime supervision. Registration is not an endorsement, and it does not itself supply Financial Ombudsman Service or FSCS protection for crypto services. This distinction is material when evaluating Zodia’s bank-connected ownership and branding: the customer needs the protections attached to the specific agreement and activity.[22]

SC Ventures’ July 2025 funding announcement says Zodia Markets was founded in 2021 by Usman Ahmad and Nick Philpott, with backing from SC Ventures and OSL Group from inception. The announced USD18.25 million Series A was led by Pharsalus Capital and included Circle Ventures and other investors. Those are documented investment relationships; they do not establish an unconditional guarantee from Standard Chartered or disclose the current percentage held by each shareholder.[23]

The current website advertises more than USD40 billion traded, 47 pairs, 17 currencies and 16 onshore markets, together with 24/5 service. These are provider-published indicators without a common measurement period or independently reconciled active-client count. They cannot support a precise daily-volume ranking against public exchanges. The current service documentation and October 2026 status notices provide stronger evidence that the institutional operation remains live.[1][19]

Operator

Zodia Markets (UK) Limited / Zodia Markets (AME) Limited

Exchange model

Centralised

Service scope

Institutional matched-principal OTC brokerage, E-Trader streaming execution and fiat/crypto settlement. The profile covers the current brokerage service.

Client types

Professional clients; Institutional clients

Pricing publication

Quote only

Pricing scope

Account- and size-specific bid/offer pricing; no universal public commission or transfer tariff was verified.

Funding scope

Approved bank accounts and crypto wallets; supported third-party collection and delivery. Operations approval governs withdrawals.

Custody and asset handling

The provider describes segregated accounts at independent banking and custody partners. Settlement balances require contractual review; a separate Zodia Custody account is not implied.

Client eligibility

Institutional onboarding and entity assignment; the ADGM entity cannot serve retail clients.

Support

Relationship manager and trading desk, API documentation and a public component-status page. Obtain the contracting entity’s formal complaint procedure during onboarding.

Authorisation and registration scope

UK FCA cryptoasset-register entry FRN 954558 identified in the regulator’s indexed record; detailed dynamic fields were unavailable. ADGM FSP 220132 is active and limited to matched-principal virtual-asset dealing, excluding retail clients.

Exchange metadata checked 21 Oct 2026Source 2Source 18Source 21Source 20Source 1Source 12

Streaming prices carry an actual settlement date. T and T1 refer to the closest available dates; as cut-offs pass, a price can roll to a later date. Check that returned date rather than assuming that every trade settles today.[6]

Session-based recovery can redeliver a terminal order result after reconnection. Clients must match that result to the transaction identifier and avoid booking duplicate deliveries. Price subscriptions, however, need to be recreated after a lost connection. This makes recovery design a real part of product suitability for an automated treasury or brokerage desk, alongside the headline availability of an API.[17]

Third-party delivery and collection are substantial parts of the service, but they are permissioned workflows. The sender or beneficiary, asset, wallet and settlement network must agree with the approved setup. For a payments business, this connects execution to the intended commercial transfer; for a fund trading only its own account, it creates additional operational choices rather than a requirement to route every transaction through a third party.[14][15]

Account groups can separate strategies, funding and settlement and restrict which team members can use each group. They are configured through the relationship manager, and an API key can see only a subset. This supports operational separation between funds or desks. It should not be described as independent legal ownership or a separate insolvency estate without the corresponding contractual structure.[4]

The trade-list service labels an executed transaction awaiting settlement separately from a fully processed transaction. Its single trade record also differs from the transaction service’s individual accounting legs. An operations team should reconcile the economic trade once while checking that both asset and currency legs reach the expected state. This is especially useful when the trading desk and treasury team work from different systems.[5]