Modern Treasury review

Modern Treasury is a hosted payment-infrastructure API paired with an operations dashboard, not a client library, CLI, or self-hosted server. It sits between a product backend and banks, payment rails, compliance workflows, accounts, and ledgering. The API covers onboarding, account creation, pay-ins and payouts, then operational work such as returns, reconciliation, and reporting. Its pitch is to replace separate bank portals, CSV uploads, and disconnected providers with one integration across fiat and stablecoins. The homepage lists ACH, RTP, FedNow, checks, wire, push-to-card, and stablecoins as money-movement options. Programmatic accounts are backed by a real-time ledger, while onboarding supports KYC, KYB, and screening. For an application team, that means delegating payment infrastructure and operations to a vendor while keeping product logic in your own service. It is a significant architectural dependency: payment availability, account state, and reconciliation become tied to Modern Treasury's API and operating model.

The homepage shows an API request using POST /api/legal_entities with a JSON body and a 201 response, giving developers a concrete HTTP integration surface. The lifecycle it describes runs from onboarding through account creation and payments to operations. Webhooks, returns, reconciliation, and reporting are named as part of that operating layer. Modern Treasury presents one API for payments, accounts, and ledgering, with a dashboard for operations and monitoring. The homepage does not name SDKs, programming languages, a CLI, or plugins. Confirm SDK availability, language support, authentication details, and API versioning in the vendor's documentation before choosing an implementation path. Its example starts with legal-entity onboarding, including business identification fields and a pending status response. The vendor says teams can add payment methods as they grow without rebuilding the integration; verify the specific rail coverage and workflow requirements for your use case.

Modern Treasury has no listed free plan or free trial. Pricing is usage-based, with charges per transaction and rates varying by payment method. The pricing page lists ACH from $0.25 per transaction; RTP/FedNow from 1% plus $0.60, capped at $5; and stablecoin orchestration from 0.30%, with a $0.50 minimum. Each listed option includes one API for payments, accounts, and ledgering, a dashboard for operations and monitoring, and dedicated support from payments experts. These are starting rates, not a complete estimate for a production workload. The vendor says annual terms are available, but publishes no monthly subscription or annualized price. It also does not publish a sample bill, volume tiers, or a complete schedule of other fees. Estimate costs using your expected payment mix and transaction volume, then ask the vendor to confirm applicable terms, minimums, and any additional charges before launch.

Modern Treasury presents a hosted API and dashboard. Its homepage does not publish an open-source license, source-code availability, or a self-hosting option, so teams should confirm those terms with the vendor rather than assume they can run the service themselves. The same applies to data export: the homepage describes ledgering, reconciliation, and reporting, but does not state export formats or migration procedures. This creates a practical lock-in risk even if your own application keeps its business logic separate. Payment workflows, account state, ledger records, and reconciliation depend on the service's API and data model. Before building around it, ask how to retrieve historical transactions and ledger data, which formats are available, and how to transition payment operations to another provider. Also confirm what remains accessible after a contract ends.

The homepage claims 99.99% uptime and $700 billion in payments processed; those are vendor-published figures, not an independent service-level guarantee. Confirm the contractual SLA, incident process, and support response commitments for your account. The homepage does not publish API rate limits, retry guidance, or detailed security controls, so ask for those before designing payment-critical services. The API lifecycle includes webhooks, returns, reconciliation, and reporting, all of which need explicit handling in production workflows. Build for delayed or failed payments and reconcile against the vendor's records rather than treating a successful API response as final settlement. Reddit discussions about Modern Treasury and USDC on Base focus on combining on-chain payments with fiat workflows; commenters see potential in global transfers and payouts, but the discussion does not establish operational performance. Validate rail availability, compliance responsibilities, and stablecoin on- and off-ramp behavior against your jurisdictions and transaction flows.