Modern Treasury

• Name: Modern Treasury
• URL: https://www.moderntreasury.com/
• Category: fiat-and-stablecoin payments control-plane company / programmable treasury infrastructure / crypto-adjacent PSP operator
• Tags: ethereum-ecosystem
• Summary: Modern Treasury belongs in companies/, not just projects/, because the durable dependency is a named operator packaging onboarding, programmable accounts, payment approvals, ledger truth, compliance workflow, fiat↔stablecoin conversion, and reconciliation inside one hosted shell. The useful question is not only what stablecoin API does Modern Treasury expose? but which company controls the account model, rail access, conversion workflow, reporting truth, and operational boundary customers inherit?
• What it does:
  • Operates a payments platform and PSP layer for launching money-movement products with one API across ACH, wire, RTP/FedNow, push-to-card, and stablecoin rails
  • Lets platforms onboard users with KYC/KYB checks, programmatically open payment accounts, and manage balances and transaction history through a unified ledgered system
  • Markets Stablecoin Payment Accounts as USD-backed accounts that can send and receive over ACH, wire, RTP, and stablecoin rails through the same API surface
  • Packages wallet provisioning and screening, USD↔stablecoin conversion, approvals, reporting, and auto-reconciliation as one shared operator workflow rather than as separate neutral rails
  • Positions the stack so customers can start inside Modern Treasury’s integrated PSP shell and later add direct bank partners without replacing the integration
• Key claims:
  • The homepage says Modern Treasury offers one API for multi-rail payments, programmable accounts, real-time reporting, and built-in compliance, and explicitly markets One Platform For Fiat and Stablecoins
  • The homepage and product materials claim more than $400 billion in payments processed and 99.99% uptime, framing the stack as production infrastructure rather than an experimental crypto sidecar
  • The stablecoin product page says customers can send, receive, and manage stablecoin payments using the same infrastructure they use for fiat without managing wallets, liquidity, or blockchain complexity
  • That same page lists onboarding, wallet provisioning and screening, USD↔stablecoin conversions, auto-reconciliation, and a shared payment-ops dashboard, which is strong evidence that the real surface is a company-run operations shell rather than a narrow API wrapper
  • The Stablecoin Payment Accounts launch post says companies can use one API to send and receive over ACH, wire, RTP, and stablecoin rails with automatic conversion between USD and stablecoins
  • The February 2026 payments launch materials say customers can start with the PSP and add direct bank partners later without replacing the integration, which makes the vendor boundary itself part of the operational lock-in story
  • The same materials highlight partnerships with Paxos, the Global Dollar Network, and Circle Alliance participation, which is useful evidence that Modern Treasury is actively packaging stablecoin distribution and settlement rather than only discussing it conceptually
• Whitepaper: No canonical standalone company whitepaper or litepaper surfaced in this pass. The clearest primary materials are the official homepage, stablecoin product page, stablecoin launch post, and payments press release; the primary-source bundle remains ../whitepapers/modern-treasury-primary-sources-2026-05-03.md.
• Sources:
  • https://www.moderntreasury.com/
  • https://www.moderntreasury.com/products/stablecoins
  • https://www.moderntreasury.com/journal/announcing-stablecoin-payment-accounts
  • https://www.moderntreasury.com/newsroom/press-releases/modern-treasury-launches-payments
  • https://www.moderntreasury.com/learn/what-is-a-stablecoin-api

Internal linkages

• Project-layer alias note: modern-treasury.
• Useful adjacent company reads: openpayd, bridge-xyz, stripe, and bvnk.
• Lower-layer contrast where the question becomes payment-initiation or interoperability standards rather than one regulated operator shell: open-payments.

Protocol / company boundary

• Modern Treasury does not read like a neutral protocol or standalone network whose deployed mechanics explain the main dependency.
• The analytically important surface is the company-run operating shell that packages partner onboarding, account issuance, ledger truth, approval workflow, fiat and stablecoin rail access, conversion handling, reconciliation, reporting, and lifecycle publication inside one inherited vendor environment.
• That is why Modern Treasury belongs in companies/: the real leverage sits with the named operator that controls the workflow graph and service boundary, not with an abstract stablecoin API label.

Control surface

• Practical authority sits in onboarding approval, account issuance, balance and ledger truth, stablecoin wallet provisioning and screening, fiat↔stablecoin conversion, payment approvals, rail support, reconciliation, reporting, and which lifecycle events customers treat as authoritative.

• The sticky dependency is workflow memory: once a platform builds around Modern Treasury-managed accounts, approvals, conversion logic, reporting, and payment-ops state, the lock-in is to the company-run operational shell rather than to a generic settlement primitive.

• Read Modern Treasury as a hosted operator boundary first. The API is distribution; the real control surface is the company shell behind account, compliance, and settlement workflow.

• Last reviewed: 2026-08-10 UTC