Razorpay to Salesforce NPSP — Integration Guide for Indian NGOs

Indian NGOs using Salesforce NPSP typically collect donations through multiple channels — fundraising events, website donation buttons, recurring UPI mandates, and corporate transfers. Razorpay handles most of the online payment layer. The gap that creates real work is what happens between a payment completing in Razorpay and a Donation record appearing in Salesforce.

Without an integration, that gap is filled by someone manually reconciling Razorpay reports against Salesforce records — a process that is slow, error-prone, and does not scale. This article covers what the integration looks like, how it works, and what it handles automatically.

What Syncs Automatically

A properly configured Razorpay–Salesforce integration handles the following automatically, without any manual intervention:

• One-time donations — Every successful Razorpay payment creates or updates a Contact in Salesforce and creates a matching Donation (Opportunity) record with amount, currency, payment method, and transaction ID.
• NACH recurring mandates — Monthly mandate status syncs in real time. Cancellations, failed debits, and renewals all update the related Salesforce Recurring Donation record automatically.
• Donation receipts — An 80G-formatted receipt is triggered from Salesforce within 30 seconds of payment confirmation and sent to the donor's email. For NACH mandates, a receipt is sent each time a debit succeeds.
• Payment failures — Failed payments create a Task in Salesforce assigned to the donor services team, flagged for follow-up within 48 hours.
• Refunds — Processed refunds update the Donation record status and trigger a confirmation email to the donor.

Contact Matching — How It Handles Duplicates

The most common integration problem is duplicate Contact records. A donor gives online in March without creating an account, gives again in September under a slightly different email, and by year-end there are two unlinked Contact records in Salesforce with split giving history.

NPSP's built-in duplicate matching rules help, but they need to be configured before the integration goes live. We set up matching on email address (primary), mobile number (secondary), and name-plus-postcode (tertiary). When Razorpay sends a payment with an email that matches an existing Contact, the Donation is linked to that Contact. When there is no match, a new Contact is created with a flag for manual review.

Campaign Tracking

Razorpay payment links and forms support custom parameters. We use these to pass the Salesforce Campaign ID through to the donation record, so every donation is automatically associated with the campaign that drove it — whether that is a Diwali appeal, a specific grant programme, or a peer-to-peer fundraising event.

This makes your fundraising analytics in Salesforce meaningful. You can see the cost-per-donation by campaign, average gift by channel, and donor retention by first-touch campaign — all without any manual data entry.

FCRA Compliance Flags

For NGOs with FCRA registration: the integration automatically flags donations from foreign payment sources. Any payment processed through a Razorpay account linked to an international card or foreign bank triggers the FCRA compliance workflow — creating the 7-day disclosure task and marking the Donation as a foreign contribution.

This only works correctly when Razorpay is configured to capture the donor's country during checkout, which requires a small change to the Razorpay payment form. We handle this configuration as part of the integration setup.

Implementation Timeline

The Razorpay–Salesforce integration is typically implemented in 2–3 weeks as a standalone project for existing Salesforce users, or included in a standard NPSP implementation. The steps:

• Week 1: Razorpay webhook configuration, Salesforce API setup, duplicate matching rule review
• Week 2: Donation record mapping, Household logic, FCRA flag configuration, receipt template setup
• Week 3: Testing across all payment types (UPI, card, net banking, NACH), donor communication testing, data reconciliation against existing records

For NGOs with large existing Razorpay transaction histories, we can also run a historical data migration — bringing past Razorpay payments into Salesforce as Donation records, giving you a complete giving history for every donor regardless of when the Salesforce implementation went live.