What PayPal data does Well pull into Qonto?

PayPal streams completed payments, refunds, disputes, holds, and currency-conversion 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 PayPal event ID preserved on the entry for audit.

How does Well match PayPal records to entries in Qonto?

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

Does Well handle multi-currency records between PayPal and Qonto?

PayPal carries the original transaction currency on every record and Qonto natively ledgers in multiple currencies. Well preserves the original amount, applies your Qonto chart-of-accounts conversion rules at posting time, and Well writes both the source and converted amounts onto the record it posts to Qonto, so the entry keeps both sides of the trade.

Can I customise which PayPal fields are sent to Qonto?

From the integration settings page you can override the default mapping field-by-field between PayPal and Qonto, ignore fields you do not want synced, or attach computed values from your connected data (tax tag, GL code, project). Custom mappings are versioned and take effect from the next reconciled record forward, so records you have already finished in Qonto keep the mapping they were created with.

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

How does Well authenticate with PayPal and Qonto?

PayPal'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 PayPal hosts outside the EU; Well processes records per the storage region configured for your workspace.

PayPal to Qonto

AvailableNative · PayPalNative · Qonto

Connect PayPal to Qonto with Well

When the PayPal payout hits Qonto, Well already knows which charges it covers; the deposit lands with the gross-net-fee split pre-computed and the FX captured at settlement.

Connect both toolsView all integrations

PayPal

Source

The PayPal integration connects your payment account to Well via MCP, importing transactions, fees, settlements, and refund data.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

PayPal pays into Qonto on a rolling schedule, and the Qonto inbound transfer carries no breakdown of the underlying transactions.

Connecting PayPal to Qonto through Well splits each Qonto deposit into the matching PayPal payments, refunds, fees, and currency adjustments, then the supplier invoice PDF is uploaded to Qonto's supplier-invoices section so the settlement is backed by a linked document.

What Well does between PayPal and Qonto

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

Trigger from PayPal

11 events · pick one

Well engine·recipe·When a PayPal payment is captured

Source

from payment · live webhook

Northpoint Logistics

via PayPal

Payment

When a PayPal payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from PayPal

6 fields read

CustomerNorthpoint Logistics
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordNorthpoint Logistics
Domainnorthpoint.io
Tax idNL876543219B01
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
VendorNorthpoint Logistics
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 PayPal and Qonto unlock together.

01Featured

Reconcile a card payout against the bank deposit

PayPal 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 PayPal 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

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

13 signals and actions across PayPal and Qonto

When a PayPal-issued invoice is paid
Pulls from PayPal transaction events. Captures invoices issued through PayPal with line items and tax. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a PayPal chargeback is filed
Pulls from PayPal transaction events. Flags the contested transaction and preserves the dispute trail. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal capture is recorded with its merchant fee
Pulls from PayPal transaction events. Pulls the merchant fee out of the capture so net revenue is correct. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal payment is held pending review
Pulls from PayPal transaction events. Detects pending captures and waits for the resolution before posting. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal subscription renews
Pulls from PayPal transaction events. Detects recurring billing cycles and matches the new charge to the contract. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a PayPal capture is denied
Pulls from PayPal transaction events. Surfaces denied captures with the denial reason for follow-up. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal capture includes a currency conversion
Pulls from PayPal transaction events. Pulls the FX rate and conversion fee from the capture. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal payout settles
Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a PayPal checkout completes
Pulls from PayPal transaction events. Picks up the moment a buyer finishes checkout, before the bank settlement. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction

Reference

Field mapping for PayPal → Qonto

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

Transaction fields

4 fields flow from PayPal into Qonto.

PayPal field	Label		Qonto field	Label
capture.amount.currency_code	Currency	→	currency	Currency
capture.create_time	Capture date	→	emitted_at	Booking date
capture.id	Capture id	→	transaction_id	Transaction id
capture.seller_receivable.fee	PayPal fee	→	amount	Amount

Invoice fields

3 fields flow from PayPal into Qonto.

PayPal field	Label		Qonto field	Label
invoice.detail.invoice_number	Invoice number	→	invoice_number	Invoice number
invoice.detail.invoice_date	Issue date	→	issue_date	Issue date
invoice.amount.currency_code	Currency	→	currency	Currency

Connect PayPal and Qonto in three steps.

1
Connect PayPal
Click Connect with PayPal; the PayPal MCP server registers a Well client automatically. PayPal'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 PayPal's completed payments, refunds, disputes, holds, and currency-conversion 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 PayPal and Qonto stay secure with Well

Well connects to PayPal through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived PayPal 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.paypal.com/mcp

Read PayPal records
Scoped to completed payments, refunds, disputes, holds, and related records. No access to anything else in your PayPal 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 PayPal records
Not granted. PayPal 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 PayPal’s admin panel.

Frequently asked questions about PayPal and Qonto on Well

01What PayPal data does Well pull into Qonto?: PayPal streams completed payments, refunds, disputes, holds, and currency-conversion 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 PayPal event ID preserved on the entry for audit.
02How does Well match PayPal records to entries in Qonto?: Well scores every candidate match between PayPal records and existing Qonto entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Qonto updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03Does Well handle multi-currency records between PayPal and Qonto?: PayPal carries the original transaction currency on every record and Qonto natively ledgers in multiple currencies. Well preserves the original amount, applies your Qonto chart-of-accounts conversion rules at posting time, and Well writes both the source and converted amounts onto the record it posts to Qonto, so the entry keeps both sides of the trade.
04Can I customise which PayPal fields are sent to Qonto?: From the integration settings page you can override the default mapping field-by-field between PayPal and Qonto, ignore fields you do not want synced, or attach computed values from your connected data (tax tag, GL code, project). Custom mappings are versioned and take effect from the next reconciled record forward, so records you have already finished in Qonto keep the mapping they were created with.
05What happens if a PayPal 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 PayPal record. Nothing silently drops.
06How does Well authenticate with PayPal and Qonto?: PayPal'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 PayPal hosts outside the EU; Well processes records per the storage region configured for your workspace.