How often does Razorpay data sync to Pennylane?

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

What happens to historical Razorpay data when I first connect to Pennylane?

Razorpay exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Pennylane ledger, and re-running the backfill is safe because Well tracks the Razorpay record IDs and updates existing Pennylane entries instead of duplicating them.

How does Well prevent duplicates when posting Razorpay records to Pennylane?

Razorpay sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Razorpay can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

Can I customise which Razorpay fields are sent to Pennylane?

The default mapping covers every Razorpay field your Pennylane chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Pennylane does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Pennylane is left exactly as it stands.

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

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

How does Well authenticate with Razorpay and Pennylane?

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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Razorpay hosts outside the EU; Well processes records per the storage region configured for your workspace.

Razorpay to Pennylane

AvailableNative · RazorpayNative · Pennylane

Connect Razorpay to Pennylane with Well

Match Razorpay captured payments, refunds, and settlements against your invoices inside Well, then forward the matched documents to Pennylane's email-in inbox as supplier and customer invoices you confirm in one click.

Connect both toolsView all integrations

Razorpay

Source

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

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

Why this pair

Razorpay processes payments in INR with state-specific GST; Pennylane runs on French SMB accounting in EUR.

The currency, tax regime, and accounting model all differ. Connecting Razorpay to Pennylane through Well matches each Razorpay payment inside its own ledger with the FX-converted amount on the booking date, GST broken out per state, and the settlement reference preserved, then forwards the matched document to Pennylane's email-in. Razorpay's MCP server pushes settlement events to Well; Pennylane's OCR creates the invoice from the forwarded PDF with GST broken out on the document.

What Well does between Razorpay and Pennylane

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

post as supplier and customer invoices

Create a supplier invoice in Pennylane

auto-posted

posted

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

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

Reconcile Razorpay multi-currency charges to Pennylane entries.

01Featured

Match a payment to its invoice

Well reads payments and invoices from Razorpay, matches each payment to the invoice it settled, and forwards the reconciled document to Pennylane's email-in address.

Resolve the customer against Pennylane

Well matches the company on a Razorpay payment against the companies already in Pennylane and carries the resolved customer onto the forwarded document.

Surface unmatched payments

A Razorpay payment that finds no invoice is held in Well's queue with its customer and amount, so nothing is forwarded without a match.

Keep the accountant's ledger untouched

Well forwards reconciled documents to Pennylane's email-in and never writes journal entries through its API, so the ledger stays your accountant's.

13 signals and actions across Razorpay and Pennylane

When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Razorpay subscription cycle renews
Detects renewal cycles and links the new invoice to the recurring contract. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Razorpay invoice is paid
Pulls the paid invoice with its line items, customer, and applied tax. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Razorpay order is fully paid
Detects when an order is fully captured and links the underlying payments to the order reference. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Razorpay payment fails
Captures failed payment attempts with the error code so you can chase the customer or retry. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
Attach the source document to the Pennylane record
The PDF Well forwards is stored as the source attachment on whichever invoice Pennylane creates from it.
Action·Document

Reference

Field mapping for Razorpay → Pennylane

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

Transaction fields

4 fields flow from Razorpay into Pennylane.

Razorpay field	Label		Pennylane field	Label
payment.amount	Captured amount	→	amount	Amount
payment.currency	Currency	→	currency	Currency
payment.created_at	Capture date	→	date	Execution date
payment.id	Charge id	→	external_reference	Source id

Invoice fields

4 fields flow from Razorpay into Pennylane.

Razorpay field	Label		Pennylane field	Label
invoice.number	Invoice number	→	label	Reference
invoice.date	Issue date	→	date	Invoice date
invoice.currency	Currency	→	currency	Currency
invoice.customer_id	Customer	→	external_reference	Source id

Connect Razorpay and Pennylane 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 Pennylane Purchases tab and the customer-invoice collections list. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Razorpay and Pennylane 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 processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-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 Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane 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 Pennylane on Well

01How often does Razorpay data sync to Pennylane?: 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 Pennylane within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02What happens to historical Razorpay data when I first connect to Pennylane?: Razorpay exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Pennylane ledger, and re-running the backfill is safe because Well tracks the Razorpay record IDs and updates existing Pennylane entries instead of duplicating them.
03How does Well prevent duplicates when posting Razorpay records to Pennylane?: Razorpay sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Razorpay can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
04Can I customise which Razorpay fields are sent to Pennylane?: The default mapping covers every Razorpay field your Pennylane chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Pennylane does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Pennylane is left exactly as it stands.
05What happens if a Razorpay record fails to post to Pennylane?: When a record fails to post to Pennylane (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 Pennylane?: 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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Razorpay hosts outside the EU; Well processes records per the storage region configured for your workspace.