What Razorpay data does Well pull into Ramp?

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 Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Razorpay event ID preserved on the entry for audit.

How often does Razorpay data sync to Ramp?

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

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

Razorpay carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

What happens if a Razorpay record fails to post to Ramp?

When a record fails to post to Ramp (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.

What happens if I disconnect Razorpay or Ramp?

Disconnecting Razorpay stops the flow at the source. Well asks the Razorpay MCP server to revoke the access token; Razorpay returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Ramp is Ramp's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Razorpay and Ramp?

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, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Razorpay and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Razorpay to Ramp

AvailableNative · RazorpayNative · Ramp

Connect Razorpay to Ramp with Well

Anchor Razorpay captured payments, refunds, and settlements to their Ramp bank lines and surface any settlement timing differences for treasury to clear in one queue.

Connect both toolsView all integrations

Razorpay

Source

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

Ramp

Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

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

What Well does between Razorpay and Ramp

One-way: Razorpay into Well into Ramp
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

Tessellate Design

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

CustomerTessellate Design
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordTessellate Design
Domaintessellate.studio
Tax idGB432109876
Sales journalVE · 2026

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorTessellate Design
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

Workflows Razorpay and Ramp unlock together.

01Featured

Reconcile a card payout against the bank deposit

Razorpay payouts are matched to the inbound Ramp 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 Ramp 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 Ramp 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 Ramp 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.

12 signals and actions across Razorpay and Ramp

When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order.
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
When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage.
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
Attach the source document to the Ramp bill
The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document

Reference

Field mapping for Razorpay → Ramp

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

Transaction fields

4 fields flow from Razorpay into Ramp.

Razorpay field	Label		Ramp field	Label
payment.amount	Captured amount	→	transaction.amount	Transaction amount
payment.currency	Currency	→	transaction.currency_code	Currency
payment.created_at	Capture date	→	transaction.user_transaction_time	Transaction time
payment.id	Charge id	→	transaction.id	Ramp transaction id

Invoice fields

3 fields flow from Razorpay into Ramp.

Razorpay field	Label		Ramp field	Label
invoice.number	Invoice number	→	matched_record.reference	Reference
invoice.currency	Currency	→	matched_record.currency	Currency
invoice.customer_id	Customer	→	matched_record.id	Source id

Connect Razorpay and Ramp 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 Ramp Bill Pay drafts queue awaiting approval. 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 Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Razorpay and Ramp 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's storage region is configured per workspace regardless of where Razorpay and Ramp host theirs.

MCP server authStorage region per workspaceGDPR-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
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
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 Ramp on Well

01What Razorpay data does Well pull into Ramp?: 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 Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Razorpay event ID preserved on the entry for audit.
02How often does Razorpay data sync to Ramp?: Razorpay 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 Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03Does Well handle multi-currency records between Razorpay and Ramp?: Razorpay carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
04What happens if a Razorpay record fails to post to Ramp?: When a record fails to post to Ramp (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.
05What happens if I disconnect Razorpay or Ramp?: Disconnecting Razorpay stops the flow at the source. Well asks the Razorpay MCP server to revoke the access token; Razorpay returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Ramp is Ramp's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Razorpay and Ramp?: 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, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Razorpay and Ramp together cover multiple regions; Well's storage region is configured per workspace.