Forward a cleared Mercury payment to Melio
Well reads each Mercury debit, resolves the vendor, and forwards a document to your Melio email-in address so the payment can be matched to the scheduled bill.
Pair Mercury statement activity with Melio bills inside Well so duplicate-debit signals fire before a second hit reaches the bank.
The Mercury integration connects your startup banking to Well via MCP, pulling transactions, balances, and counterparty data into your workspace.
The Melio connection delivers extracted bills into Melio through its Pay Bills email address.
Melio is where bills get scheduled and paid, but the money actually leaves through Mercury, and nobody wants to cross-check by hand which debit cleared which bill.
Well reads the transactions, accounts, and counterparties from Mercury, resolves the vendor behind each payment, and forwards a document to your Melio email-in address. Your team sees the payment with its vendor already matched, so a cleared Mercury debit lines up against the right bill instead of sitting as an unlabelled bank line.
Well reads each Mercury debit, resolves the vendor, and forwards a document to your Melio email-in address so the payment can be matched to the scheduled bill.
Well matches the Mercury counterparty to its company record so the payment reaches Melio naming a real vendor, not a raw bank descriptor.
The Mercury transaction stays attached to the document forwarded to Melio, so a bill payment traces to the exact debit that cleared it.
Pulls from the Mercury transactions API. Pulls each Mercury account the workspace holds with its balance, currency, and routing details.
Pulls from the Mercury transactions API. Picks up cleared ACH credits and debits with the company id reference.
Pulls from the Mercury transactions API. Tracks check deposits with the payer, amount, and clearing date.
Pulls from the Mercury transactions API. Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched.
Pulls from the Mercury transactions API. Triggers on every debit or credit posting in a Mercury account.
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code.
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date.
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction.
Driven by Mercury transaction events. The forwarded PDF is stored on the bill in your Melio inbox.
5 fields flow from Mercury into Melio.
| Mercury field | Label | Melio field | Label | |
|---|---|---|---|---|
| transaction.amount | Amount | amount | Amount | |
| transaction.currency | Currency | currency | Currency | |
| transaction.posted_at | Posted date | scheduled_for | Payment date | |
| transaction.bank_description | Description | reference | Reference | |
| transaction.id | Transaction id | payment_id | Payment id |
Click Connect with Mercury; Mercury's MCP server handles authorisation through Dynamic Client Registration. Mercury's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
Well discovers Mercury's transactions, wires, ACH transfers, card payments, and counterparty records and the the Melio Bills Inbox awaiting payment scheduling. The first batch of bank lines flows into the review queue alongside candidate scheduled payments; once you confirm the rule, Mercury debits auto-link above 85% confidence.
In Melio, open Settings > Integrations and generate an API token with payment-write scope. Paste the key into Well; Melio's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
Well connects to Mercury through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Mercury secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Mercury and Melio host theirs.
Read Mercury records
Scoped to transactions, wires, ACH transfers, card payments, and related records. No access to anything else in your Mercury account.
Deliver documents to your Melio inbox
Well forwards the extracted document to your Melio email-in address; Melio reads bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture from it and you review and post. No write credential to Melio is requested.
Modify or delete Mercury records
Not granted. Mercury is read-only on Well's side; the source of truth never moves.
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
Link both tools to Well so every cleared Mercury payment reaches Melio matched to the right vendor.
Other ways to connect Mercury or Melio through Well.

Mercury
See the Mercury connector

Melio
See the Melio connector


Mercury → Pennylane
Reconcile Mercury USD transactions inside Well, then forward…


Mercury → Xero
Match Mercury wires, ACH, and card transactions to invoices…


Square → Melio
Route Square purchase activity into Melio for vendor payment…

iBanFirst
See the iBanFirst connector

Plaid
See the Plaid connector

Bill.com
See the Bill.com connector