Connect Stripe to Salesforce

What This Integration Does

This integration writes Stripe payment activity straight onto Salesforce Accounts, Opportunities, and Contracts so revenue operations work from collected cash, not pipeline assumptions. Subscriptions, one-time charges, refunds, and failed-payment events all flow through, attaching to the right Salesforce record and updating the fields that sales, finance, and customer success rely on.

The CRM ends up reflecting what each customer has paid, when, and on what plan. No one has to copy figures from Stripe into Salesforce notes.

The Workflow

When a Stripe subscription is created (typically triggered after a sales rep closes the deal and sends the customer to a checkout), the integration finds the matching Salesforce Opportunity via a Stripe customer metadata field that carries the Opportunity ID. It moves the Opportunity to Closed Won, sets the Amount and Annual Contract Value from the Stripe subscription, and creates a Contract record linked to the Account with the start date, term, and plan name pulled directly from Stripe.

For ongoing activity, every invoice.paid event updates a rolling Lifetime Value field on the Account and writes a child record under the Account so the sales team can see exactly which renewals have processed and which are upcoming. Failed payment events (invoice.payment_failed) fire a Salesforce Task assigned to the account owner with the dunning status, the retry schedule, and the at-risk MRR, so customer success can reach out before the subscription is cancelled rather than after.

Refunds and disputes write back too: a refund pushes a negative revenue entry against the Account and adjusts the Customer Health field. The pipeline reports the sales team runs every Monday now reflect collected revenue and at-risk accounts rather than closed pipeline alone.

Before and After

Before, the revenue team reconciles Stripe to Salesforce manually at month-end, usually two or three days into the new month. Sales reps look at Opportunities marked Closed Won but have no idea whether the customer actually paid, started, downgraded, or churned. Customer success learns about failed payments from the customer rather than from the system.

After, Salesforce reflects Stripe in near real time. Sales reps see collected ACV on every account they own. Customer success gets a task the moment a payment fails. Finance can report from Salesforce because it now agrees with Stripe.

Who Needs This

Mid-market SaaS companies running sales-led motions through Salesforce while billing through Stripe. The integration becomes worth building once the Stripe customer base exceeds a few hundred active subscriptions and the manual mapping between Opportunities and subscriptions starts breaking down. That typically coincides with hiring a first dedicated revenue operations person.

How We Build This

We build this as a custom bi-directional API integration using Stripe webhooks and the Salesforce REST and Bulk APIs. Salesforce’s strict governor limits make naive integrations fragile under load, so we batch updates, use the Bulk API for backfills, and queue webhooks through our own infrastructure to ride out Salesforce maintenance windows. See Stripe API Integration and Salesforce API Integration for the underlying capabilities. Other payment-to-accounting builds sit in the integrations overview, including Stripe to Sage and PayPal to Xero if those pairings are relevant to your stack.

Get This Built

If your sales team is reporting on Closed Won and your finance team is reporting on Stripe and the two numbers never match, we can close the loop with a custom Stripe to Salesforce integration.