Cybrid primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone Cybrid whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official Cybrid site, docs portal, product pages for B2B payments and accounts/wallets, the platform-overview and sandbox guides, the public GitHub organization, and the generated Bank API documentation repo.
  • The materials consistently frame Cybrid as a compliant stablecoin-and-fiat orchestration platform rather than as a narrow on/off-ramp or trading API.

Primary-source snapshots

1) Homepage

  • URL: https://cybrid.xyz/
  • Key excerpt:
    • The homepage calls Cybrid an “Intelligent Layer for Money Movement” and says it orchestrates payments across stablecoins and fiat.
    • It highlights ACH, Wire, RTP, EFT, Interac, USDC, USDT, Bitcoin, and Lightning support through one API surface.
    • It also emphasizes named bank accounts, instant settlement, integrated compliance, and both managed and self-managed deployment models.

2) Docs introduction

  • URL: https://docs.cybrid.xyz/docs/introduction
  • Key excerpt:
    • The docs intro says Cybrid is a platform for “compliant stablecoins and fiat payment infrastructure.”
    • It directs builders to a sandbox environment, recipes, and API reference, which confirms the product is intended as a developer-integrated backend platform.

3) Platform overview

  • URL: https://docs.cybrid.xyz/docs/platform-overview
  • Key excerpt:
    • The overview says the platform supports both traditional financial applications and cryptocurrency-based products, including on/off-ramp apps, stablecoin cross-border remittance, and B2B solutions.
    • It describes an end-to-end API stack spanning KYC/KYB onboarding, opening bank accounts, fiat money movement, cryptocurrency trading and custody, and international transmission.
    • It also enumerates core API resources such as Organization, Bank, Customer, Counterparty, Account, Quote, Trade, Transfer, and Identity Verification.

4) Accounts and Wallets product page

  • URL: https://cybrid.xyz/product/fbo-accounts-wallets
  • Key excerpt:
    • The page says Cybrid supports named accounts and FBO account infrastructure so customers can store, pay, and get paid in USD, CAD, or stablecoins.
    • It says accounts can connect to ACH, EFT, wires, RTP, FedNow, and Interac e-Transfer, with automatic or on-demand conversion between fiat and stablecoins.
    • It also stresses real-time transaction logging and reconciliation.

5) B2B payments product page

  • URL: https://cybrid.xyz/solutions/b2b-payments-stablecoin-infrastructure
  • Key excerpt:
    • The B2B page says Cybrid automates supplier payouts, vendor disbursements, and treasury operations through orchestration APIs.
    • It highlights multi-rail settlement, full ledgering of debits and credits, liquidity management, and integrated KYC/KYB + AML monitoring.
    • The framing is clearly around payment operations and treasury control, not just payment acceptance.

6) Sandbox guide

  • URL: https://docs.cybrid.xyz/docs/cybrid-sandbox
  • Key excerpt:
    • The sandbox docs say builders can sign in through the Partner Portal, generate Organization or Bank API keys, test onboarding and verification, and simulate trades and transactions.
    • This reinforces that Cybrid exposes a serious integration and simulation surface for payment operators.

7) Public GitHub organization and Bank API repo

  • URLs:
  • Key excerpt:
    • The public GitHub org describes Cybrid as a cryptocurrency infrastructure platform with liquidity, custody, and compliance tooling, and lists language-specific API clients, SDKs, and demo apps.
    • The Bank API README says developers can interact directly with REST APIs or generated clients and references Organization, Bank, and Identities APIs, interactive OpenAPI documentation, sandbox usage, OAuth 2.0 bearer-token auth, and broad resource scopes.

Working conclusion

Cybrid is best cataloged as a compliance-heavy fiat-and-stablecoin money-movement control plane. The deciding evidence in this pass was the repeated combination of named/FBO accounts, multi-rail fiat connectivity, stablecoin conversions, integrated compliance workflows, sandbox + OpenAPI developer surfaces, and public multi-language client infrastructure.