Modern Treasury is payment operations infrastructure: one API and dashboard to send ACH, wire, RTP, FedNow, push-to-card, check and stablecoin payments, keep a ledger and reconcile bank activity, for finance and engineering teams that run payments in their own product or at volume.
Independently scored, one dimension at a time. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
Rails cover same-day and next-day ACH, wires, RTP, FedNow, push-to-card over Visa Direct and Mastercard Send, printed and digital checks with Positive Pay and stop payments, and USDG, USDC, PYUSD and USDT stablecoins (docs and press releases, 2026). With your own bank it also sends SWIFT, SEPA, BECS, CHAPS and Canadian EFT, and the FX docs say bank FX rates carry no Modern Treasury markup. There are no virtual card payments to vendors, so no rebates.
The homepage cites $600 billion in payments processed (vendor figure), and the API allows 100 requests a second in production (rate limits doc, updated 3 March 2026). Customers can combine the PSP with direct connections at 21 listed banks, and Ledgers nests millions of accounts in up to five levels. The ceiling is geography: the PSP covers US rails and stablecoins, with SWIFT marked coming soon, so international bank rails need your own bank.
The service level agreement (version 9 April 2024) promises 99.9 percent availability with credits of 5 to 25 percent, and targets a first response under 2 business hours for urgent incidents. Those targets apply Monday to Friday, 6am to 6pm PT, and the docs support page lists email only. Capterra shows 4.7 of 5 for customer service on 14 reviews (checked 27 September 2026); G2 blocked automated access.
Approval rules for payments and bank accounts support sequential chains, block the last user who created or edited a payment from approving it, and log every review in the audit trail (approval rules docs, updated 1 June 2026). The security page lists SOC 1 Type II, SOC 2 Type II and PCI DSS 4.0. The pricing page says Modern Treasury handles transaction monitoring, AML checks and sanctions screening, and lists KYB and KYC as included while its own FAQ lists them as compliance costs the customer incurs. The current docs show no PO matching, W-9 or 1099 handling, or e-invoicing (checked 27 September 2026).
In-product AI is modest: Reconciliation Suggestions (announced 23 October 2023) proposes matches for a person when rules cannot reach certainty, and an AI agent and workspace announced on 1 May 2025 as early access has no product page as of 27 September 2026. A first-party local MCP server (npm modern-treasury-mcp 4.21.0, 4 September 2026) and a ReadMe docs MCP read and write through the API with an API key. There is no OAuth connector and no API call to approve a payment.
The vendor says PSP customers go live in days, and its case studies cite Navan live on a first bank in under 2 weeks and Capchase after a one-month implementation. Embedded and automated flows need developer work against the sandbox, though the dashboard also supports single payments and CSV uploads of up to 1,000 payment orders, and a bring-your-own-bank setup depends on bank onboarding that the February 2026 launch release puts at 6 to 12 months. Enterprise builds can add Professional Services (launched 28 March 2024) or partner Blankfactor (announced 24 April 2025).
On 27 September 2026 the pricing page was running an A/B test: about half of loads showed a $2,000 a month starting platform fee, ACH from $0.25, RTP and FedNow from 1 percent plus $0.60, and stablecoin orchestration from 0.30 percent with a $0.50 minimum, and the rest showed no prices. Wires, checks, push-to-card and Ledgers are unpriced, terms are annual with a minimum commitment, and neither Vendr nor SpendHound has a public page for the vendor. The customer agreement prices renewals at then-current rates regardless of earlier discounts. The score sits below vendors that show an entry price to every visitor, because the price strip was an A/B test on 27 September 2026.
The current docs document no native ERP connector (checked 27 September 2026); a QuickBooks sync announced on 12 November 2019 no longer appears. Journal Reports turn transactions or expected payments into balanced journal entries described as suitable for export to an ERP, and categorization rules can stamp GL codes into transaction metadata. Push to Warehouse feeds destinations such as BigQuery and Databricks, but only in select contracts.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
You are buying payment infrastructure that your engineers build on. Modern Treasury sends ACH, wires, RTP, FedNow, push-to-card, printed and digital checks and stablecoins through one API, records every payment in a double-entry ledger, and reconciles bank transactions against expected payments with rules. You can run on its own payment service provider, launched 18 February 2026, or connect your own accounts at banks on its integrations list, which names 21. It holds SOC 1 Type II, SOC 2 Type II and PCI DSS 4.0, and payment approval rules stop the last person who created or edited a payment from approving it.
The catch for an AP buyer is scope. The current docs show no invoice capture, no PO matching, no W-9 or 1099 handling and no vendor bill inbox; the Invoices API bills your customers. There is no documented NetSuite, Sage Intacct or QuickBooks connector: Journal Reports produce entries for export, and Push to Warehouse comes only in select contracts. Pricing starts at $2,000 a month on an annual term with a minimum commitment, per a price strip the pricing page showed on about half of loads in an A/B test on 27 September 2026, and the listed RTP and FedNow rate of 1 percent plus $0.60 gets expensive on large vendor payments unless it is capped. Support response targets run Monday to Friday, 6am to 6pm PT.
Before signing, get in writing: the full per-rail fee schedule, including wires, checks and push-to-card, and a cap on the percentage RTP fee; the size of the minimum commitment and what counts toward it; a renewal cap, since the standard agreement renews for 12 months at then-current rates regardless of earlier discounts unless you give 30 days' notice; whether Push to Warehouse and Ledgers are in your order; and an exit export window, because the agreement promises data export only during the order term. If your AP team needs invoice intake and bill approvals, price an AP tool alongside it.
Jobs, mapped to how finance teams actually buy.
Navan pays employee reimbursements through the payments API, links employee bank accounts through the counterparties API and shows status with webhooks, across six methods including ACH, wire, SEPA and BACS. Procore built Procore Pay on the same Payments and Ledgers products. Your engineers own the build.
AvidXchange uses the single API to manage several bank integrations for AvidPay, for redundancy and to add rails as they arrive. This is the clearest AP use: Modern Treasury moves and tracks the money while the AP product handles invoices and approvals. A finance team buying AP software may already use it indirectly through its AP vendor.
Expected payments and reconciliation rules match incoming transactions to what you expect, and categorization rules can stamp GL codes into metadata. When rules cannot match with certainty, Reconciliation Suggestions proposes candidates for a person to confirm. Journal Reports can then turn matched activity into balanced entries for export to the ERP.
The Ledgers API records double-entry transactions for wallets, FBO and omnibus accounts, with balance locking to prevent overdrafts and monitors that fire webhooks at set thresholds. ClassPass uses it to track studio balances before payouts. Since 1 June 2026, ledger transactions cannot be backdated more than one year.
Printed checks are mailed, and digital checks arrive as PDFs the recipient can deposit by mobile. Both carry automatic stop payments, Positive Pay and custom logos. Checks run through the same ledger and reconciliation as electronic payments, at rates the pricing page does not publish.
Forget the 40-row feature grid. Pick a finance workflow and see how this tool and its closest peers actually do it, with our verdict on who wins for whom.
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
One API for payments, accounts and ledgering, the operations dashboard, infrastructure and dedicated support. Annual term; all fees count toward a minimum commitment.
Usage fee per ACH payment; the rate falls with volume, per the pricing FAQ.
Usage fee per instant payment. No cap is shown, so large payments cost more.
Conversion fee between USD and stablecoins; on-ramps and off-ramps also pay the fiat rail fee.
Listed as usage-priced on the pricing page with no rates.
Sold in usage tiers per the pricing FAQ; no tier prices are shown.
Scheduled sync of Modern Treasury data to a warehouse such as BigQuery, Databricks or Postgres; the docs say it is included only in select contracts.
The pricing page lists KYB and KYC for end users, transaction monitoring and compliance operations under what is included, while its own FAQ lists KYB and KYC as compliance costs you incur (checked 27 September 2026). Ask which applies and at what rate.
Implementation guidance, premium support and custom integrations for enterprise customers, launched 28 March 2024.
The payments and platform docs indexes, checked 27 September 2026, cover payment orders, counterparties, reconciliation, ledgers and approval rules for payments and bank accounts, with nothing for capturing vendor invoices, matching them to POs or collecting W-9s. The Invoices API creates receivables invoices that your customers pay. For AP automation, Modern Treasury covers the payment step only, and you still need an AP tool or your own build for everything before it.
A 12 November 2019 post announced a two-way QuickBooks sync, with Xero, NetSuite and Workday planned, but the current docs (checked 27 September 2026) document no ERP connector, and the old continuous accounting page now redirects to the Payments page. Journal Reports (docs updated 15 January 2026) build balanced journal entries described as suitable for export to an ERP. Push to Warehouse syncs data to destinations such as BigQuery, Databricks and Postgres, but only in select contracts, and its docs say it is not for critical-path work. Budget for your own GL integration.
The pricing page (checked 27 September 2026) lists ACH from $0.25 and RTP or FedNow from 1 percent plus $0.60. On vendor payments of tens of thousands of dollars an uncapped percentage adds up: a $50,000 payment would cost about $500.60 at the starting rate (Audit Friendly estimate). Wire, check and push-to-card rates are not published at all. Negotiate a cap or a flat instant fee, and model your payment mix by rail before signing.
Under the customer agreement for orders from 30 January 2025, each order renews for successive 12-month periods unless either party gives notice at least 30 days before the term ends. Renewal fees are at then-current rates regardless of discounted pricing in a prior order, fees are non-refundable, and late invoices accrue 1.5 percent a month. Data export is promised only during the order term, and access ends at termination. Put a renewal cap and an exit export window in the order form.
For the PSP, the Payments product page lists SWIFT as coming soon, and the docs say virtual accounts are not available when Modern Treasury acts as your payment service provider. With your own bank, the 9 July 2026 release notes cover SWIFT, SEPA, BECS and CHAPS, the docs cover Canadian EFT, and settlement timing follows your bank's cutoffs. Decide which model you are buying, and ask how the published fees apply if you bring your own bank.
The SLA (version 9 April 2024) targets a first response under 2 business hours for urgent incidents, such as being unable to initiate a payment, and under 4 business hours for delayed payments. Those clocks run only in business hours, and the docs support page lists an email address. RTP and FedNow run around the clock, so ask what coverage applies at night and on weekends before you move payouts to instant rails.
Scored on what an outside agent can actually reach: the documented API, how it authenticates, and whether the vendor ships an MCP server.
In-product AI is limited and partly unconfirmed. Reconciliation Suggestions, announced 23 October 2023, proposes matches when the deterministic reconciliation engine cannot reach certainty, and a person decides; the customer agreement calls these optional suggestions the customer must evaluate. Modern Treasury AI, an agent for payment ops questions plus a workspace that watches for anomalies such as duplicate payments, was announced on 1 May 2025 as early access with general availability planned for later that year. No product page or documentation for it was found on 27 September 2026, so treat it as unconfirmed. The Bank Operations Agent described on 24 July 2026 is an internal support tool.
Exists: yes, two first-party servers. The TypeScript SDK ships a local MCP server on npm as modern-treasury-mcp, announced 11 April 2025 and at version 4.21.0 on 4 September 2026. The ReadMe docs portal hosts a second server at docs.moderntreasury.com/mcp (page updated 6 May 2026). Neither is listed in the official MCP registry, where the only Modern Treasury entry is a third-party server from usefulapi.io, and neither appears in Claude's connector directory.
Scope: read and write. The npm server offers a docs search tool and an execute tool that runs agent-written TypeScript against the full SDK in a local Deno sandbox, with network access limited to the API host. The docs server offers list, get and search tools plus execute-request over 197 operations in its main spec, which names the production host app.moderntreasury.com/api (listed 27 September 2026). Both can create payment orders, counterparties, expected payments and ledger entries. Neither can approve a payment: the API can only cancel a payment order or send it back to needs_approval.
Turnkey: no. Both need an organization ID and API key over basic auth, and there is no OAuth sign-in. The npm server also needs Node and Deno on the user's machine. API keys can be limited to selected permissions when created, which is the safer way to hand one to an agent, since the server's own method blocking is plain string matching.
Who wins for whom: Engineering-led teams that capture and approve invoices elsewhere and want payment approval chains that block self-approval: Modern Treasury. NetSuite teams paying in USD that want PO matching and unlimited approval levels: Routable. Payers collecting W-8 forms, 1042-S data or VAT IDs abroad: Tipalti.
Payment approvals, no invoice workflow. Modern Treasury captures no invoices: payment approval rules run sequential chains, block the last user who created or edited a payment from approving it, and log each review, with SOC 1 and SOC 2 Type II listed.
Where it loses: Invoice capture, PO matching, bill approval, W-9 and 1099 handling and e-invoicing are all absent from current docs, so an AP tool or in-house build must handle everything before payment.
Source: AF score rationale: Compliance depth 70; Modern Treasury watch-outs.
Watch: Modern Treasury Payments: One API for Fiat and Stablecoins 1:51 · Official demo · Modern Treasury on YouTube (official)
Approvals and NetSuite PO matching. Routable runs unlimited approval levels and rules, matches bill lines to NetSuite PO lines 2 and 3 way with tolerances and holds payment on discrepancies, and carries SOC 1 and SOC 2 Type II reports.
Where it loses: PO matching covers only NetSuite POs in USD and is an add-on on Scale, while OFAC, TIN and bank ownership checks are add-ons below Enterprise and e-invoicing is absent.
Source: AF score rationale: Compliance depth 74; Routable pricing tiers and watch-outs.
Watch: The Most Flexible Bill Pay Platform for Mass Payouts 3:02 · Official demo · Routable on YouTube (official)
Tax forms and screening built in. Tipalti captures W-9 and W-8 forms with TIN matching, prepares 1099 and 1042-S reports, screens payees against OFAC and Do Not Pay before each payment, and matches invoices 2 and 3-way at header and line level.
Where it loses: Per-invoice fees are quote only above the $99 monthly entry price, and the services agreement promises a data download only during the term, while supplier tax forms and audit trails live in Tipalti.
Source: AF score rationale: Compliance depth 90; Tipalti pricing tiers and watch-outs.
Watch: Accounts Payable AI: Automate Invoices with Tipalti AI 1:37 · Official short · Tipalti on YouTube (official)
Who wins for whom: Engineering teams building payments into their own product that want ACH, wires, RTP, FedNow, checks and stablecoins behind one API: Modern Treasury. Platforms paying drivers or contractors instantly over RTP and FedNow: Routable. Payers with suppliers in 200+ countries who want 25 currencies held and converted in one place: Tipalti.
Bank rails through one API. One API sends same-day and next-day ACH, wires, RTP, FedNow, push-to-card, printed and digital checks with Positive Pay, and stablecoins, while a customer's own bank adds SWIFT, SEPA, BECS, CHAPS and Canadian EFT with no Modern Treasury FX markup.
Where it loses: There are no vendor virtual cards or rebates, RTP and FedNow start at 1 percent plus $0.60 a payment with no published cap, and wire, check and push-to-card rates are unpublished.
Source: AF score rationale: Payments & money movement 90; Modern Treasury pricing tiers and watch-outs.
Watch: Unlock the Power of Faster Payments with Modern Treasury 3:09 · Official demo · Modern Treasury on YouTube (official)
Instant, ACH, check and local rails. Routable pays over four ACH speeds, RTP and FedNow to 85 to 90 percent of US bank accounts, push to debit card, 11 check options, and local rails or SWIFT to 220+ countries.
Where it loses: There are no virtual cards or card rebates, per-payment fees are quote only, and the terms auto-enroll every client in an Instant Pay loan facility unless it opts out.
Source: AF score rationale: Payments & money movement 84; Routable watch-outs.
Watch: Sending Payments via CSV Upload with Routable 0:55 · Official demo · Routable on YouTube (official)
Licensed global payouts, 200+ countries. Tipalti moves money itself by ACH, global ACH, SEPA, wire, check, PayPal and cashback virtual cards to 200+ countries, holding and converting 25 currencies under US and Canadian money transmitter and UK and EU e-money licenses.
Where it loses: Per-payment and FX conversion fees are quote only, the card cashback rate is not published, and Tipalti can draw its fees from the account that funds payee payments.
Source: AF score rationale: Payments & money movement 93; Tipalti watch-outs.
Watch: Whats New in Tipalti Accounts Payable | December 2025 1:46 · Official demo · Tipalti on YouTube (official)
Wallets built with Turnkey join Global USD Accounts and stablecoin orchestration under one API, for users in the US and 90+ countries.
Checks joined the unified payments API with automatic stop payments, Positive Pay and custom logos, using the same ledger and reconciliation as other rails.
Customers can open payment accounts and pay over ACH, wire, RTP, FedNow, push-to-card and stablecoins without their own bank partner, with KYC and KYB handled by Modern Treasury.
Beam's founder joined as Head of Beam and its stablecoin orchestration folded into the platform; Fortune reported an all-stock deal worth about $40 million.
An AI agent for payment ops questions and a workspace with anomaly monitoring were announced for early access, with general availability planned later in 2025; no product page was found by 27 September 2026.
A local MCP server generated from the TypeScript SDK exposes the API to MCP clients such as Claude Desktop; it is published on npm as modern-treasury-mcp.
The pricing page (checked 27 September 2026) shows prices only in an A/B test, on about half of page loads. Where shown, it lists a platform fee starting at $2,000 a month on annual terms, plus usage: ACH from $0.25 a payment, RTP and FedNow from 1 percent plus $0.60, and stablecoin orchestration from 0.30 percent with a $0.50 minimum. All fees count toward a minimum commitment, so plan on at least $24,000 a year before usage (Audit Friendly estimate).
Wire, check, push-to-card and Ledgers pricing is not published, and no public benchmark such as Vendr lists the vendor. The FAQ says per-unit costs fall as volume grows, so bring a 12-month payment mix by rail to the first call.
Under the customer agreement for orders from 30 January 2025, orders renew for 12 months unless either side gives 30 days' notice, renewals are priced at then-current rates regardless of earlier discounts, fees are non-refundable, and liability is capped at 12 months of fees. The SLA promises 99.9 percent availability, with service credits of 5 to 25 percent.
The agreement lets you export data with the product's export features during the order term; access ends at termination, and data is deleted on request. Audit logs can be bulk exported from the dashboard, the API lists every object, and Push to Warehouse keeps a copy in your warehouse where the contract includes it. Plan the export before the term ends.
Modern Treasury says PSP customers can build in the sandbox, pass KYB and start sending payments within days. Its case studies cite Navan live on its first bank in under 2 weeks and Capchase after a one-month implementation. Bringing your own bank adds that bank's onboarding, which the vendor's February 2026 launch release puts at 6 to 12 months for new bank relationships.
Your engineers build the integration; the controller or treasury lead sets approval rules, reconciliation rules and GL coding. Enterprise customers can buy Professional Services, launched 28 March 2024, and Modern Treasury uses Blankfactor, a Globant subsidiary, for repeat integrations (announced 24 April 2025).
Yes, through a developer setup. The TypeScript SDK ships a first-party MCP server on npm (modern-treasury-mcp, version 4.21.0 on 4 September 2026) that runs locally and lets an agent write SDK code against the full API, and the docs portal hosts a second MCP at docs.moderntreasury.com/mcp that can call 197 API operations on the production host. Both can read and create payment orders, counterparties, expected payments and ledger entries.
Neither is turnkey. Both need an organization ID and API key, with no OAuth sign-in, and neither is in the official MCP registry or Claude's connector directory. An agent cannot approve a payment, because the API can only cancel a payment order or send it back for approval. Give the agent a key restricted to the objects it needs, and keep approval rules on.
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.