# Salesforce Stripe integration: ways to connect, setup, and the payment check on the opportunity

https://salesbond.app/blog/salesforce-stripe-integration-payment-status-on-opportunity-manager-check/
Published: 2026-10-27 · Updated: 2026-11-12

A Salesforce Stripe integration runs through Stripe’s own app, Salesforce Billing with Stripe as the gateway, an AppExchange package, Zapier or MuleSoft, or a consultancy’s code. None of them, out of the box, tells a sales manager which won opportunities were paid. That takes one Payment Status field, an owner for it, and two lists every Monday: Closed Won with no payment, and payments with no opportunity.

## Ways to connect Stripe and Salesforce

The official route is the Stripe app for Salesforce Platform, listed on AppExchange as “Stripe for Salesforce Platform” ( [AppExchange listing](https://appexchange.salesforce.com/appxListingDetail?listingId=4dff0f8e-0b10-47c2-a3a3-f3905e7f7927)). Stripe calls it “an integration builder within Salesforce”: the Stripe API inside Flow Builder and Apex (checked November 2026; [Stripe app for Salesforce Platform](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/overview)). Two parts come ready-made. Stripe Billing Sync copies Stripe billing objects into Salesforce custom objects, in real time or on a schedule. Stripe Events creates the webhook endpoint in Stripe for the events you pick, and each event lands as a Stripe Event record that a record-triggered flow can act on ( [Configure events](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/configure-events)). It works best, Stripe says, on Sales, Revenue, Service, Commerce and Experience Cloud.

Does Salesforce have a payment system of its own? Salesforce Billing takes payments through the Salesforce Payment Gateway, and Stripe can be the payment service behind it: Stripe’s Salesforce Billing Extension runs charges and refunds from the Salesforce Billing screens (checked November 2026; [Salesforce Billing Extension](https://docs.stripe.com/use-stripe-apps/salesforce-billing-extension)). It’s a route for teams already on Salesforce Billing, and its setup assumes Salesforce CPQ too ( [Configure Stripe app for Salesforce Billing](https://docs.stripe.com/use-stripe-apps/salesforce-billing/configuration)).

Partner packages on AppExchange are the third option. We won’t name one, because we haven’t run one. Ask any of them two things: does it write a field on the Opportunity, and how does it find the right one?

Then the integration platforms. Zapier pairs Stripe triggers such as New Payment, Failed Payment and New Refund with Salesforce actions such as Find Record and Update Record (checked November 2026; [Zapier: Salesforce and Stripe](https://zapier.com/apps/salesforce/integrations/stripe)). That is enough to find an opportunity and write one field; the finding is the hard part. MuleSoft has a Stripe Connector for Anypoint ( [Stripe Connector](https://docs.mulesoft.com/stripe-connector/latest/)), worth it only if your company already runs MuleSoft. Many search results describe one more route, a consultancy’s own build, usually on top of the official app.

Our pick: on Stripe Billing, the official app, because the data model is already drawn; on one-off payments, a flow on the Stripe Event object or a three-step Zap, because there is less to maintain. HubSpot teams face a different fork, covered in [HubSpot Stripe integration: what reaches the deal](https://salesbond.app/blog/hubspot-stripe-integration-payment-status-on-deal-manager-check/).

## Setup, per Stripe’s installation guide

1. Turn on Lightning Web Security under Setup > Session Management > Session Settings.
2. Install the package from the AppExchange listing into the right org (test and production are separate installs). Choose Install for Admins Only and tick Approve Third-Party Access.
3. Open App Launcher > Stripe for Salesforce Platform > Get Started > Authorize, and click Allow in the window that opens.
4. Paste a Stripe publishable key and a restricted access key, then click Add Account.
5. Click Install Package to add the API extension, then Finish ( [Installation guide](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/installation-guide) ).
6. On the Account Management tab, either open All Webhook Events and toggle the events you want, or open the account’s More tab and turn on Stripe Billing Sync ( [Configuration](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/configuration) ).

On a sandbox, run the setup again rather than copying stripeGC objects from production. Nothing in the vendor part mentions the Opportunity.

## Payment Status on the opportunity: one picklist, one owner

The app’s default mappings tie Stripe to Account, Contract, Order and PricebookEntry; the Opportunity isn’t there. A synced charge sits in its own custom object, and the rep on the opportunity sees Stage, Amount, Close Date, and no money.

Create a custom picklist on the Opportunity object, Payment Status, with five values:

- Not invoiced
- Invoiced
- Partially paid
- Paid
- Refunded

A sixth value is where reps start guessing. Put the field next to Amount on the layout and in the Closed Won [list view](https://salesbond.app/blog/salesforce-list-views-manager-deal-hygiene/). Add Paid Date if you forecast cash. The fees and the card stay in Stripe.

Three answers come up for who sets Paid. The first answer is a record-triggered flow on the Stripe Event object (stripeGC__Stripe_Event__c), with stripeGC__Event_Name__c in the entry condition set to the event you care about; the flow finds the opportunity and sets Paid. Stripe has no record of your opportunity, so the flow needs a key to match on. Our habit, not a feature of the app: write the Opportunity ID into the metadata of the Stripe invoice or payment when it is created. With Billing Sync on, the app’s Metadata Mappings can carry that metadata key into a field on the synced Stripe object, and the flow matches on it. The second answer is Zapier: New Payment, Find Record, Update Record, with the same ID fix. The third answer is a person: finance sets Paid weekly on whatever the automation missed.

Whichever you choose the rule is one sentence. Paid is set by whoever saw the money, never by the rep on the client’s promise; the rep sets Invoiced. Lock it with field-level security: sales reads, the integration user and one person in finance edit. Same argument as for [QuickBooks invoices on the Salesforce opportunity](https://salesbond.app/blog/salesforce-quickbooks-integration-invoice-status-on-opportunity/): a Paid field that reps can edit ends up holding the rep’s expectation of payment.

## Monday lists: Closed Won with no payment, payments with no opportunity

![Two lists: Closed Won deals not marked Paid in Salesforce, and Stripe payments with no matching opportunity, each with three actions.](https://salesbond.app/wp-content/uploads/2026/10/salesforce-stripe-integration-payment-status-on-opportunity-2.png)

The first list is a list view: Stage equals Closed Won, Close Date older than the payment terms you agreed, Payment Status not equal to Paid. Sort by Amount, largest first, and read it at the pipeline meeting. Each row gets one of three answers. Inside terms: wait. Paid outside Stripe: finance sets Paid and notes where. Never really won: that’s a talk with the rep, and the field stays as it is.

The second list starts on the Stripe side. With Billing Sync on, open the Stripe Billing Data app and take the week’s paid invoices and charges whose customer has no Closed Won opportunity. Without sync, use the Stripe dashboard plus your Zap history, where a Find Record step that found nothing is the the row you want. Three answers again: attach it to the won opportunity and set Paid; create the missing opportunity, nearly always a renewal closed by email; or call it self-serve and keep it out of the pipeline.

One more case. Paid, but the Stripe amount is not the opportunity’s Amount? That is a quote problem, and [the quote vs opportunity amount check](https://salesbond.app/blog/salesforce-quotes-opportunity-sync-amount-check/) is where it goes.

## Refunds and failed payments

Leave the rest of the deal alone in both cases. A refund sets Payment Status to Refunded, and that is all: the opportunity stays Closed Won, Amount stays what was sold. In the official app you toggle the refund events for the relevant Stripe Object under All Webhook Events.

A failed payment changes nothing on the field. The opportunity is still Invoiced, the customer is still expected to pay. What it needs is a task for the owner, today, with the reason Stripe gave: the one extra automation worth building, from Zapier’s Failed Payment trigger or the failed-payment event on the Stripe Event object. Payment Status waits until the money arrives or a manager writes the deal off.

## Who keeps this working after launch

Four people, four things, written down once.

The Salesforce admin owns the app, and it is not set-and-forget. Per the configuration page, moving from API version 2022-11-30 to 2025-04-30 means manually updating the action and Apex nodes that reference the old one, so last year’s flow can stop quietly. Finance owns Paid for whatever the automation missed. The rep owns Invoiced and the next step. The sales manager owns the two lists and one number for the monthly review: how many opportunities are Closed Won and unpaid past terms, and what they add up to.

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It works with all 15 CRMs on its integrations list, Salesforce among them, analyses deal and customer data, finds risks and explains what needs attention. [Check your CRM with SalesBond](https://salesbond.app/).
