Resolve Razorpay customers against Qonto records

About Razorpay and Qonto

Razorpay

Source

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

Qonto

Target

Qonto is two separate authorisations, not one.

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

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 in transit under TLS 1.3. Anything Well holds between Razorpay and Qonto is encrypted at rest and handled in line with GDPR.