Mercury Bank
Pay a contractor, issue an invoice, read the ledger — from your business bank account, inside your limits.
You paste an API token from Mercury; a token alone moves nothing. Your policy sets the most per payment and per 30 days, the payees and rails, and Mercury’s own approval rules still apply on top.
The owner’s policy
Stored as MERCURY_POLICY, checked inside the enclave before any request leaves. With nothing stored: read-only — the agent can look at accounts, payees, the ledger and invoices, and cannot pay, add a payee or send an invoice.
How much may it pay?
max_payment_usdMost per paymenta number, USD, whole dollars- The largest single payment. Payments are off until BOTH this and the 30-day budget are set — one without the other allows nothing. Empty: no payments at all.
max_spend_usd_monthBudget per 30 daysa number, USD, rolling 30 days- What the agent paid in the last 30 days, counted from Mercury’s own ledger, plus payments waiting for approval. Only the agent’s own payments count, unless you tick "Count every payment from the account" below. A payment that would cross it is refused. Empty: no payments at all.
To whom?
allowed_recipientsOnly these payeesa list- Mercury recipient ids, as the connector’s recipients operation lists them. With a list here the agent can never add a payee, whatever the switch below says. Empty: any payee already saved in Mercury.
allow_new_recipientsAdd new payeeson or off- Lets the agent save a payee from account and routing numbers it was given, and pay it. Off, it pays only payees already saved in Mercury by you. Off: only payees already saved in Mercury.
How?
payment_methodsRailsa set of choices- The connector uses only what is ticked. A wire is expensive and cannot be recalled, so it is never on unless you tick it. Nothing ticked: ACH only.
account_idAccount numbertext- The account the agent may use — and the only one, when set: reads, payments and invoices all run against it. It is the account number shown in your Mercury dashboard, a number like 12345678901. Not sure which? Leave it empty and ask your agent which accounts it sees; it can tell you their names and last four digits. Empty: with a single account on the login, that account. With several, the agent can read any of them and no payment runs.
Off unless you say so
allow_invoicingIssue and cancel invoiceson or off- send_invoice creates a real Mercury invoice and Mercury emails it to the customer under your company’s name; cancel_invoice cannot be undone. Rendering an invoice document needs no switch. Off: the agent can read invoices and render a document, and cannot send or cancel one.
count_all_outgoingCount every payment from the accounton or off- Off, the 30-day budget counts only the payments the agent made. On, it counts every payment leaving the account, the ones you and your team make included, so a busy month leaves the agent less. Off: only the agent’s own payments count toward the budget.
sandboxSandbox tokenon or off- Tick it when the token was created at sandbox.mercury.com — Mercury’s test bank, with its own login and simulated money. Calls then go to Mercury’s sandbox API. Nothing else changes: the limits above are checked the same way. A token and this switch that disagree are answered by Mercury with 401. Off: the token is a production one, and payments move real money.
What may it do?
allowed_operationsOperationsa set of choices- When anything is ticked, the agent may run only that — reads included — and status always answers. An operation added to the connector later is NOT included until you tick it. Nothing ticked: every operation, subject to the rules above.
rulesRulesrules- For a write the rest of the policy allows: run it, wait for your yes, or refuse it. Checked top to bottom — the first rule that matches decides; with none matching, the write runs. A rule never lets through what the limits refuse. A write that waits is prepared and shown to you whole in your inbox, and nothing happens at the bank until you approve it with one signature. No rules: every allowed write runs without asking.
Auto-approve: the agent runs it within the limits below. Manual approval: it is prepared, shown to you in your inbox, and made on your yes. Unticked: it does not run. Rules with conditions — from an amount, by a rail, to a new payee — go under the table. A group’s name turns the whole group on or off.
Operations
Every call names one in operation; the other fields are the parameters listed under it.
Reading the deployed version…