What Razorpay data does Well pull into Qonto?

Razorpay streams captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices 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 Razorpay event ID preserved on the entry for audit.

Will every Razorpay record post to Qonto automatically?

Not always. Within seconds of Razorpay 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.

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

Razorpay 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 Razorpay fields are sent to Qonto?

From the integration settings page you can override the default mapping field-by-field between Razorpay 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 Razorpay 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 Razorpay record. Nothing silently drops.

How does Well authenticate with Razorpay and Qonto?

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

Razorpay to Qonto

AvailableNative · RazorpayNative · Qonto

Connect Razorpay to Qonto with Well

Cross-reference Razorpay settlement IDs with Qonto statement references so a delayed payout never sits unmatched and treasury sees the timing gap immediately.

Connect both toolsView all integrations

Razorpay

Source

The Razorpay integration imports payment data from India's leading payment gateway into Well.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

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

What Well does between Razorpay and Qonto

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

Trigger from Razorpay

8 events · pick one

Well engine·recipe·When a Razorpay payment is captured

Source

from payment · live webhook

Northpoint Logistics

via Razorpay

Payment

When a Razorpay payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Razorpay

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 Razorpay and Qonto unlock together.

01Featured

Reconcile a card payout against the bank deposit

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

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

9 signals and actions across Razorpay and Qonto

When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Razorpay subscription cycle renews
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 Razorpay invoice is paid
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 Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Razorpay payment fails
Captures failed payment attempts with the error code so you can chase the customer or retry. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Razorpay order is fully paid
Detects when an order is fully captured and links the underlying payments to the order reference. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
Push a supplier invoice PDF to Qonto
Well POSTs the supplier invoice PDF to Qonto's /v2/supplier_invoices/bulk endpoint via OAuth so the invoice appears under your Qonto supplier invoices.
Action·Document

Reference

Field mapping for Razorpay → Qonto

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

Transaction fields

4 fields flow from Razorpay into Qonto.

Razorpay field	Label		Qonto field	Label
payment.amount	Captured amount	→	amount	Amount
payment.currency	Currency	→	currency	Currency
payment.created_at	Capture date	→	emitted_at	Booking date
payment.id	Charge id	→	transaction_id	Transaction id

Invoice fields

3 fields flow from Razorpay into Qonto.

Razorpay field	Label		Qonto field	Label
invoice.number	Invoice number	→	invoice_number	Invoice number
invoice.date	Issue date	→	issue_date	Issue date
invoice.currency	Currency	→	currency	Currency

Connect Razorpay and Qonto in three steps.

1
Connect Razorpay
Click Connect with Razorpay; Razorpay's MCP server handles authorisation. Razorpay'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 Razorpay's captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices 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 Razorpay and Qonto stay secure with Well

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

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

Frequently asked questions about Razorpay and Qonto on Well

01What Razorpay data does Well pull into Qonto?: Razorpay streams captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices 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 Razorpay event ID preserved on the entry for audit.
02Will every Razorpay record post to Qonto automatically?: Not always. Within seconds of Razorpay 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.
03Does Well handle multi-currency records between Razorpay and Qonto?: Razorpay 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 Razorpay fields are sent to Qonto?: From the integration settings page you can override the default mapping field-by-field between Razorpay 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 Razorpay 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 Razorpay record. Nothing silently drops.
06How does Well authenticate with Razorpay and Qonto?: Razorpay'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 Razorpay hosts outside the EU; Well processes records per the storage region configured for your workspace.