How does Well match Stripe records to entries in Ramp?

Well scores every candidate match between Stripe 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 Stripe data when I first connect to Ramp?

Stripe exposes the last two 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 Stripe record IDs and updates existing Ramp entries instead of duplicating them.

Does Well handle multi-currency records between Stripe and Ramp?

Stripe carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

What happens if a Stripe 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 Stripe record. Nothing silently drops.

What happens if I disconnect Stripe or Ramp?

Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe 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 Stripe and Ramp?

Stripe'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. Stripe and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Stripe to Ramp

AvailableNative · StripeNative · Ramp

Connect Stripe to Ramp with Well

Tie every Stripe payout to the matching Ramp deposit, with fees split and FX captured on each linked pair.

Connect both toolsView all integrations

Stripe

Source

The Stripe integration connects your payment infrastructure to Well via MCP, pulling charges, invoices, subscriptions, refunds, and payout data into your workspace automatically.

Ramp

Target

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

Why this pair

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

What Well does between Stripe and Ramp

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

Trigger from Stripe

12 events · pick one

Well engine·recipe·When a Stripe charge succeeds

Source

from payment · live webhook

Lemon Studio

via Stripe

Charge

When a Stripe charge succeeds

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Stripe

6 fields read

CustomerLemon Studio
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordLemon Studio
Domainlemonstudio.io
Tax idFR42514682431
Sales journalVE · 2026

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
VendorLemon Studio
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

Workflows Stripe and Ramp unlock together.

01Featured

Reconcile a card payout against the bank deposit

Stripe payouts are matched to the inbound Ramp deposit by amount, date, and currency. Once the deposit lands, the linked payout collapses onto the right bank line and the fee delta is split onto a separate Ramp record so the bank statement and the processor settlement agree to the cent.

Detect failed transfers before they hit the GL

When a Stripe payout is reversed (chargeback chain, NSF, fraud claim), Well watches the matching Ramp bank line for the reversal. The two events are paired in Well so the next reconciliation pass treats them as a single net-zero event rather than two competing entries.

Track multi-currency settlements

Stripe payouts in non-base currencies are converted at settlement and Well stores the FX rate alongside the Ramp deposit. The conversion delta is tagged for review so finance can compare the processor's FX against the bank's mid-market rate and challenge any divergence.

18 signals and actions across Stripe and Ramp

When a Stripe subscription starts
Pulls from the Stripe events feed. Tracks new subscription records with cadence, amount, and customer.
Trigger·Invoice
When a payment intent settles
Pulls from the Stripe events feed. Detects successful payment intents and links the captured charge to the intent.
Trigger·Transaction
When a Stripe payout is created
Pulls from the Stripe events feed. Triggers on every payout batch with the underlying charges and fees.
Trigger·Transaction
When a Stripe payout lands in your bank
Pulls from the Stripe events feed. Detects the bank arrival of a Stripe payout to anchor the deposit.
Trigger·Transaction
When a Stripe refund is issued
Pulls from the Stripe events feed. Captures partial and full refunds with the originating charge id.
Trigger·Transaction
When a Stripe dispute is opened
Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason.
Trigger·Transaction
When a Stripe charge succeeds
Pulls from the Stripe events feed. Captures successful card and bank charges with currency, fee, and customer reference.
Trigger·Transaction
When a Stripe charge fails
Pulls from the Stripe events feed. Captures failed charges so you can chase the customer or retry.
Trigger·Transaction
When a Stripe customer is updated
Pulls from the Stripe events feed. Detects changes to customer name, billing address, or tax id.
Trigger·Company

Reference

Field mapping for Stripe → Ramp

8 fields across 2 record types, open to see the full table.

Transaction fields

5 fields flow from Stripe into Ramp.

Stripe field	Label		Ramp field	Label
charge.amount	Charge amount	→	transaction.amount	Transaction amount
charge.currency	Currency	→	transaction.currency_code	Currency
charge.created	Charge date	→	transaction.user_transaction_time	Transaction time
charge.description	Description	→	transaction.merchant_name	Merchant
charge.id	Charge id	→	transaction.id	Ramp transaction id

Invoice fields

3 fields flow from Stripe into Ramp.

Stripe field	Label		Ramp field	Label
invoice.currency	Currency	→	matched_record.currency	Currency
invoice.number	Invoice number	→	matched_record.reference	Reference
invoice.customer	Customer reference	→	matched_record.id	Source id

Connect Stripe and Ramp in three steps.

1
Connect Stripe
Click Connect with Stripe; Stripe's MCP server handles authorisation. Stripe's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Stripe's charges, refunds, payouts, customers, disputes, and subscription events and the the Ramp Bill Pay drafts queue awaiting approval. Payouts are anchored to the matching bank deposit with the fee split into its own ledger line, so reconciliation shows gross revenue and processor fees separately.
- 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 Stripe and Ramp stay secure with Well

Well connects to Stripe through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Stripe secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Stripe and Ramp host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.stripe.com

Read Stripe records
Scoped to charges, refunds, payouts, customers, and related records. No access to anything else in your Stripe 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 Stripe records
Not granted. Stripe 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 Stripe’s admin panel.

Frequently asked questions about Stripe and Ramp on Well

01How does Well match Stripe records to entries in Ramp?: Well scores every candidate match between Stripe 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.
02What happens to historical Stripe data when I first connect to Ramp?: Stripe exposes the last two 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 Stripe record IDs and updates existing Ramp entries instead of duplicating them.
03Does Well handle multi-currency records between Stripe and Ramp?: Stripe carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
04What happens if a Stripe 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 Stripe record. Nothing silently drops.
05What happens if I disconnect Stripe or Ramp?: Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe 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 Stripe and Ramp?: Stripe'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. Stripe and Ramp together cover multiple regions; Well's storage region is configured per workspace.