When a new transaction posts on your Mercury account
Triggers on every debit or credit posting in a Mercury account.
Import Mercury bank transactions and balances for real-time cash position tracking and automated matching with invoices.
Mercury feeds bank transaction, incoming wire, outgoing payment into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Mercury’s access.
| From Mercury | In Well | Relation | |
|---|---|---|---|
| Bank transaction | Ledger line | Becomes | |
| Incoming wire | Customer payment | Matches | |
| Outgoing payment | Vendor expense | Categorizes as | |
| Balance | Cash position | Feeds |
Triggers on every debit or credit posting in a Mercury account.
Captures incoming wires with originator, reference, and value date.
Tracks outbound wires with beneficiary detail and instruction.
Picks up cleared ACH credits and debits with the company id reference.
Captures debit card transactions with merchant and MCC code.
Tracks check deposits with the payer, amount, and clearing date.
Pulls each Mercury account the workspace holds with its balance, currency, and routing details.
Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched.
Connect Mercury over OAuth (MCP DCR): Well registers a client through Mercury's OAuth Dynamic Client Registration and you approve on Mercury's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Well brings bank transaction, incoming wire, and outgoing payment in from Mercury on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Well resolves each Mercury entity into ledger line, customer payment, and vendor expense, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Your data from Mercury lands in the workspace as ledger line, customer payment, and vendor expense you can search, chart, and automate.
Ask in plain language. Well answers from your connected Mercury connection, resolved against the rest of your stack.
Ask anything about your Mercury connection
Ask about your Mercury connection…
Each one answers a question from live Mercury data. The required ones return nothing until a source like it is connected.
Needs a source like Mercury
Know exactly how many months and days of cash you have left.
Know exactly how much cash you have, and which accounts it came from.
Find what payment settled an invoice, or catch every payment that never got one.
Know what you actually spend each month, averaged over real months.
See where your cash lands if nothing new comes in.
See the bridge from last month's balance to this one.
See which suppliers owe you paperwork, before your accountant asks.
Put a name on every settled expense that still has no invoice.
Walk the whole month-end sweep in one prompt.
Drive the month-end close to the point of approval.
Close the category gaps behind your spend before you close a month.
Answers better with Mercury
See where your company's money actually goes, no spreadsheets required.
See exactly what's coming due, in what order, and how much cash it adds up to.
See how much of your cash and receivables sit outside your home currency.
Find the bills with no paperwork attached, before an auditor does.
See exactly which agents would run, before any of them does.
Turn mixed currencies into one number you can actually audit.
Connects and checks Mercury
Authorize Well to access your Mercury account through the secure connection screen.
Confirm the connection to allow Well to retrieve your accounts, transactions, and payment means.
Verify that your Mercury transactions and transfers are appearing correctly in your Well workspace.
Your Mercury credentials are never stored by Well, and all data retrieval is read-only. Mercury developer docs.
Well connects to Mercury's MCP server (mcp.mercury.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Mercury secret. Tokens are scoped to the bank transaction, incoming wire, outgoing payment, and balance Mercury exposes and refreshed server-side. Reads only, Well cannot modify or delete Mercury records.
Read Mercury records
Resources the Mercury MCP server exposes, scoped by your OAuth approval.
Resolve bank transaction, incoming wire, outgoing payment, and balance across your stack
Match identifiers in Mercury against the same entities your other connected tools expose, so each record carries cross-tool context.
Modify or delete Mercury records
Not granted; Mercury is read-only in Well. Write-back is opt-in per connector when a write surface exists.
Store Mercury passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Well connects to your Mercury account via the Mercury MCP server to pull transactions, accounts, and payment details into your workspace.
No. Well reads your transaction and transfer data to build journal entries in your Well ledger, but it does not write data, send payments, or upload receipts back to Mercury.
Well retrieves information about your company, accounts, transactions, payment means, and the people associated with your account.
Well syncs with Mercury in the background to ensure your workspace has the latest transactions and transfers ready for reconciliation.
Ready-to-ship workflows that pair Mercury with another tool through Well.
Popular pairs
More in Business banking
iBanFirst
Connect iBanFirst to Well to sync business bank accounts and transactions.
Plaid
Connect Plaid to Well to sync business bank accounts and transactions.
Qonto
Connect Qonto to Well to sync business bank accounts and transactions.
Wise
Connect Wise to Well to sync business bank accounts and transactions.
Popular cross-category
Connect once. Every bank transaction, incoming wire, outgoing payment from Mercury becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.