What Stripe data does Well pull into Melio?

Stripe streams charges, refunds, payouts, customers, disputes, and subscription events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Melio as bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture, with the Stripe event ID preserved on the entry for audit.

How often does Stripe data sync to Melio?

Stripe 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 Melio within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

How does Well match Stripe records to entries in Melio?

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

How does Well prevent duplicates when posting Stripe records to Melio?

Stripe sends each event with a stable resource ID that Well tracks against the Melio ledger. Webhook replays (which Stripe can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Melio entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

What happens if a Stripe record fails to post to Melio?

When a record fails to post to Melio (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.

How does Well authenticate with Stripe and Melio?

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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted at rest and in transit under TLS 1.3. Stripe and Melio together cover multiple regions; Well's storage region is configured per workspace.

Stripe to Melio

AvailableNative · StripeNative · Melio

Connect Stripe to Melio with Well

Pair Stripe disbursements with Melio bills; failed transfers surface inside Well so the next manual schedule reflects the real state.

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.

Melio

Target

The Melio connection delivers extracted bills into Melio through its Pay Bills email address.

Why this pair

Stripe pays out a batch from customer collections; Melio sends scheduled payments to vendors on US rails.

Connecting Stripe to Melio through Well stages Melio vendor payments against the latest Stripe payout balance with the underlying charge breakdown attached on each payment record, so vendor disbursement is funded directly from customer revenue. Stripe's MCP server pushes payout events to Well; Melio's Smart Bill Capture creates the vendor payment bill from the forwarded PDF, with the batch reference attached for your team to schedule.

What Well does between Stripe and Melio

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

Trigger from Stripe

14 events · pick one

Well engine·recipe·When a Stripe charge succeeds

Source

from payment · live webhook

Riverstone Capital

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

CustomerRiverstone Capital
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordRiverstone Capital
Domainriverstone.partners
Tax idFR45678123456
Sales journalVE · 2026

Confidence97%

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

Post

schedule as bills

Create a bill in your Melio inbox

auto-posted

posted

TypeBill
VendorRiverstone Capital
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Melio

Action in Melio

2 compatible with this trigger

Create a bill in your Melio inboxResolve a Melio vendor from the bill

Bridge Stripe payouts to Melio reimbursements.

01Featured

Bridge merchant payouts to vendor reimbursements

Stripe payout batches are joined to the reimbursement records inside Well by date and total. The per-line breakdown becomes individual documents forwarded to Melio, so a payout that covers 30 reimbursements arrives as 30 entries you can confirm one by one, not one lump sum to chase down later.

Detect failed disbursements

A failed Stripe disbursement triggers a flag inside Well: the linked vendor payment is marked needs reschedule, the Stripe failure code is attached, and the workspace owner is notified with the candidate next-payment date based on your standard reschedule policy.

Tie chargebacks to the originating vendor bill

Chargebacks landing in Stripe are traced back to the originating vendor bill inside Well by reference and amount. The chargeback context is forwarded to Melio on the affected document, so AP can decide whether to reschedule a corrected payment or write off the loss with the original Stripe reason in hand.

Settle expense reimbursements weekly

Approved expense reimbursements are batched inside Well into a weekly Stripe disbursement run, paid in a single ACH window, and matched on settlement. The per-claim audit trail stays intact inside Well and on the matched documents forwarded to Melio.

18 signals and actions across Stripe and Melio

When a Stripe invoice is finalised
Pulls from the Stripe events feed. Captures the finalised invoice before payment, with totals and due date.
Trigger·Invoice
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 customer is created
Pulls from the Stripe events feed. Pulls new customer records with name, email, and tax id where set.
Trigger·Company
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 charge fails
Pulls from the Stripe events feed. Captures failed charges so you can chase the customer or retry.
Trigger·Transaction
When a Stripe invoice is marked paid
Pulls from the Stripe events feed. Pulls the paid invoice with its line items, customer, and applied tax.
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 customer is updated
Pulls from the Stripe events feed. Detects changes to customer name, billing address, or tax id.
Trigger·Company
When a Stripe dispute is opened
Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason.
Trigger·Transaction

Reference

Field mapping for Stripe → Melio

12 fields across 3 record types, open to see the full table.

Transaction fields

5 fields flow from Stripe into Melio.

Stripe field	Label		Melio field	Label
charge.amount	Charge amount	→	amount	Amount
charge.currency	Currency	→	currency	Currency
charge.created	Charge date	→	scheduled_for	Payment date
charge.description	Description	→	reference	Reference
charge.id	Charge id	→	payment_id	Payment id

Invoice fields

4 fields flow from Stripe into Melio.

Stripe field	Label		Melio field	Label
invoice.currency	Currency	→	currency	Currency
invoice.number	Invoice number	→	bill_number	Bill number
invoice.due_date	Due date	→	due_date	Due date
invoice.customer	Customer reference	→	bill_id	Bill id

Company fields

3 fields flow from Stripe into Melio.

Stripe field	Label		Melio field	Label
customer.name	Customer name	→	vendor_name	Vendor name
customer.email	Email	→	email	Email
customer.id	Customer id	→	vendor_id	Vendor id

Connect Stripe and Melio 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 Melio Bills Inbox awaiting payment scheduling. Each payout is paired to its scheduled vendor payment by date and total; failed transfers reverse the linked payment automatically so the schedule self-corrects.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Melio
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.
- AuthConnect
- First sync~10 min

How Stripe and Melio 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 Melio 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 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.
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 Melio on Well

01What Stripe data does Well pull into Melio?: Stripe streams charges, refunds, payouts, customers, disputes, and subscription events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Melio as bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture, with the Stripe event ID preserved on the entry for audit.
02How often does Stripe data sync to Melio?: Stripe 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 Melio within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03How does Well match Stripe records to entries in Melio?: Well scores every candidate match between Stripe records and existing Melio entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Melio updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04How does Well prevent duplicates when posting Stripe records to Melio?: Stripe sends each event with a stable resource ID that Well tracks against the Melio ledger. Webhook replays (which Stripe can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Melio entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
05What happens if a Stripe record fails to post to Melio?: When a record fails to post to Melio (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.
06How does Well authenticate with Stripe and Melio?: 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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted at rest and in transit under TLS 1.3. Stripe and Melio together cover multiple regions; Well's storage region is configured per workspace.