Aaron Makelky
Back to blog

Field notes

Meow vs Mercury: why my business banking went to Mercury

· 8 min read

Mercury · Meow · Business Banking · AI Agents

I needed a real business bank for my consulting practice. A fractional CFO friend recommended Meow, then admitted he banks at Mercury. Wells Fargo was the incumbent I was trying to escape. So I compared Meow and Mercury properly: the apps, the APIs, the pricing, and what my agents can actually do with each one.

Mercury won as my daily operating account. Meow won as the better idea for how agents should touch money.

The full comparison

API DECISION MEMO Meow vs Mercury
Recommendation

Mercury is the better daily driver.

For a solo consultant prioritizing mobile banking, invoicing, webhooks, and automation, Mercury is the more complete operating setup.

Best overall fit · with a $29.90/mo caveat
CHANGE THE DECISION LENS
MERCURY Native iOS and Android apps, mature receivables, approval alerts, and broad banking APIs make it the stronger everyday operating account.
MEOW Its official MCP can create products, customers, and invoices, manage virtual cards, and draft transfers for human approval. Mercury’s official MCP is read-only.
MEOW Meow has no invoicing-API paywall. Mercury requires Plus at $29.90 per month for Invoices and Customers API access.
THE SHORT VERSION

Choose the workflow, not just the API.

Mercury wins the human layer. Its native mobile apps handle balances, transfers, cards, mobile check deposit, receipts, and pending-approval alerts. Meow wins the agent layer: its official MCP can create invoices, issue or freeze virtual cards, and draft transfers for human approval.

M

Pick Mercury
if the bank account needs to work well from your phone.

W

Pick Meow
if coding-agent write access matters more than a mobile app.

01

Mobile app

Mercury, clearly

Native iOS + Android — Meow has no native app.

02

Webhooks

Both are strong

Signed delivery, retries, and event filtering on both sides.

03

Invoicing API

Meow on access

Both create and track invoices; Mercury requires Plus.

04

Coding agents

Meow, clearly

Official MCP writes invoices and drafts transfers.

HEAD-TO-HEAD

What changes in practice

The two APIs overlap heavily. The decisive differences are mobile access, MCP write capability, and the friction around invoicing and write tokens.

Capability
Meow
Mercury
MobileUse it away from a desk
NO NATIVE APP Web dashboard + agent-first strategy

Meow explicitly positions banking as shifting away from apps toward AI agents.

STRONGEST FIT Native iOS and Android

Balances, transactions, transfers, mobile check deposit, cards, receipt scanning, widgets, and push alerts for pending approvals.

InvoicesCreate, send, track
NO PAYWALL Full Billing API

Products, customers, invoices, line items, PDF downloads, recipient email, multiple payment methods, and lifecycle status.

PLUS REQUIRED Full Accounts Receivable API

Create, send, update, cancel, track, and download PDFs. Requires Mercury Plus at $29.90/month or higher.

Official MCPConnect a coding agent
ACTIONABLE OAuth or API-key surface

Create products, customers, and invoices; issue or manage virtual cards; draft transfers that stay pending until a person approves them.

BETA · READ-ONLY Hosted OAuth connection

Official tools list and inspect accounts, transactions, cards, invoices, customers, and more—but do not create invoices or send money.

REST writesDirect automation
LOWER FRICTION Scoped x-api-key

Full read/write API with about 30 fine-grained scopes. No IP-whitelist requirement.

STATIC IP FRICTION Bearer token + whitelist

Read & Write tokens require IP whitelisting. Custom tokens can expose selected endpoints, but write scopes generally still need a whitelist.

WebhooksTrigger automations
10 TRIES · ~91 HOURS Standard Webhooks format

HMAC-SHA-256, snapshot or thin payloads, test events, delivery history, redrive, secret rotation, and circuit breaking.

10 TRIES · ~1 DAY Filtered event subscriptions

HMAC-SHA-256, event-type and path filters, test verification, and at-least-once delivery. Not available in sandbox.

SandboxBuild without risk
RICH SIMULATION Sandbox + development environments

Simulate inbound transfers, stablecoin funding, card authorization and settlement events, and application approval.

DUMMY DATA Separate sandbox account

Preloaded data and sandbox-only tokens. Use the Events API because webhooks do not run in the sandbox.

API SURFACE

Drill into the details

Open any section for the parts most likely to affect an integration plan.

Accounts, payments, cards & operations

Meow

  • Accounts, balances, transactions, limits, statements, tax documents, contacts, users, reimbursements, and routing-number validation.
  • ACH, scheduled ACH, domestic wire, internal book, international, crypto, and USDC transfer creation.
  • Create, update, and revoke cards; bill-pay CRUD and document upload flows.
  • Business onboarding, representatives, KYC, due diligence, and document uploads are API-accessible.

Mercury

  • Accounts, transactions, statements, recipients, merchants, categories, credit, treasury, users, organization, and SAFEs.
  • Send money to recipients, internal transfers, checks, and domestic wires; manage send-money approval requests.
  • Create, update, cancel, freeze, and unfreeze cards; Vault can reveal card details.
  • Attachments, transaction metadata, statement PDFs, and OAuth2 integration flows.
Authentication & token management

Meow

  • API key in the x-api-key header, created and managed in the dashboard.
  • Fine-grained scopes include invoices, products, customers, transfers, cards, webhooks, bill pay, and simulations.
  • Multi-entity keys add an x-entity-id header. OAuth is reserved for the MCP surface.

Mercury

  • Bearer or basic authentication with Read Only, Read and Write, or Custom token tiers.
  • Write access generally requires IP whitelisting; scopes cannot be edited after creation.
  • Unused tokens are auto-deleted after 45 days; unused permissions can also be auto-downgraded after 45 days, with seven days’ email notice.
Invoice lifecycle & payment methods

Meow

  • Status covers draft, open, pending, scheduled, partially paid, canceled, expired, and overdue.
  • Tracks total, paid, and due amounts; supports invoice dates, due dates, notes, line items, recipient email, and PDF download.
  • Documented payment methods include bank transfer, card, ACH debit, international wire, and several USDC/USDT networks.

Mercury

  • Create, list, get, update, cancel, attach files, download PDF, and send by email at creation.
  • Customer payment methods include credit card, Apple Pay, Google Pay, wire, ACH, and ACH debit for subscribers.
  • Plus adds recurring invoices and ACH-debit invoicing at $1 per transaction.
IMPLEMENTATION PATH

What each choice commits you to

RECOMMENDED

Mercury as the operating account

Best if you want dependable phone access first, then layer automation around it.

  1. Budget $29.90/month for Plus if coding-created invoices are a requirement.
  2. Use the native mobile app for approvals, deposits, cards, receipts, and push alerts.
  3. Connect the official MCP for safe read access; use REST for invoice creation and other writes.
  4. Plan a static-IP or carefully scoped token strategy before giving a coding agent write access.
Best fit for you: the phone remains a first-class control surface while automations handle the repetitive work.
AGENT-FIRST ALTERNATIVE

Meow as the automation account

Best if you want a coding agent to do more through an official integration.

  1. Connect the official MCP with OAuth or a scoped API key.
  2. Let agents create products, customers, invoices, and virtual cards.
  3. Use transfer drafts so payments still require human dashboard approval.
  4. Day-to-day mobile banking centers on the web dashboard.
Best fit for you: if Muse or Codex taking real invoice and card actions outweighs the need for a polished phone app.
SOURCES

Primary sources

Comparison based on product and developer documentation read September 18, 2026. Features, pricing, and access policies can change.

What I actually need from a business bank

I need five things: a mobile app I can run the business from, invoicing I can trigger from my own systems, an API my automations can use, transfers I can track, and a bank that doesn't make my wife drive to a branch to get added to an account.

The branch visit that ended the debate

Wells Fargo made us go in person to get my wife added to a business account. In 2026. Mercury let me add her online, is shipping her a physical card, and sent 25 checks for free.

Wells Fargo treated its process as sacred and my time as worthless. Mercury acted like software. I know which one I want holding my operating cash.

Where Mercury wins: the daily operating account

Mercury is the better bank for the unglamorous daily work. The mobile app is native and actually good, which matters because I run most of my business from my phone. Transfers have real tracking instead of the "it'll show up in 1-3 business days, good luck" experience. Webhooks mean my systems know when money moves without me polling an API like it's 2014.

The invoicing API is the sleeper feature. I can generate and send invoices from my own workflows instead of living inside someone else's dashboard. It requires a Plus plan, which is worth knowing before you build on it.

Mercury's API story has one real wart for my use case: general read and write tokens require IP whitelisting. That's fine for a server with a static IP and annoying for agents running on dynamic infrastructure. Their official MCP was documented as beta and read-only, so don't plan on your agent doing much inside Mercury yet.

Where Meow wins: agent-native money movement

Meow is built around a genuinely better idea for how agents should touch money: the agent prepares transfers and a human approves them. That's the workflow I actually want. I don't want my agent moving money autonomously, and I don't want to be the API either. Human-approved drafts are the setup I want for agent-run finance: the agent drafts, I approve.

The pricing is unusual: no public paid subscription for the core banking and agent offering. The paid parts are gated by balance instead of subscription. Yield and brokerage products need a $100,000 checking balance, and the treasury product runs 1 basis point per month, annualized.

The weak spot is mobile: Meow has no native mobile app, and I run my business from my phone. That is the gap that keeps it from being my daily driver.

The pricing

Mercury is straightforward: a free tier, Plus at $29.90 a month, Pro at $299 a month. The invoicing API needs Plus.

Meow has no public paid subscription for the core offering. The costs show up as balance gates and treasury fees instead. Different model, not necessarily a cheaper one, depending on how much cash you keep parked.

My verdict

Mercury is my operating account. It does the daily work better: mobile, invoices, webhooks, tracking, and a bank that treats my time like it matters. Meow is the one I'm watching. The human-approved transfer draft is how agent-run finance should work. If they ship a real mobile app and keep the agent-approval workflow ahead of Mercury's, I'll take another look.

If you're picking today and you mostly need a bank that works, pick Mercury. If you're building agent workflows that touch money and you want a human in the approval loop by design, Meow deserves a real look.

Disclosure: the Mercury link below is my referral link. It costs you nothing and supports the site. If you'd rather not use it, mercury.com works the same.

Open a Mercury account with my referral link

Common questions about Meow and Mercury

Should I pick Meow or Mercury for my business banking?

I picked Mercury as my daily operating account because of its mobile app, invoicing API, webhooks, and transfer tracking. Meow is the better pick if you want agent-native workflows with human-approved transfer drafts. If you mostly need a bank that just works day to day, I'd start with Mercury.

How much does Mercury cost?

Mercury has a free tier, Plus at $29.90 a month, Pro at $299 a month. The invoicing API requires a Plus plan or higher.

Does Meow charge a subscription?

No. Meow's core banking and agent offering has no public paid subscription. The paid parts are gated by balance instead: yield and brokerage products require a $100,000 checking balance, and the treasury product charges 1 basis point per month, annualized.

Can my AI agents move money with Mercury or Meow?

Meow is built for this: agents can prepare transfers that a human approves. Mercury's official MCP was documented as beta and read-only, and its general read/write API tokens require IP whitelisting, which is friction for agents running on dynamic infrastructure. For agent-driven money movement with a human in the loop, Meow has the better model right now.

Did you really have to visit a branch to add your wife to Wells Fargo?

Yes. Wells Fargo required an in-person visit to add my wife to a business account. Mercury let me add her online, shipped her a physical card, and sent 25 checks for free. That single experience told me more about the two banks than any feature table.