Chain

  • Name: Chain
  • URL: https://chain.com/
  • Category: stablecoin payments company / wallet-and-ledger control plane operator / bank-and-card settlement operator
  • Tags: ethereum-ecosystem
  • Summary: Chain belongs in companies/, not projects/, because the useful question is not what protocol does Chain run? but which named operator onboards enterprises, links bank accounts, screens wallets and recipients, issues wallet-and-ledger accounts, routes payouts across bank / card / onchain rails, and publishes the payment-state truth customers are expected to trust? The practical leverage sits in admission, screening, funding, payout routing, ledger design, and the regulated operator shell around fiat-to-stablecoin conversion and settlement workflow.
  • What it does:
    • Onboards enterprises into a stablecoin operating stack that bundles wallets, ledger/account models, bank funding, recipient management, and multi-rail payout workflow
    • Lets customers fund wallets from linked bank accounts and automatically convert fiat into USDC as part of the first-party operating path
    • Supports payouts to registered recipients through bank rails, direct onchain USDC transfers, and card off-ramp flows via Visa Direct and Mastercard Send
    • Operates wallet-registration and wallet-management APIs with sanctions screening and risk scoring on submitted blockchain addresses
    • Packages an immutable-ledger / account-system story around pooled, FBO, and dedicated account models rather than exposing one narrow payment API in isolation
  • Key claims:
    • The homepage says Chain provides stablecoin infrastructure for payments, cards & wallets, emphasizes direct stablecoin rails, and claims access to banking networks such as ACH, Fedwire, FedNow, RTP, SEPA, Faster Payments, Visa, and Mastercard, which makes the operator boundary explicit
    • The payments product page says Chain provides access to a partner network of regulatory licenses plus Chain Direct Infrastructure, supports 7+ major stablecoins and 12 fiat currencies, and lets enterprises design bi-directional flows between fiat and stablecoins
    • The payments docs describe funding, payouts, payees, and bank-account linking flows including automatic fiat-to-USDC conversion and Plaid-based bank linking, which means the day-1 operating model is company-shaped rather than protocol-neutral
    • The wallets docs say wallet addresses are automatically screened against sanctions lists and risk databases and expose risk scores / categories as part of the API surface, which is exactly the kind of policy authority that belongs in companies/
    • The cards product page says Chain supports stablecoin off-ramp payouts to existing Visa and Mastercard cards across 200+ countries and territories without card issuing, which shows the company is composing multiple external rails behind one branded control plane
    • The official GitHub organization is verified for chain.com and still exposes technical lineage such as TxVM plus newer Sequence SDK repositories, reinforcing that the practical operator shell matters more here than any one sub-technology label
  • Whitepaper: No separate company whitepaper is the point here. The strongest primary materials remain the official site, payments/cards/docs surfaces, the Onyx-linked ledger framing, and the verified GitHub organization already collected in ../whitepapers/chain-primary-sources-2026-04-27.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep chain only as an alias so legacy links keep resolving without pretending there is a separate Chain protocol or product layer doing independent analytical work.
  • Keep this note focused on the named operator boundary: enterprise onboarding, wallet and payee admission, sanctions / risk screening, bank funding, fiat-to-USDC conversion, payout routing, and ledger/account truth.
  • That split matters because the real dependency is not how does Chain-as-a-protocol work? but which company controls the easiest bank-to-stablecoin-to-card operating path many enterprise users inherit by default?

Control surface

  • Practical authority sits in customer admission, linked-bank setup, wallet and recipient screening, account-model selection, payout routing, supported fiat / stablecoin coverage, ledger semantics, and webhook / lifecycle truth.

  • Chain matters because those defaults decide who can move money, where they can move it, how risk review is applied, and which settlement rails are exposed as normal.

  • Read it as a company-run stablecoin payments and treasury shell, not as a neutral settlement primitive.

  • Last reviewed: 2026-08-12 UTC