What Square data does Well pull into Qonto?

Square streams card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments 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 Square event ID preserved on the entry for audit.

How often does Square data sync to Qonto?

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

How does Well match Square records to entries in Qonto?

Well scores every candidate match between Square 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.

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

Square 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 Square record IDs and updates existing Qonto entries instead of duplicating them.

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

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

How does Well authenticate with Square and Qonto?

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

Square to Qonto

AvailableNative · SquareNative · Qonto

Connect Square to Qonto with Well

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

Connect both toolsView all integrations

Square

Source

The Square connection reads your Square account through the Square MCP server using OAuth.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

Connect Square to Qonto through Well so records flow without manual rework.

What Well does between Square and Qonto

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

Trigger from Square

7 events · pick one

Well engine·recipe·When a Square card payment is captured

Source

from payment · live webhook

Verdant Foods

via Square

Payment

When a Square card payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Square

6 fields read

CustomerVerdant Foods
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordVerdant Foods
Domainverdantfoods.eu
Tax idES98765432100
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
VendorVerdant Foods
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 Square and Qonto unlock together.

01Featured

Reconcile a card payout against the bank deposit

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

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

10 signals and actions across Square and Qonto

When a Square refund is issued
Captures partial and full refunds with the originating payment id. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Square customer is updated
Detects changes to a Square customer's name, email, or stored payment method and refreshes the company record. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
When a Square card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Square payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Square order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Square payment includes a tip
Pulls the tip amount off the payment so it can be routed separately. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company

Reference

Field mapping for Square → Qonto

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

Transaction fields

5 fields flow from Square into Qonto.

Square field	Label		Qonto field	Label
payment.amount_money.amount	Payment amount	→	amount	Amount
payment.amount_money.currency	Currency	→	currency	Currency
payment.created_at	Charge date	→	emitted_at	Booking date
payment.note	Description	→	label	Label
payment.id	Charge id	→	transaction_id	Transaction id

Invoice fields

4 fields flow from Square into Qonto.

Square field	Label		Qonto field	Label
invoice.invoice_number	Invoice number	→	invoice_number	Invoice number
invoice.invoice_date	Issue date	→	issue_date	Issue date
invoice.due_date	Due date	→	due_date	Due date
invoice.total_money.currency	Currency	→	currency	Currency

Connect Square and Qonto in three steps.

1
Connect Square
Click Connect with Square; Square's MCP server registers a Well client automatically. Square'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 Square's card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments 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 Square and Qonto stay secure with Well

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

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

Frequently asked questions about Square and Qonto on Well

01What Square data does Well pull into Qonto?: Square streams card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments 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 Square event ID preserved on the entry for audit.
02How often does Square data sync to Qonto?: Square 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 Qonto within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03How does Well match Square records to entries in Qonto?: Well scores every candidate match between Square 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.
04What happens to historical Square data when I first connect to Qonto?: Square 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 Square record IDs and updates existing Qonto entries instead of duplicating them.
05Does Well handle multi-currency records between Square and Qonto?: Square 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.
06How does Well authenticate with Square and Qonto?: Square'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 Square hosts outside the EU; Well processes records per the storage region configured for your workspace.