What Stripe data does Well pull into Qonto?

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 Qonto as supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices, with the Stripe event ID preserved on the entry for audit.

Will every Stripe record post to Qonto automatically?

Not always. Within seconds of Stripe firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

What happens to historical Stripe data when I first connect to Qonto?

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 Qonto ledger, and re-running the backfill is safe because Well tracks the Stripe record IDs and updates existing Qonto entries instead of duplicating them.

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

When a record fails to post to Qonto (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 Qonto?

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 Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 Qonto?

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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Stripe and Qonto is encrypted at rest and handled in line with GDPR.

Stripe to Qonto

AvailableNative · StripeNative · Qonto

Connect Stripe to Qonto with Well

Stripe settlements arrive in Qonto with the underlying charge breakdown preserved, so the bank reconciliation sees gross revenue and processor fees as separate lines.

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.

Qonto

Target

The Qonto connection is Qonto's MCP server, approved over Dynamic Client Registration, and it carries offline_access, organization.

Why this pair

Stripe and Qonto sit on either side of a single line that breaks reconciliation: the payout.

Stripe pays out a batch covering dozens of charges, with fees netted out; Qonto receives that one deposit with no breakdown attached. Connecting them through Well means every Qonto inbound transfer arrives already split: by charge, by customer, by refund, with the fees on a separate ledger row.

What Well does between Stripe and Qonto

One-way: Stripe into Well into Qonto
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

reconcile as supplier invoices

Push a supplier invoice PDF to Qonto

auto-posted

posted

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

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

Workflows Stripe and Qonto unlock together.

01Featured

Minutes, not days

Reconcile Stripe payouts against Qonto on a rolling basis instead of a month-end scramble.

Catch breaks the same day

Failed payouts, stuck refunds, and FX adjustments surface when they happen, not weeks later.

Charge to deposit, traced

Follow every customer charge from Stripe through to its Qonto deposit with full history.

Retire the match spreadsheet

Drop the month-end workbook that stitches Stripe and Qonto together by hand.

15 signals and actions across Stripe and Qonto

When a payment intent settles
Pulls from the Stripe events feed. Detects successful payment intents and links the captured charge to the intent. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
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. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Stripe invoice is finalised
Pulls from the Stripe events feed. Captures the finalised invoice before payment, with totals and due date. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Stripe dispute is opened
Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
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. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
When a Stripe subscription cycle renews
Pulls from the Stripe events feed. Detects renewal cycles and links the new invoice to the recurring contract. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Stripe charge succeeds
Pulls from the Stripe events feed. Captures successful card and bank charges with currency, fee, and customer reference. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
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. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Stripe subscription starts
Pulls from the Stripe events feed. Tracks new subscription records with cadence, amount, and customer. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice

Reference

Field mapping for Stripe → Qonto

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

Transaction fields

5 fields flow from Stripe into Qonto.

Stripe field	Label		Qonto field	Label
charge.amount	Charge amount	→	amount	Amount
charge.currency	Currency	→	currency	Currency
charge.created	Charge date	→	emitted_at	Booking date
charge.description	Description	→	label	Label
charge.id	Charge id	→	transaction_id	Transaction id

Invoice fields

5 fields flow from Stripe into Qonto.

Stripe field	Label		Qonto field	Label
invoice.currency	Currency	→	currency	Currency
invoice.number	Invoice number	→	invoice_number	Invoice number
invoice.issue_date	Issue date	→	issue_date	Issue date
invoice.due_date	Due date	→	due_date	Due date
invoice.tax	Tax total	→	tax_amount	Tax

Company fields

3 fields flow from Stripe into Qonto.

Stripe field	Label		Qonto field	Label
customer.name	Customer name	→	supplier_name	Supplier
customer.tax_id	Tax id	→	supplier_tax_id	Tax id
customer.metadata.domain	Domain	→	supplier_website	Website

Connect Stripe and Qonto 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 Qonto supplier-invoices section. 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 Qonto
Click Connect with Qonto; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

47 agent skills run on Stripe and Qonto.

Each one answers a question from the data this pair brings in. The required ones return nothing until a source like it is connected.

Needs a source like these

Runway

Know how many months of cash you have at your current burn, with both sides of the division shown.

Cash position

Know how much cash you hold right now, with the accounts counted and the ones left out both stated.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Chase late invoices

Get a prioritized list of who to chase for payment, with their contact info and a message already drafted.

Rank clients by LTV

Find out what each customer is worth over its whole life, ranked from the most valuable down.

Company profile

Everything you know about one company, in one view.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Missing receipts

Find the bills with no paperwork attached, before an auditor does.

Burn rate

Know what you spend in an average month over a window you can see, with the months that carried no spend counted.

Recurring revenue

Know what you can count on earning each month, averaged over real months.

Cash forecast

See the settled month-end cash series and where the line goes from the last complete month.

Cash flow bridge

See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close from open to sent to your accounting tool.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Board pack

The board numbers in one pass, each with its scope and its window stated.

Subscription spend

See which suppliers you pay on a schedule, what each costs a month, and how that spend moved.

Subscription actions

Cancel a subscription, ask for a better price or contest a double debit, with your bank's facts in the email.

SaaS billing

See who cancelled, which payments failed and what was refunded, read live from Stripe, Paddle or Lago.

Prefill Form 1120

Get page 1 of your 1120 back as a PDF with your own book figures already in the boxes, and a list of every box left for your preparer.

Prefill Form 1099-NEC

Get one 1099-NEC per contractor back as a PDF with your own posted figures already in box 1, and the list of payees you cannot file for yet.

Unposted and blocked

See what in a month has not reached the ledger, and which pile each item sits in.

Check bank and books

Check that your bank and your books match, and re-run what missed rows.

VAT radar

See the net VAT your posted ledger shows for a quarter and which invoices to fix first.

Accounting reports

Read your profit and loss or balance sheet straight from QuickBooks or Xero.

Answers better with these connected

Receivables aging

See who owes you money, and how long they have been sitting on it.

Bills due

See what you owe and when, ordered by due date with a running total.

FX exposure

See how much of your cash and receivables sit outside your reporting currency.

Invoice fetching agents

See exactly which agents would run, before any of them does.

Convert currencies

Turn mixed currencies into one number you can actually audit.

Payables aging

See what you owe your suppliers, and how long each bill has been past due.

Compose a board

The measures you name, arranged on one board that stores the question rather than the answer.

Revenue by customer

See which customers your revenue came from in a period, ranked, with the part you could not place named.

Supplier spend register

See what you paid each supplier over a year, ranked, with the invoices that could not be placed counted beside the total.

Call and claim

Claim a refund or a compensation with the evidence in hand, and know what to say when you call.

Money back

Find the supplier refunds and VAT credits your company is still owed, with the evidence for each.

Employer cost

Read a month of payslips, or each of several months, and state, per person, gross pay plus the employee deductions and the employer charges the payslip printed, then list the payroll related bills paid from the bank that no payslip carries.

Check contractor status

For each supplier that looks like a freelancer, read the purchase invoices, the payment rail and any contract Well holds, and state the facts a requalification question turns on, next to the papers your country expects you to keep.

Uses them when they are there

Invoice design

Pick how an invoice prints, from the designs and records you already have.

Chart of accounts

Read the accounts your workspace posts to, number by number.

Import a statement

Drop a statement you already have, and get its transactions as records.

Connects and checks them

Check your connections

See what is connected, what is syncing, and what is missing.

Build your context graph

Connect your AI apps and your tools, then see your business as one context graph.

Connect your bank

Get the bank feed in, and confirm it is really live.

Tax id chase

The companies you deal with that carry no tax identifier, listed before year end.

Browse all skills

How Stripe and Qonto 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. Anything Well holds between Stripe and Qonto is encrypted at rest and handled in line with GDPR.

MCP server authEncrypted at restGDPR compliant

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
Post approved records to Qonto
Over Qonto's API, scoped to supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices you have approved (case-by-case or via a per-rule auto-post threshold).
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
Not granted. A session resolves only to the workspaces your account belongs to, and Well checks that membership before it returns any record.
refused

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

Frequently asked questions about Stripe and Qonto on Well

01What Stripe data does Well pull into Qonto?: 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 Qonto as supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices, with the Stripe event ID preserved on the entry for audit.
02Will every Stripe record post to Qonto automatically?: Not always. Within seconds of Stripe firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03What happens to historical Stripe data when I first connect to Qonto?: 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 Qonto ledger, and re-running the backfill is safe because Well tracks the Stripe record IDs and updates existing Qonto entries instead of duplicating them.
04What happens if a Stripe record fails to post to Qonto?: When a record fails to post to Qonto (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 Qonto?: 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 Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 Qonto?: 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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Stripe and Qonto is encrypted at rest and handled in line with GDPR.

Reconcile Stripe with Qonto.

Connect both accounts and see your payouts matched automatically.

Try Well free

Read-only scopes on Stripe
AES-256 at rest, TLS 1.3 in transit
GDPR compliant
Revocable Qonto access in one click

Other ways to connect Stripe or Qonto through Well.

Browse all