Integrations · Payments

Connect Razorpay to Well

Name: Razorpay entities in Well
Creator: Well

Connect Razorpay so its payment, payout, refund, and customer become queryable in conversation and through your agents.

What Well pulls from Razorpay

Razorpay feeds payment, payout, refund into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Razorpay’s access.

From Razorpay	In Well	Relation
Payment	Invoice	Matches
Payout	Bank deposit	Settles into
Refund	Credit note	Becomes
Customer	Company	Enriches

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Razorpay → Well

8 triggers from Razorpay.

When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage.
Trigger·Transaction
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order.
Trigger·Transaction
When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank.
Trigger·Transaction
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window.
Trigger·Transaction
When a Razorpay subscription cycle renews
Detects renewal cycles and links the new invoice to the recurring contract.
Trigger·Invoice
When a Razorpay invoice is paid
Pulls the paid invoice with its line items, customer, and applied tax.
Trigger·Invoice
When a Razorpay order is fully paid
Detects when an order is fully captured and links the underlying payments to the order reference.
Trigger·Transaction
When a Razorpay payment fails
Captures failed payment attempts with the error code so you can chase the customer or retry.
Trigger·Transaction

What Well does with your Razorpay connection

Connect

Connect Razorpay over OAuth (MCP DCR): Well registers a client through Razorpay's OAuth Dynamic Client Registration and you approve on Razorpay's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings payment, payout, and refund in from Razorpay on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Razorpay entity into invoice, bank deposit, and credit note, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Razorpay lands in the workspace as invoice, bank deposit, and credit note you can search, chart, and automate.

Questions Razorpay unlocks

Ask in plain language. Well answers from your connected Razorpay connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Razorpay connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Razorpay connection…

Connect Razorpay in three steps

01
Authorise Razorpay via MCP
From Well's Connections panel, search for Razorpay and click Connect. Well discovers Razorpay's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Razorpay's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.razorpay.com/mcp
02
Map your entities
Well's MCP client discovers payment, payout, refund, and customer from Razorpay that Razorpay's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Razorpay records. Because Razorpay ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Razorpay records happens in the background.

How Razorpay stays secure with Well

Well connects to Razorpay's MCP server (mcp.razorpay.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Razorpay secret. Tokens are scoped to the payment, payout, refund, and customer Razorpay exposes and refreshed server-side. Reads only, Well cannot modify or delete Razorpay records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.razorpay.com/mcp

Read Razorpay records
Resources the Razorpay MCP server exposes, scoped by your OAuth approval.
granted
Resolve payment, payout, refund, and customer across your stack
Match identifiers in Razorpay against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Razorpay records
Not granted; Razorpay is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Razorpay passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Razorpay’s admin panel.

Frequently asked questions about Razorpay and Well

From Well, open Connections, find Razorpay, and click Connect. Well discovers the OAuth metadata at mcp.razorpay.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Razorpay's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in payment, payout, refund, and customer from Razorpay and reshapes each entity into your workspace: payment becomes invoice; payout becomes bank deposit. Every record arrives with the source identifier preserved, so Razorpay stays the source of truth while Well lets you query the data alongside the rest of your stack.

Once Razorpay is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Razorpay source, so you can always trace a workspace record back to the original.

Yes. Razorpay customers are indexed in your workspace as company, so questions like "show me last week's customers from Razorpay" return them with the original Razorpay link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

Well combines live Razorpay events with periodic reconciliation reads of payment, payout, refund, and customer. New rows appear within seconds when Razorpay pushes them; periodic reads catch anything a push missed. The first connect backfills history from Razorpay in the background.

Open Connections > Razorpay in Well and click Disconnect. Well calls Razorpay's token revocation endpoint and stops calling Razorpay immediately on its side; provider-side propagation to Razorpay's admin panel varies by provider. The payment, payout, refund, and customer Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Well captures the original currency and the conversion rate Razorpay applies, then reports both side by side. If you operate in EUR and Razorpay settles in USD or GBP, the converted line and the raw line both land in the ledger, so reconciliation against the deposit currency works without manual FX math.