How often does Mercury data sync to Ramp?

Mercury pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

How does Well match Mercury records to entries in Ramp?

Well scores every candidate match between Mercury records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

What happens to historical Mercury data when I first connect to Ramp?

Mercury exposes the last three years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Mercury record IDs and updates existing Ramp entries instead of duplicating them.

What happens if a Mercury record fails to post to Ramp?

When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Mercury record. Nothing silently drops.

What happens if I disconnect Mercury or Ramp?

Disconnecting Mercury stops the flow at the source. Well asks the Mercury MCP server to revoke the access token; Mercury returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Ramp is Ramp's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Mercury and Ramp?

Mercury's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Mercury to Ramp

AvailableNative · MercuryNative · Ramp

Connect Mercury to Ramp with Well

Mirror Mercury reconciliation rules onto Ramp for the second leg of every inter-account flow, with the FX gain or loss landing on its own ledger line.

Connect both toolsView all integrations

Mercury

Source

The Mercury integration connects your startup banking to Well via MCP, pulling transactions, balances, and counterparty data into your workspace.

Ramp

Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

Connect Mercury to Ramp through Well so records flow without manual rework.

What Well does between Mercury and Ramp

One-way: Mercury into Well into Ramp
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Mercury

6 events · pick one

Well engine·recipe·When a new transaction posts on your Mercury account

Source

from bank line · live webhook

Uber BV

via Mercury

Transaction

When a new transaction posts on your Mercury account

INV-1024 · 22 Apr 2026$1,284.00

Extract

5 fields read from Mercury

5 fields read

CounterpartyUber BV
Booking date22 Apr 2026
Amount$1,284.00
CurrencyUSD
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyUber BV
Tax idNL852071589B01
Ledger account6251 · Travel
Match1 candidate invoice

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorUber BV
Amount$1,284.00
Ledger6251 · Travel
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

Cross-reconcile Mercury and Ramp statements.

01Featured

Mirror reconciliation flags across accounts

When a transaction reconciles cleanly in Mercury, Well mirrors the matched flag and supporting documents onto the related Ramp record. Treasury teams running two accounts in parallel see the same reconciliation state without re-running the match per account.

Detect inter-account transfers

Outbound debits from Mercury that match inbound credits in Ramp on amount, date, and counterparty are recognised as inter-account transfers and tagged accordingly. The transfer never accidentally reads as revenue on one side or expense on the other in the downstream accounting feed.

Track FX between two-currency accounts

When Mercury debits one currency and Ramp credits another, Well snaps the FX rate at the timestamp of the transfer, tags the FX gain or loss on the Ramp ledger line, and keeps both the source and destination amounts on the matching pair so audit can recompute the conversion from primary data.

Surface unsettled inbound deposits

Deposits sitting unconfirmed in Ramp for longer than the expected settlement window are checked against Mercury outbound payments. Matches flip the Ramp record to settled; mismatches surface in a review queue with the candidate Mercury debit alongside so treasury can chase the right counterparty.

12 signals and actions across Mercury and Ramp

When a Mercury card charge posts
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code.
Trigger·Transaction
When a new transaction posts on your Mercury account
Pulls from the Mercury transactions API. Triggers on every debit or credit posting in a Mercury account.
Trigger·Transaction
When a wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date.
Trigger·Transaction
When a check is deposited to Mercury
Pulls from the Mercury transactions API. Tracks check deposits with the payer, amount, and clearing date.
Trigger·Transaction
When an ACH payment clears in Mercury
Pulls from the Mercury transactions API. Picks up cleared ACH credits and debits with the company id reference.
Trigger·Transaction
When a wire transfer is sent from Mercury
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction.
Trigger·Transaction
When a Mercury account's payment details are read
Pulls from the Mercury transactions API. Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched.
Trigger·Payment method
When a Mercury account is read
Pulls from the Mercury transactions API. Pulls each Mercury account the workspace holds with its balance, currency, and routing details.
Trigger·Account
Resolve a Ramp vendor from the bill
Driven by Mercury transaction events. Ramp's OCR resolves the vendor name from the document. You confirm or merge against an existing Ramp vendor.
Action·Company

Reference

Field mapping for Mercury → Ramp

5 fields across 1 record type, open to see the full table.

Transaction fields

5 fields flow from Mercury into Ramp.

Mercury field	Label		Ramp field	Label
transaction.amount	Amount	→	transaction.amount	Transaction amount
transaction.currency	Currency	→	transaction.currency_code	Currency
transaction.posted_at	Posted date	→	transaction.user_transaction_time	Transaction time
transaction.bank_description	Description	→	transaction.merchant_name	Merchant
transaction.id	Transaction id	→	transaction.id	Ramp transaction id

Connect Mercury and Ramp in three steps.

1
Connect Mercury
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.
- AuthConnect
2
Map your accounts
Well discovers Mercury's transactions, wires, ACH transfers, card payments, and counterparty records and the the Ramp Bill Pay drafts queue awaiting approval. Inter-account transfers and FX deltas are matched across both statements; treasury sees one reconciliation state instead of two competing accounts.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Mercury and Ramp stay secure with Well

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 Ramp host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.mercury.com/mcp

Read Mercury records
Scoped to transactions, wires, ACH transfers, card payments, and related records. No access to anything else in your Mercury account.
granted
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
granted
Modify or delete Mercury records
Not granted. Mercury is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Mercury’s admin panel.

Frequently asked questions about Mercury and Ramp on Well

01How often does Mercury data sync to Ramp?: Mercury pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02How does Well match Mercury records to entries in Ramp?: Well scores every candidate match between Mercury records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03What happens to historical Mercury data when I first connect to Ramp?: Mercury exposes the last three years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Mercury record IDs and updates existing Ramp entries instead of duplicating them.
04What happens if a Mercury record fails to post to Ramp?: When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Mercury record. Nothing silently drops.
05What happens if I disconnect Mercury or Ramp?: Disconnecting Mercury stops the flow at the source. Well asks the Mercury MCP server to revoke the access token; Mercury returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Ramp is Ramp's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Mercury and Ramp?: Mercury's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Ramp together cover multiple regions; Well's storage region is configured per workspace.