Bring Razorpay payments into Ramp with the customer resolved

About Razorpay and Ramp

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.

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

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.