When a new transaction posts on your Mercury account
Triggers on every debit or credit posting in a Mercury account.
Trigger·Transaction
Integrations · Business bankingConnect Mercury to Well
Import Mercury bank transactions and balances for real-time cash position tracking and automated matching with invoices.
What Well pulls from Mercury
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 |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Mercury → Well
8 triggers from Mercury.
When a wire transfer arrives in Mercury
Captures incoming wires with originator, reference, and value date.
Trigger·TransactionWhen a wire transfer is sent from Mercury
Tracks outbound wires with beneficiary detail and instruction.
Trigger·TransactionWhen an ACH payment clears in Mercury
Picks up cleared ACH credits and debits with the company id reference.
Trigger·TransactionWhen a Mercury card charge posts
Captures debit card transactions with merchant and MCC code.
Trigger·TransactionWhen a check is deposited to Mercury
Tracks check deposits with the payer, amount, and clearing date.
Trigger·TransactionWhen a Mercury account is read
Pulls each Mercury account the workspace holds with its balance, currency, and routing details.
Trigger·AccountWhen a Mercury account's payment details are read
Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched.
Trigger·Payment method
What Well does with your Mercury connection
Connect
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.
Sync
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.
Enrich
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.
Available
Your data from Mercury lands in the workspace as ledger line, customer payment, and vendor expense you can search, chart, and automate.
Questions Mercury unlocks
Ask in plain language. Well answers from your connected Mercury connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Mercury connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Mercury connection…
Connect Mercury in three steps
- 01
Authorise Mercury via MCP
From Well's Connections panel, search for Mercury and click Connect. Well discovers Mercury's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Mercury's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.mercury.com/mcp
- 02
Map your entities
Well's MCP client discovers bank transaction, incoming wire, outgoing payment, and balance from Mercury that Mercury's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Mercury records. Because Mercury ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Mercury records happens in the background. Mercury developer docs.
How Mercury stays secure with Well
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.
OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requestsmcp.mercury.com/mcp
- granted
Read Mercury records
Resources the Mercury MCP server exposes, scoped by your OAuth approval.
- granted
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.
- refused
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.
- refused
Store Mercury passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Disconnect any time from Well settings or Mercury’s admin panel.
Frequently asked questions about Mercury and Well
From Well, open Connections, find Mercury, and click Connect. Well discovers the OAuth metadata at mcp.mercury.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Mercury's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in bank transaction, incoming wire, outgoing payment, and balance from Mercury and reshapes each entity into your workspace: bank transaction becomes ledger line; incoming wire becomes customer payment. Every record arrives with the source identifier preserved, so Mercury stays the source of truth while Well lets you query the data alongside the rest of your stack.
Once Mercury is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Mercury source, so you can always trace a workspace record back to the original.
Every workspace ledger line built from Mercury carries the source bank transaction identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Mercury record; from Mercury, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well combines live Mercury events with periodic reconciliation reads of bank transaction, incoming wire, outgoing payment, and balance. New rows appear within seconds when Mercury pushes them; periodic reads catch anything a push missed. The first connect backfills history from Mercury in the background.
Open Connections > Mercury in Well and click Disconnect. Well calls Mercury's token revocation endpoint and stops calling Mercury immediately on its side; provider-side propagation to Mercury's admin panel varies by provider. The bank transaction, incoming wire, outgoing payment, and balance Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Mercury records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Connect Mercury with
Ready-to-ship workflows that pair Mercury with another tool through Well.
Pennylane
Reconcile Mercury USD transactions inside Well, then forward…
Xero
Match Mercury wires, ACH, and card transactions to invoices…
QuickBooks
Reconcile Mercury transactions inside Well with vendors reso…
Qonto
Reconcile Mercury USD activity against Qonto EUR balances wi…
Freshbooks
Sync Mercury transactions to FreshBooks as expenses or bills…
Pairs well with Mercury
More in Business banking
Anytime
Connect Anytime to Well to sync business bank accounts and transactions.
Blank
Connect Blank to Well to sync business bank accounts and transactions.
Bourso Business
Connect Bourso Business to Well to sync business bank accounts and transactions.
Husk
Connect Husk to Well to sync business bank accounts and transactions.
Popular cross-category
Ready to connect Mercury?
Connect once. Every bank transaction, incoming wire, outgoing payment from Mercury becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.