Hex Trust primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official site’s custody / payments service pages plus public GitHub and OpenAPI artifacts.

Primary-source snapshots

1) Official homepage

• URL: https://www.hextrust.com/
• Key excerpt:
  • The homepage says Hex Trust offers fully regulated institutional digital-asset markets services, custody, and staking.
  • It also highlights Convert-to-Pay, an instant payment API for institutions that enables digital-asset acceptance and compliant fiat settlement for regulated payment providers.
  • The broader service taxonomy already suggests Hex Trust is operating across custody, markets, staking, and payments rather than selling only vault storage.

2) Custody page

• URL: https://www.hextrust.com/services/custody
• Key excerpt:
  • The custody materials describe institutional-grade digital-asset custody with HSM FIPS 140-3 Level 3 security, cross-domain controls, role segregation, SOC governance work, and high-performance operations.
  • The page explicitly mentions insolvency-remote legal structure, insured custody, and support for a wide set of chains and assets.
  • The FAQ section says Hex Trust is regulated in multiple jurisdictions including Singapore, Dubai, and Hong Kong and emphasizes off-balance-sheet client asset protection.

3) Convert-to-Pay service page

• URL: https://www.hextrust.com/services/payment/convert-to-pay
• Key excerpt:
  • The page describes Convert-to-Pay as an instant payment API built for institutions.
  • It outlines an RFQ-based workflow in which a user receives a quote and deposit address, crypto is received into Hex Trust custody, assets are either off-ramped directly or converted via external liquidity venues, and fiat is paid out to the client’s bank account.
  • The stated use cases include payout providers, prepaid card issuers, and digital payment providers, which is a strong clue that Hex Trust should be cataloged partly as payment-and-settlement infrastructure.

4) Convert-to-Pay OpenAPI specification

• URL: https://raw.githubusercontent.com/hextrust/convert-to-pay-api/main/openapi.yaml
• Key excerpt:
  • The OpenAPI file is titled HTM Payment API and documents authenticated endpoints under https://api.hextrust.com/v1.
  • It specifies JWT-based authentication plus API-key headers and includes endpoints such as /system/ping, /system/time, and /convert-to-pay/availablePairs.
  • The existence of a public OpenAPI artifact is strong evidence that the payment surface is a real API product rather than only a sales narrative.

5) GitHub organization

• URL: https://github.com/hextrust
• Key excerpt:
  • The public org includes repos such as convert-to-pay-api, HexClientApi, HexClientApiPHP, web3-provider-sdk-js, and token- or infrastructure-adjacent repos like wrapped-xrp and hex-stablecoin-usd.
  • Even though the public repo surface is not exhaustive, it is enough to show Hex Trust has shipped external-facing API and infrastructure artifacts.

6) HexClientApi README

• URL: https://raw.githubusercontent.com/hextrust/HexClientApi/master/README.md
• Key excerpt:
  • The README describes HexClientApi as a Node.js helper for Hex APIs.
  • It says full API specification is available through the Hex Trust ops team and provides a basic usage example for authenticated client API requests.
  • This suggests the public repos are one window into a larger institutional API surface that is partly customer-gated.

Working conclusion

Hex Trust is best cataloged as institutional custody, staking, and crypto-fiat settlement infrastructure. The combined homepage, service pages, OpenAPI spec, and public API-helper repos show a broader digital-asset control plane than a simple custody-only label would capture.