Bring Mercury payments together with Ramp spend in Well

About Mercury and Ramp

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.

1. 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. 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. 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

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.