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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Stripe hosts outside the EU; Well processes records per the storage region configured for your workspace.

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 works on supplier invoices in both directions.

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

Reconcile a card payout against the bank deposit

Stripe payouts are matched to the inbound Qonto 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 Qonto 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 Qonto 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 Qonto 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.

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; you approve the connection inside Qonto and authorise the supplier_invoice.write scope so Well can POST PDFs to /v2/supplier_invoices. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
- First sync~30 min

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. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-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
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
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 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Stripe hosts outside the EU; Well processes records per the storage region configured for your workspace.

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-aligned
Revocable Qonto access in one click

Other ways to connect Stripe or Qonto through Well.

Browse all

Stripe

See the Stripe connector

Qonto

See the Qonto connector

Stripe → Pennylane

Match every Stripe charge and payout inside Well, then forwa…

Stripe → QuickBooks

Match Stripe charges, refunds, payouts inside Well, then for…

PayPal → Qonto

Match PayPal payouts to the Qonto bank deposit that received…

Bill.com

See the Bill.com connector

Melio

See the Melio connector

iBanFirst

See the iBanFirst connector

Last reviewed: 2026-05-26

Connect Stripe to Qonto with Well

About Stripe and Qonto

What Well does between Stripe and Qonto

Workflows Stripe and Qonto unlock together.

Reconcile a card payout against the bank deposit

Detect failed transfers before they hit the GL

Track multi-currency settlements

15 signals and actions across Stripe and Qonto

When a payment intent settles

When a Stripe payout lands in your bank

When a Stripe invoice is finalised

When a Stripe dispute is opened

When a Stripe customer is created

When a Stripe subscription cycle renews

When a Stripe charge succeeds

When a Stripe invoice is marked paid

When a Stripe subscription starts

Transaction fields

Invoice fields

Company fields

Connect Stripe and Qonto in three steps.

Connect Stripe

Map your accounts

Connect Qonto

How Stripe and Qonto stay secure with Well

Frequently asked questions about Stripe and Qonto on Well

Reconcile Stripe with Qonto.

Related integrations