Razorpay logoIntegrations · Payments

Connect Razorpay to Well

Sync Razorpay captured payments, refunds, and settlements into Well to simplify your reconciliation

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 RazorpayIn Well
Payment
Invoice
Payout
Bank deposit
Refund
Credit note
Customer
Company
Razorpay logo
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

  1. 01

    Connect your Razorpay account

    Authorize Well to access your Razorpay transaction history and invoice records.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.razorpay.com/mcp
  2. 02

    Map your entities

    Confirm the connection within your Well workspace to begin the initial data sync.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Verify that your captured payments, refunds, and settlements appear correctly in your transaction ledger.

    • First syncstarts as soon as connect completes

Well only reads your Razorpay transaction history and never modifies your payment settings or customer records.

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

How does Well retrieve my Razorpay transactions?

Well pulls your captured payments, refunds, settlements, and invoices directly from your Razorpay account to keep your workspace updated.

Can I update or edit Razorpay invoices from within Well?

No. Well reads your Razorpay data to help you reconcile transactions, but it does not write, edit, or send data back to your Razorpay account.

How does Well handle customer details associated with payments?

Well imports customer names and payment methods linked to each transaction, allowing you to view payment histories in one place.

Razorpay logo

Ready to connect Razorpay?

Connect once. Every payment, payout, refund from Razorpay becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.